From: "Benjamin K. Stuhl" <benjamin.stuhl@colorado.edu>
To: Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Linux-Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: "sched: add vslice" causes horrible interactivity under load
Date: Sun, 27 Jan 2008 14:44:00 -0700 [thread overview]
Message-ID: <20080127144400.78e0aec5@colorado.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]
Hi,
I recently upgraded from 2.6.23.x to 2.6.24 and found that whereas
with 2.6.23.x I could have multiple "make -j3" compilation runs going
in the background with no real problems (on a dual-core Core 2), with
2.6.24 I get multiple-second lags when trying to switch tasks in KDE.
I did a git bisect starting from 9b73e76f3cf63379dcf45fcd4f112f5812418d0a
in Linus's 2.6.25 tree in the hope that the recent scheduler merge might
have fixed the problem, but no such luck. Instead, git bisect points its
all-knowing finger at
commit 67e9fb2a39a1d454218d50383094940982be138f
Author: Peter Zijlstra <a.p.zijlstra@chello.nl>
Date: Mon Oct 15 17:00:10 2007 +0200
sched: add vslice
add vslice: the load-dependent "virtual slice" a task should
run ideally, so that the observed latency stays within the
sched_latency window.
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
A straight-forward git revert crashes at boot, so I don't have a patch to offer. :-/
(Please keep me CC'ed, since I'm not subscribed to LKML.)
Thanks for your help,
-- BKS
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2008-01-27 22:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-27 21:44 Benjamin K. Stuhl [this message]
2008-01-27 22:14 ` "sched: add vslice" causes horrible interactivity under load Ingo Molnar
2008-01-27 22:17 ` Ingo Molnar
2008-01-27 22:19 ` Ingo Molnar
2008-01-28 15:32 ` Benjamin K. Stuhl
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=20080127144400.78e0aec5@colorado.edu \
--to=benjamin.stuhl@colorado.edu \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.