qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Cody <jcody@redhat.com>
To: Peter Lieven <pl@kamp.de>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, kwolf@redhat.com,
	mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/2] block/nfs: try to avoid the bounce buffer in pwritev
Date: Fri, 17 Feb 2017 16:37:15 -0500	[thread overview]
Message-ID: <20170217213715.GJ19045@localhost.localdomain> (raw)
In-Reply-To: <1487349541-10201-3-git-send-email-pl@kamp.de>

On Fri, Feb 17, 2017 at 05:39:01PM +0100, Peter Lieven wrote:
> if the passed qiov contains exactly one iov we can
> pass the buffer directly.
> 
> Signed-off-by: Peter Lieven <pl@kamp.de>
> ---
>  block/nfs.c | 23 ++++++++++++++++-------
>  1 file changed, 16 insertions(+), 7 deletions(-)
> 
> diff --git a/block/nfs.c b/block/nfs.c
> index ab5dcc2..bb4b75f 100644
> --- a/block/nfs.c
> +++ b/block/nfs.c
> @@ -295,20 +295,27 @@ static int coroutine_fn nfs_co_pwritev(BlockDriverState *bs, uint64_t offset,
>      NFSClient *client = bs->opaque;
>      NFSRPC task;
>      char *buf = NULL;
> +    bool my_buffer = false;

g_free() is a nop if buf is NULL, so there is no need for the my_buffer
variable & check.

>  
>      nfs_co_init_task(bs, &task);
>  
> -    buf = g_try_malloc(bytes);
> -    if (bytes && buf == NULL) {
> -        return -ENOMEM;
> +    if (iov->niov != 1) {
> +        buf = g_try_malloc(bytes);
> +        if (bytes && buf == NULL) {
> +            return -ENOMEM;
> +        }
> +        qemu_iovec_to_buf(iov, 0, buf, bytes);
> +        my_buffer = true;
> +    } else {
> +        buf = iov->iov[0].iov_base;
>      }
>  
> -    qemu_iovec_to_buf(iov, 0, buf, bytes);
> -
>      if (nfs_pwrite_async(client->context, client->fh,
>                           offset, bytes, buf,
>                           nfs_co_generic_cb, &task) != 0) {
> -        g_free(buf);
> +        if (my_buffer) {
> +            g_free(buf);
> +        }
>          return -ENOMEM;
>      }
>  
> @@ -317,7 +324,9 @@ static int coroutine_fn nfs_co_pwritev(BlockDriverState *bs, uint64_t offset,
>          qemu_coroutine_yield();
>      }
>  
> -    g_free(buf);
> +    if (my_buffer) {
> +        g_free(buf);
> +    }
>  
>      if (task.ret != bytes) {
>          return task.ret < 0 ? task.ret : -EIO;
> -- 
> 1.9.1
> 

  reply	other threads:[~2017-02-17 21:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17 16:38 [Qemu-devel] [PATCH 0/2] block/nfs optimizations Peter Lieven
2017-02-17 16:39 ` [Qemu-devel] [PATCH 1/2] block/nfs: convert to preadv / pwritev Peter Lieven
2017-02-17 21:33   ` Jeff Cody
2017-02-17 16:39 ` [Qemu-devel] [PATCH 2/2] block/nfs: try to avoid the bounce buffer in pwritev Peter Lieven
2017-02-17 21:37   ` Jeff Cody [this message]
2017-02-17 21:42     ` Eric Blake
2017-02-17 21:51       ` Jeff Cody
2017-02-22 12:47         ` Kevin Wolf
2017-02-22 12:48           ` Jeff Cody
2017-02-24  3:50 ` [Qemu-devel] [PATCH 0/2] block/nfs optimizations Jeff Cody

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=20170217213715.GJ19045@localhost.localdomain \
    --to=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=pl@kamp.de \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.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).