From: Pavel Machek <pavel@suse.cz>
To: Albert Cahalan <albert@users.sf.net>
Cc: Jens Axboe <axboe@suse.de>,
P@draigBrady.com, 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: Tue, 18 Nov 2003 10:27:10 +0100 [thread overview]
Message-ID: <20031118092710.GA203@elf.ucw.cz> (raw)
In-Reply-To: <1068508372.734.116.camel@cube>
Hi!
> I suppose the nice() wrapper in glibc could
> be modified... but that's kind of silly when
> the kernel is getting modified anyway.
Perhaps modifying glibc is the right way after all. We do not want to
have nice(), ionice() and then cpunice() as a kernel interface.
OTOH it would be good to keep ionice() on the same scale as other
"nice" values so that "do-it-all" interface is easier.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-11-18 13:08 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
2003-11-10 23:52 ` Albert Cahalan
2003-11-18 9:27 ` Pavel Machek [this message]
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=20031118092710.GA203@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=P@draigBrady.com \
--cc=albert@users.sf.net \
--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