qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/4] block: Vectored bdrv_writev_vmstate
Date: Tue, 9 Apr 2013 10:04:38 +0200	[thread overview]
Message-ID: <20130409080438.GA2922@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <5162EDD2.1030304@redhat.com>

Am 08.04.2013 um 18:18 hat Paolo Bonzini geschrieben:
> Il 08/04/2013 18:03, Stefan Hajnoczi ha scritto:
> > Looks fine on the block side.  Perhaps Orit, Juan, or Paolo can
> > double-check the migration side.
> > 
> > Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
> 
> Looks good, but given there are patches to fix it, I'm not sure it's
> worth the trouble...

Shouldn't this perform even a little better? And we should get rid of
non-vectored interfaces in the block layer anyway.

Kevin

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-05 19:27 [Qemu-devel] [PATCH 0/4] block: Vectored bdrv_writev_vmstate Kevin Wolf
2013-04-05 19:27 ` [Qemu-devel] [PATCH 1/4] block: Introduce bdrv_writev_vmstate Kevin Wolf
2013-04-05 19:27 ` [Qemu-devel] [PATCH 2/4] savevm: Implement block_writev_buffer() Kevin Wolf
2013-04-05 19:27 ` [Qemu-devel] [PATCH 3/4] block: Introduce bdrv_pwritev() for qcow2_save_vmstate Kevin Wolf
2013-04-05 19:27 ` [Qemu-devel] [PATCH 4/4] qemu-iotests: A few more bdrv_pread/pwrite tests Kevin Wolf
2013-04-08 16:03 ` [Qemu-devel] [PATCH 0/4] block: Vectored bdrv_writev_vmstate Stefan Hajnoczi
2013-04-08 16:18   ` Paolo Bonzini
2013-04-09  8:04     ` Kevin Wolf [this message]
2013-04-09  8:08       ` Paolo Bonzini
2013-04-09  8:30         ` Stefan Hajnoczi
2013-04-09 12:30 ` Stefan Hajnoczi

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=20130409080438.GA2922@dhcp-200-207.str.redhat.com \
    --to=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.com \
    /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).