linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jan Kara <jack@suse.cz>,
	linux-fsdevel@vger.kernel.org, Kazuya Mio <k-mio@sx.jp.nec.com>
Subject: Re: [PATCH] direct-io: Submit bio after boundary buffer is added to it
Date: Tue, 9 Apr 2013 22:55:56 +0200	[thread overview]
Message-ID: <20130409205556.GC15214@quack.suse.cz> (raw)
In-Reply-To: <20130409134758.fc074bcfda430b0ce6508d06@linux-foundation.org>

On Tue 09-04-13 13:47:58, Andrew Morton wrote:
> On Tue,  9 Apr 2013 17:42:49 +0200 Jan Kara <jack@suse.cz> wrote:
> 
> > Currently, dio_send_cur_page() submits bio before current page and
> > cached sdio->cur_page is added to the bio if sdio->boundary is set. This
> > is actually wrong because sdio->boundary means the current buffer is the
> > last one before metadata needs to be read. So we should rather submit
> > the bio after the current page is added to it.
> > 
> > Reported-by: Kazuya Mio <k-mio@sx.jp.nec.com>
> > Signed-off-by: Jan Kara <jack@suse.cz>
> > ---
> >  fs/direct-io.c |   28 +++++++++++-----------------
> >  1 files changed, 11 insertions(+), 17 deletions(-)
> > 
> >  Andrew, can you add this patch the previous direct IO boundary handling fix?
> 
> What is the user-visible impact of these two patches?
  I've measured about 10% throughput improvement of direct IO reads on ext3
with SATA harddrive (from 90 MB/s to 100 MB/s) with these patches applied.
With ramdisk, the improvement was about 3-fold (from 350 MB/s to 1.2 GB/s).
For other filesystems (such as ext4), the improvements won't be as visible
because the frequency of BH_Boundary flag being set is much smaller...

								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

      reply	other threads:[~2013-04-09 20:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09 15:42 [PATCH] direct-io: Submit bio after boundary buffer is added to it Jan Kara
2013-04-09 20:47 ` Andrew Morton
2013-04-09 20:55   ` Jan Kara [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=20130409205556.GC15214@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=k-mio@sx.jp.nec.com \
    --cc=linux-fsdevel@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).