linux-kernel - Re: resend: KERNEL BUG: nice level should not affect SCHED

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] [day] [month] [year] [list]

Message-ID: <45F56F37.6090407@nortel.com>
Date:	Mon, 12 Mar 2007 09:18:15 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	Con Kolivas <kernel@...ivas.org>
CC:	Robert Love <rml@...ell.com>, Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...l.org>,
	Linux kernel <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...l.org>
Subject: Re: resend: KERNEL BUG: nice level should not affect SCHED_RR timeslice

Con Kolivas wrote:

> Indeed we do change timeslice with nice on rt_tasks in mainline at the moment. 
> Truth is most rt programming couldn't care less about timeslices, but your 
> point about it deviating from the standard is valid. RSDL does not change 
> timeslice with nice on SCHED_RR tasks so it's sort of getting addressed by 
> proxy.

Unfortunately we have some vendor-supplied software that does care about 
timeslices.  It's a crazy thing with multiple SCHED_RR kernel threads 
that don't really self-manage very well.  They're spawned by a 
SCHED_OTHER task and inherit its nice level.

We modified the startup for the spawning task to run it at a lower nice 
level and were fairly surprised when the latency of message handling 
went way up.

Chris
-
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/