From: Jens Axboe <axboe@suse.de>
To: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: State of the CFQ scheduler
Date: Fri, 29 Aug 2003 08:59:32 +0200 [thread overview]
Message-ID: <20030829065932.GL16684@suse.de> (raw)
In-Reply-To: <1062107920.665.0.camel@teapot.felipe-alfaro.com>
On Thu, Aug 28 2003, Felipe Alfaro Solana wrote:
> On Thu, 2003-08-28 at 21:47, Jens Axboe wrote:
>
> > It shouldn't be too hard to adapt the latest version from before -mm
> > dropped it and adapting to the current kernels. If you want to give that
> > a go, I'd be happy to help you out.
>
> Why don't you post a patch against 2.6.0-test4 or 2.6.0-test4-mm1 on
> LKML? I would like to start using CFQ again :-)
Heh, did you not read the email? :)
I'll see if I get squeeze it in today, stay tuned.
--
Jens Axboe
next prev parent reply other threads:[~2003-08-29 7:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 13:55 State of the CFQ scheduler David Nielsen
2003-08-28 19:47 ` Jens Axboe
2003-08-28 21:58 ` Felipe Alfaro Solana
2003-08-29 6:59 ` Jens Axboe [this message]
2003-08-29 8:15 ` [PATCH] 2.6.0-test4 CFQ io scheduler Jens Axboe
2003-08-29 10:48 ` State of the CFQ scheduler Felipe Alfaro Solana
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=20030829065932.GL16684@suse.de \
--to=axboe@suse.de \
--cc=felipe_alfaro@linuxmail.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).