archive mirror
 help / color / mirror / Atom feed
From: Arjan van de Ven <>
To: utz lehmann <>
Cc: LKML <>, Chris Wright <>
Subject: Re: [PATCH] scheduling priorities with rlimit
Date: Sun, 09 Jan 2005 20:06:37 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <1105290936.24812.29.camel@segv.aura.of.mankind>

On Sun, 2005-01-09 at 18:15 +0100, utz lehmann wrote:
> Hi
> I really like the idea of controlling the maximum settable scheduling
> priorities via rlimit. See the Realtime LSM thread. I want to give users
> the right to raise the priority of previously niced jobs.
> I have modified Chris Wright's patch (against 2.6.10):
> (
> - allow always to increase nice levels (lower priority).
> - set the default for RLIMIT_PRIO to 0.
> - add the other architectures.
> With this the default is compatible with the old behavior.
> With RLIMIT_PRIO > 0 a user is able to raise the priority up to the
> value. 0-39 for nice levels 19 .. -20, 40-139 for realtime priorities
> (0 .. 99).

this is a bit of an awkward interface don't you think?
I much rather have the rlimit match the exact nice values we communicate
to userspace elsewhere, both to be consistent and to not expose
scheduler internals to userpsace.

Also I like the idea of allowing sysadmins to make certain users/groups
nice levels 5 and higher (think a university machine that makes all
students nice 5 and higher only, while giving staff 0 and higher, and
the sysadmin -5 and higher ;)

  reply	other threads:[~2005-01-09 19:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-09 17:15 [PATCH] scheduling priorities with rlimit utz lehmann
2005-01-09 19:06 ` Arjan van de Ven [this message]
2005-01-09 19:23   ` utz lehmann
2005-01-09 20:34   ` Chris Wright
2005-01-10 18:01     ` utz lehmann
2005-01-10 15:15   ` Horst von Brand

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).