mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: varg@theor.jinr.ru (Sheplyakov Alexei)
To: Andi Kleen <andi@firstfloor.org>
Cc: dragoran <drago01@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: allow non root users to set io priority "idle" ?
Date: Wed, 8 Aug 2007 13:51:32 +0400	[thread overview]
Message-ID: <20070808095132.GA31020@theor.jinr.ru> (raw)
In-Reply-To: <p73zm14lxyy.fsf@bingen.suse.de>

[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]

On Mon, Aug 06, 2007 at 01:11:01PM +0200, Andi Kleen wrote:

> Very low priority can starve others when it holds some kernel resource
> needed by another task.  

Nevertheless ordinary users are permitted to lower priority ([re]nice)
and resource limits (setrlimit).

> For IO I suppose the same could happen too. e.g. low priority
> task wants to write out a page and keeps it locked until the IO 
> is finished. High priority task wants to access the page and has
> to wait until it is unlocked. Middle task generates an endless
> stream of IO that makes the idle priority writeout never finish.

I don't quite understand. There are a lot of other ways to starve such
high-priority process: 
1. renice the low-priority process
2. send it a signal
3. ptrace it
4. use something like cpulimit (http://cpulimit.sourceforge.net/) to stall it
....

So I think current behaviour of ionice is inconsistent (and pointless).

P.S. 
Please CC me, I'm not subscribed.

Best regards,
 Alexei

-- 
All science is either physics or stamp collecting.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

  parent reply	other threads:[~2007-08-08 10:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-06  9:45 dragoran
2007-08-06 11:11 ` Andi Kleen
2007-08-06 10:26   ` dragoran
2007-08-06 10:35     ` Andi Kleen
2007-08-06 11:06       ` dragoran
2007-08-07 20:44       ` Jens Axboe
2007-08-07 21:35         ` dragoran
2007-08-07 22:18           ` dragoran
2007-08-08  0:04             ` Andi Kleen
2007-08-08  5:06             ` Jens Axboe
2007-08-08  9:37               ` dragoran
2007-08-08  2:26   ` Lee Revell
2007-08-08 10:17     ` Andi Kleen
2007-08-08  9:51   ` Sheplyakov Alexei [this message]
2007-08-08 10:20     ` Andi Kleen
2007-08-08 11:49       ` Sheplyakov Alexei
2007-08-08 11:55         ` Andi Kleen
2007-08-08 10:52     ` Jens Axboe
     [not found] <8P7nW-2Jc-7@gated-at.bofh.it>
     [not found] ` <8P7QZ-3AR-17@gated-at.bofh.it>
     [not found]   ` <8P80L-3N5-25@gated-at.bofh.it>
     [not found]     ` <8P8ak-3Yr-9@gated-at.bofh.it>
2007-08-07 18:21       ` Bodo Eggert

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=20070808095132.GA31020@theor.jinr.ru \
    --to=varg@theor.jinr.ru \
    --cc=andi@firstfloor.org \
    --cc=drago01@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®