Wes Peters wrote:
>
> Mike Smith wrote:
> >
> > Actually, there's still a *lot* of work that has to be done to make this
> > work "right" - let me say two things only:
> >
> > "resource allocation"
> >
> > "interrupt routing"
>
> And that's just the start. When it comes to network interfaces, trying
> to unthread them from the system in a small, fixed amount of time like
> will be required for hot-eject on CPCI, CardBus, etc., is really fugly.
Maybe it can be solved in two steps:
1. When the card is physically removed inform the driver that it
should shut down and don't try to get to the card afterwards. That means
it would handle some subset of configuration requests and delay or
throw away any data transfer requests.
2. Later take any neccessary amount of time to clean up the things.
-SB
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
