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

[Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>]

> >  - superblock read/write.
> > 
> - fasync
> 
> [had some patches for "fasync_locked", not sure if it's worth it]
> 
> - character device open

file structures - as well

> I tried to recruit kernel janitors some time ago to just do all the
> ioctl -> ioctl_unlocked/explicit lock_kernel changes. There were a few
> patches generated but the effort died down then.

Start at the other end - you can't fix the ioctls until you fix what the
ioctls interact with. That ends up at the basic data structure and once
you fix those the rest just starts to fall into place.
--
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/