>>>>> " " == Alexander Viro <[EMAIL PROTECTED]> writes:
> Now, now. BKL _is_ worth the removal. The thing being, "oh, we
> just take BKL, so we don't have to worry about SMP races" is
> wrong attitude. In practice. For every SMP race there's a UP
> one lurking nearby.
You forget to mention the main reason for the BKL in ->lookup():
certain derived structures (struct inode springs to mind) get changed
in various places in the code. Apart from the BKL there is no way yet
to make those changes SMP-safe everywhere in the VFS.
Look for instance at the assorted references to i_size, i_?time etc,
which get referenced sometimes in fs-specific code, sometimes in
fs/inode.c, sometimes in mm/filemap.c...
Cheers,
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]
