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: <p73fxzr2bv4.fsf@bingen.suse.de>
Date:	Wed, 31 Oct 2007 22:49:35 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
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

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.

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