From: "Martin J. Bligh" <mbligh@aracnet.com>
To: John Yau <jyau_kernel_dev@hotmail.com>, "'Robert Love'" <rml@tech9.net>
Cc: linux-kernel@vger.kernel.org
Subject: RE: [PATCH] Minor scheduler fix to get rid of skipping in xmms
Date: Sat, 06 Sep 2003 19:40:14 -0700 [thread overview]
Message-ID: <149150000.1062902395@[10.10.2.4]> (raw)
In-Reply-To: <000201c374c8$1124ee20$f40a0a0a@Aria>
>> The rationale behind Ingo's patch is to "break up" the timeslices to give
> better scheduling latency to
>> multiple tasks at the same priority.
>> So it is not "unnecessary context switches," just "extra context switches."
>
> Hmm...my reasoning is that those switches are unnecessary because the
> interactivity bonus/penalty will take care of breaking the timeslices up in
> case of a CPU hog, albeit not at precise 25 ms granularity. Though having
> regularity in scheduling is nice, I think Ingo's patch somewhat negates the
> purpose of having heterogenous time slice lengths. I suspect Ingo's
> approach will thrash the caches quite a bit more than mine; we should
> definitely test this a bit to find out for sure. Any suggestions on how to
> go about that?
>
> If we're going to do a context switch every 25 ms no matter what, we might
> as well just make the scheduler a true real time scheduler, dump having
> different time slice lengths and interactivity recalculations, and go
> completely round robin with strictly enforced priorities and a single class
> of time slice somewhere 1 to 5 ms long.
IIRC, that context switching was what sucked on cpu bound jobs (like
doing a kernel compile). If you can send me both patches (offline),
I'll do a straight comparison on the benchmarking rig I have set up
on Monday.
M.
next prev parent reply other threads:[~2003-09-07 2:41 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-06 9:46 [PATCH] Minor scheduler fix to get rid of skipping in xmms John Yau
2003-09-06 10:03 ` Michael Buesch
2003-09-06 17:01 ` Robert Love
2003-09-06 17:59 ` John Yau
2003-09-06 18:17 ` John Yau
2003-09-06 19:42 ` Rahul Karnik
2003-09-06 20:04 ` Robert Love
2003-09-06 22:41 ` John Yau
2003-09-07 2:40 ` Martin J. Bligh [this message]
2003-09-07 5:13 ` Nick Piggin
2003-09-07 7:48 ` Johnny Yau
2003-09-07 8:10 ` Nick Piggin
2003-09-07 8:35 ` John Yau
2003-09-07 9:26 ` Nick Piggin
2003-09-07 17:30 ` John Yau
2003-09-07 17:36 ` Nick Piggin
2003-09-08 0:22 ` Con Kolivas
2003-09-08 0:27 ` David Lang
2003-09-08 0:47 ` Con Kolivas
2003-09-07 5:08 ` Nick Piggin
2003-09-07 6:18 ` Andrew Morton
2003-09-07 6:29 ` Nick Piggin
2003-09-07 6:45 ` Andrew Morton
2003-09-07 6:59 ` Nick Piggin
2003-09-07 7:02 ` Nick Piggin
2003-09-07 14:32 ` Martin J. Bligh
2003-09-07 17:02 ` Robert Love
2003-09-07 17:34 ` Andrew Morton
2003-09-07 18:12 ` Nick Piggin
2003-09-07 18:13 ` Nick Piggin
2003-09-06 15:58 John Yau
2003-09-06 16:57 ` Michael Buesch
2003-09-08 22:27 Steven Pratt
2003-09-08 22:56 ` Andrew Morton
2003-09-08 23:22 ` William Lee Irwin III
2003-09-09 2:10 ` Con Kolivas
2003-09-09 2:16 ` Con Kolivas
2003-09-09 2:31 ` Con Kolivas
2003-09-09 2:33 ` Andrew Morton
2003-09-09 4:14 ` Nick Piggin
2003-09-09 6:49 ` Con Kolivas
2003-09-09 23:53 ` Cliff White
2003-09-10 2:12 ` Nick Piggin
2003-09-10 19:05 ` Steven Pratt
2003-09-10 20:23 ` Dave Hansen
[not found] ` <3F5FE385.10204@cyberone.com.au>
[not found] ` <3F607E62.3010903@austin.ibm.com>
[not found] ` <3F60873B.4000005@cyberone.com.au>
2003-09-11 22:57 ` Steven Pratt
2003-09-11 0:14 ` Cliff White
2003-09-09 22:06 ` Steven Pratt
2003-09-09 22:12 ` Andrew Morton
2003-09-10 13:59 ` Steven Pratt
2003-09-10 18:51 ` Steven Pratt
[not found] <tCPY.4xU.1@gated-at.bofh.it>
[not found] ` <tDsR.5tY.31@gated-at.bofh.it>
[not found] ` <tZ0f.49P.5@gated-at.bofh.it>
[not found] ` <tZjz.4Bn.7@gated-at.bofh.it>
2003-09-09 23:24 ` David Mosberger-Tang
2003-09-11 2:55 Andrew Theurer
2003-09-11 11:04 ` Nick Piggin
2003-09-11 13:05 ` Andrew Theurer
2003-09-11 13:53 ` Nick Piggin
2003-09-11 14:37 ` Andrew Theurer
2003-09-11 23:32 Craig Thomas
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='149150000.1062902395@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=jyau_kernel_dev@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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).