From: Orit Wasserman <owasserm@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: mst@redhat.com, chegu_vinod@hp.com, qemu-devel@nongnu.org,
quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 5/8] Use writev ops if available
Date: Thu, 21 Mar 2013 15:52:34 +0200 [thread overview]
Message-ID: <514B10A2.2030502@redhat.com> (raw)
In-Reply-To: <514B0EDB.10808@redhat.com>
On 03/21/2013 03:44 PM, Paolo Bonzini wrote:
> Il 21/03/2013 14:23, Orit Wasserman ha scritto:
>> Update qemu_fflush and stdio_close to use writev ops if they are available
>>
>> Signed-off-by: Orit Wasserman <owasserm@redhat.com>
>> ---
>> savevm.c | 30 ++++++++++++++++++++----------
>> 1 file changed, 20 insertions(+), 10 deletions(-)
>>
>> diff --git a/savevm.c b/savevm.c
>> index ab81dd3..fde59d3 100644
>> --- a/savevm.c
>> +++ b/savevm.c
>> @@ -292,7 +292,7 @@ static int stdio_fclose(void *opaque)
>> QEMUFileStdio *s = opaque;
>> int ret = 0;
>>
>> - if (s->file->ops->put_buffer) {
>> + if (s->file->ops->put_buffer || s->file->ops->writev_buffer) {
>> int fd = fileno(s->stdio_file);
>> struct stat st;
>>
>> @@ -515,24 +515,34 @@ static void qemu_file_set_error(QEMUFile *f, int ret)
>> }
>> }
>>
>> -/** Flushes QEMUFile buffer
>> +/**
>> + * Flushes QEMUFile buffer
>> *
>> + * If there is writev_buffer QEMUFileOps it uses it otherwise uses
>> + * put_buffer ops.
>> */
>> static void qemu_fflush(QEMUFile *f)
>> {
>> int ret = 0;
>>
>> - if (!f->ops->put_buffer) {
>> + if (f->ops->writev_buffer) {
>> + if (f->is_write && f->iovcnt > 0) {
>> + ret = f->ops->writev_buffer(f->opaque, f->iov, f->iovcnt);
>
> This needs to update f->pos.
>
>> + }
>> + } else if (f->ops->put_buffer) {
>> + if (f->is_write && f->buf_index > 0) {
>> + ret = f->ops->put_buffer(f->opaque, f->buf, f->pos, f->buf_index);
>> + }
>
> I think this has to go through all the iovecs (i.e. never look at
> f->buf_index, only f->iovcnt). Otherwise RAM migration does not work,
> because the page data is not copied to f->buf. But that's pretty much
> it, the series looks good.
You are right I will fix it.
>
> However, I'd still prefer to have qemu_put_buffer_no_copy coalesce
> adjacent iovecs. Otherwise you might end up with only 3-400 bytes in
> each sendmsg when serializing device data.
Yes this will be helpful for the device state.
Orit
>
> Paolo
>
>> + } else {
>> return;
>> }
>> - if (f->is_write && f->buf_index > 0) {
>> - ret = f->ops->put_buffer(f->opaque, f->buf, f->pos, f->buf_index);
>> - if (ret >= 0) {
>> - f->pos += f->buf_index;
>> - }
>> - f->buf_index = 0;
>> - f->iovcnt = 0;
>> +
>> + if (ret >= 0) {
>> + f->pos += f->buf_index;
>> }
>> + f->buf_index = 0;
>> + f->iovcnt = 0;
>> +
>> if (ret < 0) {
>> qemu_file_set_error(f, ret);
>> }
>>
>
next prev parent reply other threads:[~2013-03-21 13:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 13:23 [Qemu-devel] [PATCH v2 0/8] Migration: Remove copying of guest ram pages Orit Wasserman
2013-03-21 13:23 ` [Qemu-devel] [PATCH v2 1/8] Add QemuFileWritevBuffer QemuFileOps Orit Wasserman
2013-03-21 13:23 ` [Qemu-devel] [PATCH v2 2/8] Add socket_writev_buffer function Orit Wasserman
2013-03-21 13:23 ` [Qemu-devel] [PATCH v2 3/8] Update bytes_xfer in qemu_put_byte Orit Wasserman
2013-03-21 13:23 ` [Qemu-devel] [PATCH v2 4/8] Store the data to send also in iovec Orit Wasserman
2013-03-21 13:23 ` [Qemu-devel] [PATCH v2 5/8] Use writev ops if available Orit Wasserman
2013-03-21 13:44 ` Paolo Bonzini
2013-03-21 13:52 ` Orit Wasserman [this message]
2013-03-21 13:23 ` [Qemu-devel] [PATCH v2 6/8] More optimized qemu_put_be64/32/16 Orit Wasserman
2013-03-21 13:23 ` [Qemu-devel] [PATCH v2 7/8] Add qemu_put_buffer_no_copy Orit Wasserman
2013-03-21 13:23 ` [Qemu-devel] [PATCH v2 8/8] Use qemu_put_buffer_no_copy for guest memory pages Orit Wasserman
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=514B10A2.2030502@redhat.com \
--to=owasserm@redhat.com \
--cc=chegu_vinod@hp.com \
--cc=mst@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).