mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <axboe@suse.de>,
	ck list <ck@vds.kolivas.org>
Subject: Re: [patch] cfq: ioprio inherit rt class
Date: Sat, 03 Jun 2006 13:40:28 -0400	[thread overview]
Message-ID: <1149356428.28744.27.camel@mindpipe> (raw)
In-Reply-To: <200606031010.08794.kernel@kolivas.org>

On Sat, 2006-06-03 at 10:10 +1000, Con Kolivas wrote:
> On Saturday 03 June 2006 03:12, Jens Axboe wrote:
> > Not sure. RT io needs to be considered carefully, but I guess so does RT
> > CPU scheduling. For now I'd prefer to play it a little safer, and only
> > inheric the priority value and not the class.
> 
> The problem I envisioned with that was that realtime tasks, if they don't 
> specify an io priority (as most current code doesn't), would basically get io 
> priority 4 and have the same proportion as any nice 0 SCHED_NORMAL task 
> whereas -nice tasks automatically are getting better io priority. How about 
> givent them normal class but best priority so they are at least getting the 
> same as nice -20?
> 

Con,

Have you seen RT threads trying to disk IO 'in the wild' or is this a
theoretical concern?  I don't know of any such apps.

Lee


  reply	other threads:[~2006-06-03 17:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-27  1:50 Con Kolivas
2006-05-27  2:08 ` Con Kolivas
2006-06-02 17:12 ` [ck] " Jens Axboe
2006-06-03  0:10   ` Con Kolivas
2006-06-03 17:40     ` Lee Revell [this message]
2006-06-03 18:52       ` Horst von Brand
2006-06-04  1:37       ` Con Kolivas

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=1149356428.28744.27.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=axboe@suse.de \
    --cc=ck@vds.kolivas.org \
    --cc=kernel@kolivas.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

Powered by JetHome