mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guillaume Chazarain <guichaz@yahoo.fr>
To: Jens Axboe <axboe@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cfq + io priorities
Date: Sun, 09 Nov 2003 11:57:39 +0100	[thread overview]
Message-ID: <SRLGXA875SP047EDQLEC055ZHDZX2V.3fae1da3@monpc> (raw)

> A process has an assigned io nice level, anywhere from 0 to 20. Both of

OK, I ask THE question : why not using the normal nice level, via
current->static_prio ?
This way, cdrecord would be RT even in IO, and nice -19 updatedb would have
a minimal impact on the system.

> these end values are "special" - 0 means the process is only allowed to
> do io if the disk is idle, and 20 means the process io is considered

So a process with ioprio == 0 can be forever starved. As it's not
done this way for nice -19 tasks (unlike FreeBSD), wouldn't it be
safer to give a very long deadline to ioprio == 0 requests ?


Thanks for making something I have been dreaming of for a long time :)


Guillaume





             reply	other threads:[~2003-11-09 10:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-09 10:57 Guillaume Chazarain [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2003-11-10  1:49 Albert Cahalan
2003-11-10 10:19 ` Herbert Xu
2003-11-10 13:07   ` 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
2003-11-11 17:46     ` Toon van der Pas
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=SRLGXA875SP047EDQLEC055ZHDZX2V.3fae1da3@monpc \
    --to=guichaz@yahoo.fr \
    --cc=axboe@suse.de \
    --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

Powered by JetHome