linux-kernel - Re: [PATCH 5/6] sched: SCHED_FIFO/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] [thread-next>] [day] [month] [year] [list]

Message-Id: <1193868208.5911.3.camel@lappy>
Date:	Wed, 31 Oct 2007 23:03:28 +0100
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Mike Galbraith <efault@....de>,
	Dmitry Adamushko <dmitry.adamushko@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Lennart Poettering <mzxreary@...inter.de>
Subject: Re: [PATCH 5/6] sched: SCHED_FIFO/SCHED_RR watchdog timer


On Wed, 2007-10-31 at 22:49 +0100, Andi Kleen wrote:
> Peter Zijlstra <a.p.zijlstra@...llo.nl> writes:
> 
> > Introduce a new rlimit that allows the user to set a runtime timeout
> > on real-time tasks. Once this limit is exceeded the task will receive
> > SIGXCPU.
> 
> Nice idea.
> 
> It would be even nicer if you could allow a couple of them. Partition
> the RT priorities into a few classes and have an own limit for each them.
> 
> A small number of classes (3-4) would be probably enough and not bloat
> the rlimits too much.
> 
> I'm thinking of the case where you have different kinds of real
> time processes. Like your mp3 player which you want to be slightly
> real time, but with a low SIGXCPU limit. 
> 
> And then something else real time which is more important and
> you would set a higher limit. etc.

But its an rlimit, it can be set per process. Not sure what multiple
classes per process would gain us, let alone how that process has to
figure out which class to use.


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