public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Fengguang Wu <wfg@mail.ustc.edu.cn>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] readahead update on splice reads
Date: Tue, 12 Jun 2007 08:40:18 +0200	[thread overview]
Message-ID: <20070612064018.GP18832@kernel.dk> (raw)
In-Reply-To: <20070612030450.590659600@mail.ustc.edu.cn>

On Tue, Jun 12 2007, Fengguang Wu wrote:
> Andrew,
> 
> The two patches optimizes readahead invocations in splice reads:
> 
> 	readahead: move synchronous readahead call out of splice loop
> 	readahead: pass real splice size
> 
> They can be appended to readahead-convert-splice-invocations.patch in
> -mm tree.

Patches look nice, but unfortunately only -mm stuff and will need to be
rebased once 2.6.23 opens anyway.

Where are we on the ondemand read-ahead merging? -mm has continually had
different read-ahead code than mainline now for seemingly years, seems a
bit pointless to me. Either we get the stuff merged, or toss it out.
Nothing needs to simmer that long.

I suspect we wont see any real potential regressions before it hits
mainline anyway.

-- 
Jens Axboe


      parent reply	other threads:[~2007-06-12  6:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070612030450.590659600@mail.ustc.edu.cn>
2007-06-12  3:00 ` [PATCH 0/2] readahead update on splice reads Fengguang Wu
     [not found] ` <20070612030905.685830707@mail.ustc.edu.cn>
2007-06-12  3:00   ` [PATCH 1/2] readahead: move synchronous readahead call out of splice loop Fengguang Wu
     [not found] ` <20070612030905.812075843@mail.ustc.edu.cn>
2007-06-12  3:00   ` [PATCH 2/2] readahead: pass real splice size Fengguang Wu
2007-06-12  6:40 ` 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=20070612064018.GP18832@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wfg@mail.ustc.edu.cn \
    /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