From: dragoran <drago01@gmail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: allow non root users to set io priority "idle" ?
Date: Mon, 06 Aug 2007 13:06:47 +0200 [thread overview]
Message-ID: <46B700C7.5090801@gmail.com> (raw)
In-Reply-To: <20070806103553.GA16133@one.firstfloor.org>
Andi Kleen wrote:
>> couldn't this be fixed by bumping idle tasks to middle while they hold a
>>
>
> Usually to high.
>
> But it's all complicated and hasn't been done consistently
> (there are real time mutexes in the -rt kernel for example,
> but there are lots of other locks and they have higher overhead too)
> and it's unclear we really want to do all this complexity anyways.
>
> Also as I said the problem could then still happen in user space
> which then would all need to be fixed to handle PI too.
>
> In some cases the relationship is also not as simple as a single
> lock. And for IO handling it would be likely quite hard.
>
> I personally always found idle priorities quite dubious because
> even if they worked reliable for the CPU they will clear your cache/
> load your memory controller and impact all other programs because
> of this. And for the disk they will cause additional seeks which are
> also very costly.
>
>
ok, thx so that means that the best that can be done for now is to run
beagle as best effort with prio 7 (like its done now).
next prev parent reply other threads:[~2007-08-06 11:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 9:45 allow non root users to set io priority "idle" ? 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 [this message]
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
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=46B700C7.5090801@gmail.com \
--to=drago01@gmail.com \
--cc=andi@firstfloor.org \
--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