lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 3 Mar 2008 11:03:56 +0100
From:	"Michael Kerrisk" <mtk.manpages@...glemail.com>
To:	"Arnd Bergmann" <arnd@...db.de>
Cc:	"Ingo Molnar" <mingo@...e.hu>, "Christoph Hellwig" <hch@....de>,
	cbe-oss-dev@...abs.org, "Jeremy Kerr" <jk@...abs.org>,
	linux-kernel@...r.kernel.org
Subject: Re: SCHED_IDLE documentation

On Mon, Mar 3, 2008 at 10:31 AM, Arnd Bergmann <arnd@...db.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?

Thanks.  That was going to be my next question!

I'm guessing that SCHED_IDLE doesn't get completely starved by a CPU
hog running nice +19, but it would still be interesting to know:
roughly how much of the CPU could the CPU_IDLE process expect to get
in that case?

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

Also might be useful to add th e answer to this to the man page...

Cheers,

Michael


-- 
Michael Kerrisk
Maintainer of the Linux man-pages project
http://www.kernel.org/doc/man-pages/
Want to report a man-pages bug?  Look here:
http://www.kernel.org/doc/man-pages/reporting_bugs.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ