|| ||Ingo Molnar <mingo-AT-elte.hu>|
|| ||Alan Cox <alan-AT-lxorguk.ukuu.org.uk>|
|| ||Re: SD still better than CFS for 3d ?(was Re: 2.6.23-rc1)|
|| ||Tue, 31 Jul 2007 11:13:59 +0200|
|| ||Peter Zijlstra <peterz-AT-infradead.org>,
Kasper Sandberg <lkml-AT-metanurb.dk>,
Linus Torvalds <torvalds-AT-linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel-AT-vger.kernel.org>,
* Alan Cox <firstname.lastname@example.org> wrote:
> > code runs under the BKL, and the only other major kernel
> > infrastructure that has BKL dependencies is the TTY code. Kasper, as
> > a debugging
> And half the ioctls some of which trigger long code sections.
the tty layer has relatively short BKL latencies, but reiser3 has long
ones, so those got transposed over to the tty layer, making it all quite
noticeable to the user.
BKL contention is not a big issue on the desktop _unless_ there's at
least one workload that creates really long BKL latencies. That
multiplexes it out to all the other BKL-using subsystems too.
the DRI/DRM BKL use was a problem some time ago, but i think it's now
using unlocked_ioctl(), correct? All the other ioctls are rare enough to
not really matter.
with PREEMPT_BKL there's also some sort of random effect of priority
inversion that makes the actual latencies depend on the scheduler - but
we dont understand that effect exactly, yet. (hopefully Kasper can help
us out with that. Peter got rid of his reiser3 partition the moment the
latencies were traced back to it.)
> For the tty layer I'm waiting for the revoke code to get finished up
> and move from -mm into Linus tree. At that point the real evil
> lock_kernel related stuff in the tty layer can switch to using the
> revoke code for hangup paths and then other bits can be tackled.
oh, wonderful! Alan, you are a true wizard :-) The tty layer is one of
the very few pieces of kernel code that scares the hell out of me :-)
to post comments)