public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chris@wirex.com>
To: Stephen Baker <stbaker@cisco.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux Kernel Patch; setpriority
Date: Wed, 27 Mar 2002 14:32:31 -0800	[thread overview]
Message-ID: <20020327143231.A19240@figure1.int.wirex.com> (raw)
In-Reply-To: <3CA232A1.7040702@cisco.com>

* Stephen Baker (stbaker@cisco.com) wrote:
> 
> This patch will allow a process or thread to changes it's priority 
> dynamically based on it's capabilities.  In our case we wanted to use 
> threads with Linux.  To have true priorities we need root to use 
> SCHED_FIFO or SCHED_RR; in many case root access is not allowed but we 
> still wanted priorities.  So we started using setpriority to change a 
> threads priority.  Now we used nice values from 19 to 0 which did not 
> require root access.  In some cases a thread need to raise it's nice 
> level and this would fail.  I also saw a note man renice(8) that said 
> this bug exists.

hmm, SUS v3 seems to disagree.

"Only a process with appropriate privileges can lower its nice value."

and with this patch setpriority(2) is now inconsistent with nice(2)
(albeit i don't know how much longer that interface will persist in arch
independent portion of the kernel based on the comments surrounding it).

-chris

  parent reply	other threads:[~2002-03-27 22:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-27 20:59 Linux Kernel Patch; setpriority Stephen Baker
2002-03-27 21:19 ` David Wagner
2002-03-29  0:24   ` Mike Fedyk
2002-03-27 22:32 ` Chris Wright [this message]
2002-03-28 21:19   ` Bill Davidsen
2002-03-28 22:20     ` Stephen Baker
2002-03-29  0:39       ` Bill Davidsen

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=20020327143231.A19240@figure1.int.wirex.com \
    --to=chris@wirex.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stbaker@cisco.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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