linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Jens Axboe <axboe@kernel.dk>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Jeff Moyer <jmoyer@redhat.com>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/3] implement readpages() for block device to optimize sequential read
Date: Thu, 21 Aug 2014 14:44:12 -0700	[thread overview]
Message-ID: <20140821144412.2a97f2a7400590097f3926de@linux-foundation.org> (raw)
In-Reply-To: <CAC5umygJozyMs5ybyDjCeZLrPnJOAYoNnjsvAFkYFRfVZiivKQ@mail.gmail.com>

On Sat, 16 Aug 2014 02:09:44 +0900 Akinobu Mita <akinobu.mita@gmail.com> wrote:

> 2014-08-15 7:04 GMT+09:00 Andrew Morton <akpm@linux-foundation.org>:
> > On Tue,  5 Aug 2014 23:38:31 +0900 Akinobu Mita <akinobu.mita@gmail.com> wrote:
> >
> >> This patchset implements readpages() operation for block device by
> >> using mpage_readpages() which can create multipage BIOs instead of
> >> BIOs for each page and reduce system CPU time consumption.
> >
> > Patchset is simple and straightforward enough.  But who the
> > heck cares about the performance of buffered reads from /dev/XXX?
> 
> I tend to consider the block device as a baseline when I measure the
> performance of the storage device.  So I was a bit surprised when I saw
> the performance of buffered reads from filesystem is better than the one
> from block device.  That is the reason about this patch for me.

OK.  The lack of readpages for blockdevs has been an outstanding oddity
for a decade or longer - I think it's just that nobody was motivated to
do it because the workload isn't important.

But the implementation looks pretty simple so why not clean it up.

I grabbed the patches.

      reply	other threads:[~2014-08-21 21:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 14:38 [PATCH 0/3] implement readpages() for block device to optimize sequential read Akinobu Mita
2014-08-05 14:38 ` [PATCH 1/3] vfs: make guard_bh_eod() more generic Akinobu Mita
2014-08-05 14:38 ` [PATCH 2/3] vfs: guard end of device for mpage interface Akinobu Mita
2014-08-05 14:38 ` [PATCH 3/3] block_dev: implement readpages() to optimize sequential read Akinobu Mita
2014-08-14 22:04 ` [PATCH 0/3] implement readpages() for block device " Andrew Morton
2014-08-15 17:09   ` Akinobu Mita
2014-08-21 21:44     ` Andrew Morton [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=20140821144412.2a97f2a7400590097f3926de@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=akinobu.mita@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=jmoyer@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).