public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Albert Cahalan <albert@users.sf.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cfq + io priorities
Date: 10 Nov 2003 08:07:54 -0500	[thread overview]
Message-ID: <1068469674.734.80.camel@cube> (raw)
In-Reply-To: <E1AJ994-0002xM-00@gondolin.me.apana.org.au>

On Mon, 2003-11-10 at 05:19, Herbert Xu wrote:
> Albert Cahalan <albert@users.sf.net> wrote:
> > 
> > Sure, but do it in a way that's friendly to
> > all the apps and admins that only know "nice".
> > 
> > nice_cpu   sets CPU niceness
> > nice_net   sets net niceness
> > nice_disk  sets disk niceness
> > ...
> > nice       sets all niceness values at once
> 
> That's a user space problem.  No matter what Jens
> does, you can always make nice(1) do what you said.

It's not just the nice command. There's a syscall
interface you know, and lots of apps use it.

#include <unistd.h>
int nice(int inc);

You planning to hack ALL those apps? You'll
convince BSD-centric developers to include
this Linux-specific change?

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.



  parent reply	other threads:[~2003-11-10 13:23 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   ` Albert Cahalan [this message]
2003-11-10 13:31     ` [PATCH] cfq + io priorities 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
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=1068469674.734.80.camel@cube \
    --to=albert@users.sf.net \
    --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