From: P@draigBrady.com
To: Jens Axboe <axboe@suse.de>
Cc: Albert Cahalan <albert@users.sourceforge.net>,
Herbert Xu <herbert@gondor.apana.org.au>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cfq + io priorities
Date: Mon, 10 Nov 2003 13:57:51 +0000 [thread overview]
Message-ID: <3FAF995F.70406@draigBrady.com> (raw)
In-Reply-To: <20031110133746.GB32637@suse.de>
Jens Axboe wrote:
> On Mon, Nov 10 2003, P@draigBrady.com wrote:
>
>>Albert Cahalan wrote:
>>
>>>Besides, the kernel load average was changed to
>>>include processes waiting for IO. It just plain
>>>makes sense to mix CPU usage with IO usage by
>>>default. Wanting different niceness for CPU
>>>and IO is a really unusual thing.
>>
>>I strongly agree. Of course it would be
>>nice/necessary to have seperate nice values,
>>but setting the global one should set the
>>underlying ones (cpu, disk, ...) also.
>
> Global one? nice is CPU in Linux, period.
Currently this is what it actually does.
But functionally, high nice value (to me at least)
means this process is low priority on the system =>
other processes get more system resources, and
the fact that this doesn't apply to IO until
now is just a defect. Now I can see some advantage
to splitting the tunables but not requiring
a new interface to turn this functionalit on.
I would like the new interface to turn it off.
I.E. I would like:
nice
cpu
IO
whereas you would like:
really_nice
nice
ionice
> ionice is io priority. I'm not
> going to change this. So Albert and you can agree as much as you want,
> unless you have some heavier arguments it's not going to help one bit.
fair enough.
Pádraig.
next prev parent reply other threads:[~2003-11-10 13:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 1:49 [PATCH] cfq + io priorities Albert Cahalan
2003-11-10 10:19 ` Herbert Xu
2003-11-10 10:36 ` Ali Magik Rama
2003-11-10 13:07 ` [PATCH] cfq + io priorities Albert Cahalan
2003-11-10 13:31 ` P
2003-11-10 13:37 ` Jens Axboe
2003-11-10 13:57 ` P [this message]
2003-11-10 23:52 ` Albert Cahalan
2003-11-18 9:27 ` Pavel Machek
2003-11-11 17:46 ` Toon van der Pas
-- strict thread matches above, loose matches on Subject: below --
2003-11-09 10:57 Guillaume Chazarain
2003-11-09 11:39 ` Jens Axboe
2003-11-13 12:54 ` Pavel Machek
2003-11-16 22:56 ` Jakob Oestergaard
2003-11-17 8:14 ` Jens Axboe
2003-11-18 13:26 ` Pavel Machek
2003-11-18 13:32 ` Jens Axboe
2003-11-18 13:38 ` Pavel Machek
2003-11-08 12:47 Jens Axboe
2003-11-08 13:25 ` Jens Axboe
2003-11-08 14:06 ` Jens Axboe
2003-11-09 21:30 ` Shailabh Nagar
2003-11-09 21:34 ` Jens Axboe
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=3FAF995F.70406@draigBrady.com \
--to=p@draigbrady.com \
--cc=albert@users.sourceforge.net \
--cc=axboe@suse.de \
--cc=herbert@gondor.apana.org.au \
--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