qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Orit Wasserman <owasserm@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/6] migration: followups for writev patches
Date: Tue, 16 Apr 2013 10:41:47 -0500	[thread overview]
Message-ID: <87zjwyo538.fsf@codemonkey.ws> (raw)
In-Reply-To: <515BE38E.8050505@redhat.com>

Orit Wasserman <owasserm@redhat.com> writes:

> On 03/27/2013 06:36 PM, Paolo Bonzini wrote:
>> This series fixes a few small problems in Orit's writev patches:
>> 
>> 1) socket_put_buffer is not needed anymore and can be dropped (patch 1);
>> 
>> 2) sendmsg could do a partial write even for a blocking socket, in
>> case it is interrupted by a signal. This should not happen for
>> migration, but it is relatively easy to fix in iov_send_recv (patches
>> 2 to 5);
>> 
>> 3) recent libvirt will always use fd migration, and thus will not
>> benefit from the writev speedups.  fd migration also uses FILE*, which
>> incurs an extra copy.  Patch 6 fixes both issues.
>> 
>> Thanks,
>> 
>> Paolo
>> 
>> Paolo Bonzini (6):
>>   qemu-file: drop socket_put_buffer
>>   iov: reorganize iov_send_recv, part 1
>>   iov: reorganize iov_send_recv, part 2
>>   iov: reorganize iov_send_recv, part 3
>>   iov: handle partial writes from sendmsg and recvmsg
>>   qemu-file: do not use stdio for qemu_fdopen
>> 
>>  savevm.c   | 113 ++++++++++++++++++++++++++++++++++++++++++++++++-------------
>>  util/iov.c | 104 ++++++++++++++++++++++++++++++++------------------------
>>  2 files changed, 148 insertions(+), 69 deletions(-)
>> 
> Series
> Reviewed-by: Orit Wasserman <owasserm@redhat.com>

Per Paolo, I will process this through my queue.

Regards,

Anthony Liguori

      reply	other threads:[~2013-04-16 15:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27 16:36 [Qemu-devel] [PATCH 0/6] migration: followups for writev patches Paolo Bonzini
2013-03-27 16:36 ` [Qemu-devel] [PATCH 1/6] qemu-file: drop socket_put_buffer Paolo Bonzini
2013-04-09 13:20   ` Juan Quintela
2013-03-27 16:36 ` [Qemu-devel] [PATCH 2/6] iov: reorganize iov_send_recv, part 1 Paolo Bonzini
2013-04-09 13:18   ` Juan Quintela
2013-03-27 16:36 ` [Qemu-devel] [PATCH 3/6] iov: reorganize iov_send_recv, part 2 Paolo Bonzini
2013-04-09 13:23   ` Juan Quintela
2013-03-27 16:36 ` [Qemu-devel] [PATCH 4/6] iov: reorganize iov_send_recv, part 3 Paolo Bonzini
2013-04-09 13:24   ` Juan Quintela
2013-03-27 16:36 ` [Qemu-devel] [PATCH 5/6] iov: handle partial writes from sendmsg and recvmsg Paolo Bonzini
2013-04-09 13:27   ` Juan Quintela
2013-03-27 16:36 ` [Qemu-devel] [PATCH 6/6] qemu-file: do not use stdio for qemu_fdopen Paolo Bonzini
2013-04-09 13:30   ` Juan Quintela
2013-04-16 21:09   ` Anthony Liguori
2013-04-03  8:08 ` [Qemu-devel] [PATCH 0/6] migration: followups for writev patches Orit Wasserman
2013-04-16 15:41   ` Anthony Liguori [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=87zjwyo538.fsf@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=owasserm@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@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).