From: Sid Boyce <sboyce@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: 2.6.x Scheduler, preemption and responsiveness - puzzlement
Date: Sun, 11 Jul 2004 23:08:06 +0100 [thread overview]
Message-ID: <40F1BA46.9000207@blueyonder.co.uk> (raw)
With the 2.6 kernel I expected that my boxes would be responsive under
heavy loads such as exacted by updatedb. What I'm finding is that when
updatedb and other heavy hitters are running, I'm often unable to switch
desktops or start other tasks. I'm currently using 2.6.7-mm1, but this
has been true for all 2.6 kernels. I have CONFIG_PREEMPT=y,
/proc/sys/kernel/kernel_preemption doesn't exist.
SuSE 9.1, Athlon XP2800+, 512M.
Regards
Sid.
--
Sid Boyce .... Hamradio G3VBV and keen Flyer
===== LINUX ONLY USED HERE =====
next reply other threads:[~2004-07-11 22:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-11 22:08 Sid Boyce [this message]
2004-07-11 22:18 ` 2.6.x Scheduler, preemption and responsiveness - puzzlement bert hubert
2004-07-11 22:55 ` Sid Boyce
2004-07-12 1:00 ` Alistair John Strachan
[not found] ` <20040712000137.GA3854@hobbes.itsari.int>
2004-07-12 1:06 ` Sid Boyce
2004-07-12 1:57 ` Con Kolivas
2004-07-12 9:19 ` Sid Boyce
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=40F1BA46.9000207@blueyonder.co.uk \
--to=sboyce@blueyonder.co.uk \
--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