Re: [Announce] BKL shifting into drivers and filesystems - beware

From: Linus Torvalds (torvalds@transmeta.com)
Date: Fri Jul 14 2000 - 14:24:38 EST


On Fri, 14 Jul 2000, David Woodhouse wrote:

>
> torvalds@transmeta.com said:
>
> > I much rather do it now than later. Later means either: (a) during
> > 2.4.x or (b) early in 2.5.x.
>
> If we're going to do it, we're removing the last cases where it was valid
> to use sleep_on() and friends (with a few exceptions).

People _still_ don't understand.

AL VIRO DID NOT REMOVE THE BKL.

He MOVED it. He moved it into the "release()" function, so that we can
pick them off one-by-one. Some of them were never needed (like the
networking code that actually dropped it on purpose immediately), and some
of them will be trivial to fix up.

But no behaviour was changed. sleep_on() is still valid, because code that
used to have the kernel lock _still_ has the kernel lock. It's just that
they got it themselves, instead of depending on the VFS layer to get it
for them.

                Linus

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Sat Jul 15 2000 - 21:00:20 EST