From: Bill Davidsen <davidsen@tmr.com>
To: Linux Kernel mailing List <linux-kernel@vger.kernel.org>
Subject: Preempt of BKL and with tickless systems
Date: Tue, 08 May 2007 17:06:21 -0400 [thread overview]
Message-ID: <4640E64D.3070304@tmr.com> (raw)
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.
I've been running some sched tests, and it seems to make little
difference how that's set. Before I run a bunch of extra tests, I
thought I'd ask.
New topic: I have found preempt, both voluntary and forced, seems to
help more with response as the HZ gets smaller. How does that play with
tickless operation, or are you-all waiting for me to run my numbers with
all values of HZ and not, and tell the world what I found? ;-)
--
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 reply other threads:[~2007-05-08 21:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 21:06 Bill Davidsen [this message]
2007-05-09 0:01 ` Preempt of BKL and with tickless systems Lee Revell
2007-05-10 21:19 ` Bill Davidsen
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=4640E64D.3070304@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
/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