From: walt <wa1ter@myrealbox.com>
To: linux-kernel@vger.kernel.org
Subject: Preemptible Big Kernel Lock?
Date: Mon, 10 Jan 2005 17:48:57 -0800 (PST) [thread overview]
Message-ID: <20050110172910.F49234@x9.ybpnyarg> (raw)
I've been running the P-BKL all day and I've been very
happy with it so far.
I've found the machine to be very responsive and smooth
during compilation of large programs, playback of audio/
video, all the usual stuff I do on my desktop machine.
The problem is: the same machine was also great two
days ago, before the preemptible BKL -- the best it's
been for years. I can't tell the difference, and I
had no complaints even before this update.
Two questions:
Would I expect to see a difference on a uni-processor
machine? (That's all I have.)
What kind of testing could I do to demonstrate the
difference?
next reply other threads:[~2005-01-11 1:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 1:48 walt [this message]
2005-01-11 7:46 ` Preemptible Big Kernel Lock? Arjan van de Ven
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=20050110172910.F49234@x9.ybpnyarg \
--to=wa1ter@myrealbox.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;
as well as URLs for NNTP newsgroup(s).