LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Michael Kerrisk <mtk.manpages@googlemail.com>,
	Christoph Hellwig <hch@lst.de>,
	cbe-oss-dev@ozlabs.org, Jeremy Kerr <jk@ozlabs.org>,
	linux-kernel@vger.kernel.org
Subject: Re: SCHED_IDLE documentation
Date: Mon, 3 Mar 2008 11:04:18 +0100	[thread overview]
Message-ID: <20080303100418.GF18281@elte.hu> (raw)
In-Reply-To: <200803031031.52335.arnd@arndb.de>


* Arnd Bergmann <arnd@arndb.de> wrote:

> On Monday 03 March 2008, Ingo Molnar wrote:
> > > * What's the difference between SCHED_IDLE and SCHED_BATCH?
> > 
> > SCHED_BATCH can still have nice levels from -20 to +19, it is a modified 
> > SCHED_OTHER/SCHED_NORMAL for "throughput oriented" workloads.
> > 
> > SCHED_IDLE overrides the nice settings and it means a "super idle" 
> > workload.
> 
> Does that mean that a SCHED_IDLE task still runs some of the time if 
> you have a CPU hog running on +19, or can any other process starve the 
> SCHED_IDLE task?

yes, even SCHED_IDLE tasks get some CPU time - so complete starvation 
should not be possible. We dont really want to define the exact amount 
of time they need. (we might want to change that in the future) But it 
will always be less prio than nice +19 :-) You can think of it as if it 
was "nice +30".

> What happens if you have two SCHED_IDLE tasks on a single CPU, do they 
> get equal share, or will they just run as batch jobs?

they get equal share.

you can try it out too: if you have 2.6.23 or newer kernels then just 
pick up schedtool and use "schedtool -I" to run SCHED_IDLE tasks.

	Ingo

  parent reply	other threads:[~2008-03-03 10:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1203376368.275756.252634247263.1.gpush@pokey>
     [not found] ` <200803030612.28039.arnd@arndb.de>
     [not found]   ` <20080303051719.GA26102@lst.de>
2008-03-03  6:21     ` Arnd Bergmann
2008-03-03  7:33       ` Ingo Molnar
2008-03-03  8:40         ` Michael Kerrisk
2008-03-03  9:24           ` Ingo Molnar
2008-03-03  9:31             ` Arnd Bergmann
2008-03-03 10:03               ` Michael Kerrisk
2008-03-03 10:04               ` Ingo Molnar [this message]
2008-03-03 10:12                 ` Michael Kerrisk
2008-03-03 10:07             ` Michael Kerrisk
2008-03-03 10:17               ` Ingo Molnar
2008-03-03 10:20                 ` Michael Kerrisk
2008-03-03 12:31             ` Michael Kerrisk
2008-03-03 12:52               ` Ingo Molnar
2008-03-03 14:06                 ` Michael Kerrisk
2008-03-04 11:11                   ` Peter Zijlstra
2008-03-05 15:19                     ` Michael Kerrisk
2008-03-03 14:42                 ` Michael Kerrisk
2008-03-05 15:02                   ` Michael Kerrisk

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=20080303100418.GF18281@elte.hu \
    --to=mingo@elte.hu \
    --cc=arnd@arndb.de \
    --cc=cbe-oss-dev@ozlabs.org \
    --cc=hch@lst.de \
    --cc=jk@ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk.manpages@googlemail.com \
    --subject='Re: SCHED_IDLE documentation' \
    /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

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).