linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: majianpeng <majianpeng@gmail.com>
Cc: viro <viro@ZenIV.linux.org.uk>,
	linux-raid <linux-raid@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	axboe@fusionio.com
Subject: Re: [PATCH 1/2] fs/block-dev.c:fix performance regression in O_DIRECT writes to md block devices.
Date: Mon, 16 Jul 2012 15:21:16 +1000	[thread overview]
Message-ID: <20120716152116.725e5db6@notabene.brown> (raw)
In-Reply-To: <201207160930466402203@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1973 bytes --]

On Mon, 16 Jul 2012 09:30:50 +0800 majianpeng <majianpeng@gmail.com> wrote:

> For regular file, write operaion used blk_plug function.But for block
> file,write operation did not use blk_plug.
> 
> Signed-off-by: Jianpeng Ma <majianpeng@gmail.com>
> ---
>  fs/block_dev.c |    7 ++++++-
>  1 files changed, 6 insertions(+), 1 deletions(-)
> 
> diff --git a/fs/block_dev.c b/fs/block_dev.c
> index c2bbe1f..22cd436 100644
> --- a/fs/block_dev.c
> +++ b/fs/block_dev.c
> @@ -215,9 +215,14 @@ blkdev_direct_IO(int rw, struct kiocb *iocb, const struct iovec *iov,
>  {
>  	struct file *file = iocb->ki_filp;
>  	struct inode *inode = file->f_mapping->host;
> +	struct blk_plug plug;
> +	ssize_t ret;
>  
> -	return __blockdev_direct_IO(rw, iocb, inode, I_BDEV(inode), iov, offset,
> +	blk_start_plug(&plug);
> +	ret =  __blockdev_direct_IO(rw, iocb, inode, I_BDEV(inode), iov, offset,
>  				    nr_segs, blkdev_get_blocks, NULL, NULL, 0);
> +	blk_finish_plug(&plug);
> +	return ret;
>  }
>  
>  int __sync_blockdev(struct block_device *bdev, int wait)

[cc:ing Jens Axboe]

I think we do need something like this, but I don't think this is the right
place for it.

For normal filesystem writes, the blk_{start,finish}_plug calls are in
generic_file_aio_write which is the "aio_write" function, or is called by it.
aio_write calls generic_file_aio_write, calls blk_start_plug, call
__generic_file_aio_write.

For block devices we bypass the generic_file_aio_write:

aio_write calls blkdev_aio_write calls __generic_file_aio_write - without
calling blk_start_plug.
So I think the calls to blk_start_plug and blk_finish_plug should go in
blkdev_aio_write.  i.e. blkdev_aio_write should be made to look more like
generic_file_aio_write (just without the mutex_lock/unlock).

If you redo the patch like that and test it I'll happily add my Reviewed-by.

I suspect it should be merged through Jens' tree.

Thanks,
NeilBrown


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2012-07-16  5:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-16  1:30 [PATCH 1/2] fs/block-dev.c:fix performance regression in O_DIRECT writes to md block devices majianpeng
2012-07-16  5:21 ` NeilBrown [this message]
2012-07-16  5:30   ` majianpeng

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=20120716152116.725e5db6@notabene.brown \
    --to=neilb@suse.de \
    --cc=axboe@fusionio.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=majianpeng@gmail.com \
    --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).