All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <ms@teamix.de>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>, Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: [PATCH] CFS scheduler: documentation about scheduling policies
Date: Tue, 23 Sep 2008 11:01:26 +0200	[thread overview]
Message-ID: <200809231101.41624.ms@teamix.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1648 bytes --]

The documentation about the CFS scheduler is scarse when it comes to 
scheduling policies. This patch adds a chapter about the scheduling policies 
it supports. Peter Zijlstra provided most of the information for it in

http://marc.info/?l=linux-kernel&m=122210038326356&w=2

This patch is based on 2.6.27-rc7.

Signed-off-by: Martin Steigerwald <ms@teamix.de>

---
--- sched-design-CFS.txt-2.6.27-rc7     2008-07-13 23:51:29.000000000 +0200
+++ sched-design-CFS.txt        2008-09-23 10:33:01.107393509 +0200
@@ -118,6 +118,29 @@ Some implementation details:
    quite a bit simpler as a result.


+Supported scheduling policies
+=============================
+
+CFS implements three scheduling policies:
+
+  - SCHED_NORMAL (traditionally called SCHED_OTHER): The scheduling
+    policy that is used for regular tasks.
+
+  - SCHED_BATCH: Does not preempt nearly as often as regular tasks
+    would, thereby allowing tasks to run longer and make better use of
+    caches but at the cost of interactivity. This is well suited for
+    batch jobs.
+
+  - SCHED_IDLE: This is even weaker than nice 19, but its not a true
+    idle timer scheduler in order to avoid to get into priority
+    inversion problems which would deadlock the machine.
+
+SCHED_FIFO/_RR are implemented in sched_rt.c and are as specified by
+POSIX.
+
+The command chrt from util-linux-ng 2.13.1.1 can set all of these except
+SCHED_IDLE.
+
 Group scheduler extension to CFS
 ================================

-- 
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 --]

             reply	other threads:[~2008-09-23  9:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-23  9:01 Martin Steigerwald [this message]
2008-09-23  9:11 ` [PATCH] CFS scheduler: documentation about scheduling policies Ingo Molnar
2008-09-23  9:53   ` Martin Steigerwald
2008-09-23 10:14     ` Ingo Molnar
2008-09-23 11:48   ` Martin Steigerwald
2008-09-23 11:50     ` Ingo Molnar
2008-09-23 12:01       ` Martin Steigerwald
2008-09-23 12:07         ` Ingo Molnar
2008-09-23 12:10         ` 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=200809231101.41624.ms@teamix.de \
    --to=ms@teamix.de \
    --cc=a.p.zijlstra@chello.nl \
    --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.