Re: [announce] "kill the Big Kernel Lock (BKL)" tree

[Alan Cox]

> > So you just stick unlock_kernel()/lock_kernel() around the call
> > to TTY (or similar to the entry points)
> > 
> 
> ... assuming that the ISDN code doesn't assume lock continuity across 
> the TTY call.

And procfs and between the tty and the net config code and ...

Keeping the BKL just in legacy places doesn't work. A counting mutex (ie
one you can self multi-lock) might be very useful to fix some of these
however as once we push it down to the point of being a driver specific
lock we can just give it a driver mutex
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/