From: Andi Kleen <andi@firstfloor.org>
To: Sheplyakov Alexei <varg@theor.jinr.ru>
Cc: Andi Kleen <andi@firstfloor.org>, 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:55:35 +0200 [thread overview]
Message-ID: <20070808115535.GB13878@one.firstfloor.org> (raw)
In-Reply-To: <20070808114949.GA8465@theor.jinr.ru>
> The original question (unless I'm missing something) was "why _the owner_
> of a process is not enabled to lower its IO priority?" The owner of the
> process certainly can send signal and ptrace it.
Ah I misparsed you.
Sending signals and ptraces is atomic regarding system operations. This means
the kernel will finish doing whatever it is doing (or bail out releasing
all resources) before processing them. So stopping a process this
way can never starve its IO. Ok there are special cases like user space
FUSE or NFS servers that can block operations, but these are expected to run
as root.
-Andi
next prev parent reply other threads:[~2007-08-08 11:55 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
2007-08-08 10:20 ` Andi Kleen
2007-08-08 11:49 ` Sheplyakov Alexei
2007-08-08 11:55 ` Andi Kleen [this message]
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=20070808115535.GB13878@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=drago01@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=varg@theor.jinr.ru \
/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®