From: Jens Axboe <axboe@suse.de>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RFT] simple deadline I/O scheduler
Date: Fri, 15 Mar 2002 11:57:56 +0100 [thread overview]
Message-ID: <20020315105756.GC22169@suse.de> (raw)
In-Reply-To: <20020104094334.N8673@suse.de> <E16l8sQ-0000EX-00@starship> <20020314073216.GB30351@suse.de> <E16lXVY-0000Rn-00@starship>
In-Reply-To: <E16lXVY-0000Rn-00@starship>
On Thu, Mar 14 2002, Daniel Phillips wrote:
> On March 14, 2002 08:32 am, Jens Axboe wrote:
> > On Wed, Mar 13 2002, Daniel Phillips wrote:
> > > Andrew Morton is also working in here, with a collection of ideas that I hope
> > > are complementary if looked at the right way. See his '[patch] delayed disk
> > > block allocation' post.
> >
> > Right, I noticed. We could get good write clustering in general with vm
> > merging, though.
>
> Sorry, I can't parse that, do you mean 'if the elevator merging is merged with
> vm's' or 'if vm does merging' or... ?
Heh, guess it wasn't too clear. It was supposed to say 'if vm does the
merging' or at least partially does it.
--
Jens Axboe
prev parent reply other threads:[~2002-03-15 10:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 8:43 [PATCH][RFT] simple deadline I/O scheduler Jens Axboe
2002-01-04 9:21 ` Jens Axboe
2002-01-04 10:51 ` Jens Axboe
2002-01-05 13:38 ` Pavel Machek
2002-01-07 19:31 ` Mark Hahn
2002-01-07 19:57 ` Rik van Riel
2002-01-08 6:43 ` Jens Axboe
2002-03-13 13:33 ` Daniel Phillips
2002-03-14 7:32 ` Jens Axboe
2002-03-14 15:51 ` Daniel Phillips
2002-03-15 10:57 ` Jens Axboe [this message]
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=20020315105756.GC22169@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
/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.