From: Jens Axboe <axboe@suse.de>
To: Con Kolivas <kernel@kolivas.org>
Cc: ck list <ck@vds.kolivas.org>, linux list <linux-kernel@vger.kernel.org>
Subject: Re: [ck] [patch] cfq: ioprio inherit rt class
Date: Fri, 2 Jun 2006 19:12:16 +0200 [thread overview]
Message-ID: <20060602171215.GM4400@suse.de> (raw)
In-Reply-To: <200605271150.41924.kernel@kolivas.org>
On Sat, May 27 2006, Con Kolivas wrote:
> Jens, ml
>
> I was wondering if cfq io priorities should be explicitly set to the realtime
> class when no io priority is specified from realtime tasks as in the
> following patch? (rt_task() will need to be modified to suit the PI changes in
> -mm)
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.
--
Jens Axboe
next prev parent reply other threads:[~2006-06-02 17:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-27 1:50 [patch] cfq: ioprio inherit rt class Con Kolivas
2006-05-27 2:08 ` Con Kolivas
2006-06-02 17:12 ` Jens Axboe [this message]
2006-06-03 0:10 ` Con Kolivas
2006-06-03 17:40 ` Lee Revell
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=20060602171215.GM4400@suse.de \
--to=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;
as well as URLs for NNTP newsgroup(s).