From: Martin Steigerwald <ms@teamix.de>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>
Subject: documentation about scheduling policies
Date: Mon, 22 Sep 2008 17:29:06 +0200 [thread overview]
Message-ID: <200809221729.06870.ms@teamix.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1514 bytes --]
Please CC to me as I am not subscribed to linux-kernel.
Hi!
I wonder about scheduling policies in CFS. I find these:
ms@mango> grep "case SCHED_" sched.c sched_fair.c | sort | uniq
~/lokal/Kernel/linux-2.6.26/kernel
sched.c: case SCHED_BATCH:
sched.c: case SCHED_FIFO:
sched.c: case SCHED_IDLE:
sched.c: case SCHED_NORMAL:
sched.c: case SCHED_RR:
sched_fair.c seems to differentiate SCHED_PATCH only:
ms@mango> egrep "(SCHED_I|SCHED_B)" sched_fair.c
~/lokal/Kernel/linux-2.6.26/kernel
* Completely Fair Scheduling (CFS) Class (SCHED_NORMAL/SCHED_BATCH)
if (likely(!sysctl_sched_compat_yield) && curr->policy != SCHED_BATCH)
{
if (unlikely(p->policy == SCHED_BATCH))
The documentation on scheduling policies in Documentation/scheduler appears
rather scarse to me.
The wikipage at
http://ck.wikia.com/wiki/SchedulingPolicies
has more hints. But I wonder whether they are up to date and also they partly
related to RSDL/SD features.
What about SCHED_IDLEPRIO anyway - the description of it makes it appear quite
useful to me? Is it SCHED_IDLE in the new scheduler? Hmm, it does not appear
that chrt can set this scheduling priority as of util-linux-ng 2.13.1.1.
I am willing to create documentation patches provided someone explains these
to me ;-).
Ciao,
--
Martin Steigerwald - team(ix) GmbH - http://www.teamix.de
gpg: 19E3 8D42 896F D004 08AC A0CA 1E10 C593 0399 AE90
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2008-09-22 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 15:29 Martin Steigerwald [this message]
2008-09-22 16:18 ` documentation about scheduling policies Peter Zijlstra
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=200809221729.06870.ms@teamix.de \
--to=ms@teamix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.