lkml.org 
[lkml]   [2008]   [May]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [announce] "kill the Big Kernel Lock (BKL)" tree
On Thu, May 15, 2008 at 02:34:30PM +0100, Alan Cox wrote:
> > > - superblock read/write.
> > >
> > - fasync
> >
> > [had some patches for "fasync_locked", not sure if it's worth it]
> >
> > - character device open
>
> file structures - as well

How so?

>
> > 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.

In my experience there's usually not too much interaction with other
kernel structures at the random driver ioctl level. I'm sure tty is
different, but it's probably not typical.

-Andi
>


\
 
 \ /
  Last update: 2008-05-15 16:23    [W:0.072 / U:0.480 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site