Re: 2.6.0-test7-mm1

[Ben Collins <bcollins@debian.org>]

> >>nodemgr_add_host() looks like the hard one.  Maybe make hl_drivers_lock a
> >>sleeping lock?
> >
> >
> >Problem is, things like bus resets happen in interrupt, and while I can
> >push off some things to occur in the nodemgr thread, a lot of other
> >stuff has to happen in the interrupt, and they require the same lock.
> 
> I was looking briefly at this too, and as you say, the problem is that 
> some things have to happen in interrupt, others happen in process 
> context.  I've attached a patch that implements one way to fix it: 
> double book-keeping - we maintain two lists of the highlevel drivers, 
> one protected by a semaphore another protected by the rw spinlock. The 
> lists are identical, except between the two list_add_tail()'s (and the 
> two list_del()'s), but that doesn't allow any harmful race conditions.
> 
> A more radical approach would be to split the highlevel interface into 
> two interfaces add_host() + remove_host() in a hpsb_host_notification 
> interface and the rest in another interface.  The driver would have to 
> register both interfaces if it needs them. Some drivers only use 
> add_host() and remove_host(), so they could register only the 
> hpsb_host_notification interface.

Actually I'm leaning toward getting rid of our internal locking and
reference counting and relying heavily on the device model's reference
counting and such. Take some of the work load off of our code.

Each host already has a device associated with it, so it just requires a
revamp of some internals.

-- 
Debian     - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/