From: Bill Davidsen <davidsen@tmr.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Linux Kernel mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Preempt of BKL and with tickless systems
Date: Thu, 10 May 2007 17:19:16 -0400 [thread overview]
Message-ID: <46438C54.20101@tmr.com> (raw)
In-Reply-To: <75b66ecd0705081701n414c29f7r74b0e4836798393a@mail.gmail.com>
Lee Revell wrote:
> On 5/8/07, Bill Davidsen <davidsen@tmr.com> wrote:
>> I think I have a reasonable grip on the voluntary and full preempt
>> models, can anyone give me any wisdom on the preempt of the BKL? I know
>> what it does, the question is where it might make a difference under
>> normal loads. Define normal as servers and desktops.
>
> This was introduced by Ingo to solve a real problem that I found,
> where some codepath would hold the BKL for long enough to introduce
> excessive scheduling latencies - search list archive for details. But
> I don't remember the code path (scrolling the FB console? VT
> switching? reiser3? misc. ioctl()s?). Basically, taking the BKL
> disabled preemption which caused long latencies.
>
> It's certainly possible that whatever issue led to this was solved in
> another way since.
>
Anything is possible. I feel that using voluntary + bkl is probably good
for most servers, forced preempt for desktop, although it really doesn't
seem to do much beyond voluntary.
Thanks for the clarification.
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2007-05-10 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 21:06 Preempt of BKL and with tickless systems Bill Davidsen
2007-05-09 0:01 ` Lee Revell
2007-05-10 21:19 ` Bill Davidsen [this message]
2007-05-21 7:36 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46438C54.20101@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox