From: Jens Axboe <axboe@suse.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Florian Schmidt <mista.tapas@gmx.net>,
Libin Varghese <libinv@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: I/O Scheduling
Date: Sat, 28 Jan 2006 20:18:14 +0100 [thread overview]
Message-ID: <20060128191814.GD9750@suse.de> (raw)
In-Reply-To: <1138471719.2799.20.camel@mindpipe>
On Sat, Jan 28 2006, Lee Revell wrote:
> On Sat, 2006-01-28 at 18:54 +0100, Florian Schmidt wrote:
> >
> > i'm also interested in these. Especially I/O priorities per
> > process/task similar to scheduling priorities. It would be just
> > awesome to be able to give i.e. a hd recording program (or any other
> > data aquisition or playback program) a high I/O priority.
> >
>
> I believe it's already implemented for the CFQ scheduler only, but the
> patch does not seem to be in mainline.
>
> Jens, what's the status of this?
It's merged, since 2.6.13.
--
Jens Axboe
next prev parent reply other threads:[~2006-01-28 19:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-28 9:58 I/O Scheduling Libin Varghese
2006-01-28 17:54 ` Florian Schmidt
2006-01-28 18:08 ` Lee Revell
2006-01-28 19:18 ` Jens Axboe [this message]
2006-01-28 19:44 ` Lee Revell
2006-01-28 21:28 ` 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=20060128191814.GD9750@suse.de \
--to=axboe@suse.de \
--cc=libinv@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mista.tapas@gmx.net \
--cc=rlrevell@joe-job.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.