From: Arnd Bergmann <arnd@arndb.de>
To: Ingo Molnar <mingo@elte.hu>
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 10:31:51 +0100 [thread overview]
Message-ID: <200803031031.52335.arnd@arndb.de> (raw)
In-Reply-To: <20080303092422.GA18281@elte.hu>
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?
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?
Arnd <><
next prev parent reply other threads:[~2008-03-03 9:32 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 ` SCHED_IDLE documentation 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 [this message]
2008-03-03 10:03 ` Michael Kerrisk
2008-03-03 10:04 ` Ingo Molnar
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=200803031031.52335.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=cbe-oss-dev@ozlabs.org \
--cc=hch@lst.de \
--cc=jk@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mtk.manpages@googlemail.com \
/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.