All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: quintela@redhat.com
Cc: kwolf@redhat.com, owasserm@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/4] migration: set f->is_write and flush in add_to_iovec
Date: Tue, 09 Apr 2013 13:39:34 +0200	[thread overview]
Message-ID: <5163FDF6.1080600@redhat.com> (raw)
In-Reply-To: <87hajgdjmt.fsf@elfo.elfo>

Il 09/04/2013 13:32, Juan Quintela ha scritto:
> Paolo Bonzini <pbonzini@redhat.com> wrote:
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> ---
>>  savevm.c | 25 +++++++++----------------
>>  1 file changed, 9 insertions(+), 16 deletions(-)
>>
>> diff --git a/savevm.c b/savevm.c
>> index b1d8988..c952c41 100644
>> --- a/savevm.c
>> +++ b/savevm.c
>> @@ -631,6 +631,11 @@ static void add_to_iovec(QEMUFile *f, const uint8_t *buf, int size)
>>          f->iov[f->iovcnt].iov_base = (uint8_t *)buf;
>>          f->iov[f->iovcnt++].iov_len = size;
>>      }
>> +
>> +    f->is_write = 1;
>> +    if (f->buf_index >= IO_BUF_SIZE || f->iovcnt >= MAX_IOV_SIZE) {
>> +        qemu_fflush(f);
>> +    }
>>  }
>>  
>>  void qemu_put_buffer_async(QEMUFile *f, const uint8_t *buf, int size)
>> @@ -645,14 +650,8 @@ void qemu_put_buffer_async(QEMUFile *f, const uint8_t *buf, int size)
>>          abort();
>>      }
>>  
>> -    add_to_iovec(f, buf, size);
>> -
>> -    f->is_write = 1;
>>      f->bytes_xfer += size;
>> -
>> -    if (f->buf_index >= IO_BUF_SIZE || f->iovcnt >= MAX_IOV_SIZE) {
>> -        qemu_fflush(f);
>> -    }
>> +    add_to_iovec(f, buf, size);
>>  }
>>  
>>  void qemu_put_buffer(QEMUFile *f, const uint8_t *buf, int size)
>> @@ -674,7 +673,6 @@ void qemu_put_buffer(QEMUFile *f, const uint8_t *buf, int size)
>>          if (l > size)
>>              l = size;
>>          memcpy(f->buf + f->buf_index, buf, l);
>> -        f->is_write = 1;
>>          f->buf_index += l;
> 
> we increase buf_index
> 
>>          qemu_put_buffer_async(f, f->buf + (f->buf_index - l), l);
> 
> and we call add_to_iovec() here inside.  Notice the torture to get the
> old buf_index value.
> 
>>          if (qemu_file_get_error(f)) {
>> @@ -697,15 +695,10 @@ void qemu_put_byte(QEMUFile *f, int v)
>>          abort();
>>      }
>>  
>> -    f->buf[f->buf_index++] = v;
>> -    f->is_write = 1;
>> +    f->buf[f->buf_index] = v;
>>      f->bytes_xfer++;
>> -
>> -    add_to_iovec(f, f->buf + (f->buf_index - 1), 1);
>> -
>> -    if (f->buf_index >= IO_BUF_SIZE || f->iovcnt >= MAX_IOV_SIZE) {
>> -        qemu_fflush(f);
>> -    }
>> +    add_to_iovec(f, f->buf + f->buf_index, 1);
>> +    f->buf_index++;
> 
> And here,  we call add_to_iovec() and then increase buf_index
> 
> Is there any good reason for not being consistent?

The reason is that I didn't want to switch
qemu_put_buffer_async->add_to_iovec in this patch.  I do it in the next one.

> Once there,  I think that moving the handling of buf_index to inside
> add_to_iovec() looks like a good idea?

add_to_iovec() is not called always with something from f->buf.  But it
is a good idea to move this handling of buf_index:

    if (f->buf_index >= IO_BUF_SIZE || f->iovcnt >= MAX_IOV_SIZE) {

out of add_to_iovec.  I do that in patch 4.

Paolo

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

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 11:29 [Qemu-devel] [PATCH 0/4] QEMUFile improvements and simplifications Paolo Bonzini
2013-04-08 11:29 ` [Qemu-devel] [PATCH 1/4] migration: set f->is_write and flush in add_to_iovec Paolo Bonzini
2013-04-09 11:32   ` Juan Quintela
2013-04-09 11:39     ` Paolo Bonzini [this message]
2013-04-08 11:29 ` [Qemu-devel] [PATCH 2/4] migration: use a single I/O operation when writev_buffer is not defined Paolo Bonzini
2013-04-09 11:38   ` Juan Quintela
2013-04-09 11:42     ` Paolo Bonzini
2013-04-08 11:29 ` [Qemu-devel] [PATCH 3/4] migration: drop is_write complications Paolo Bonzini
2013-04-09 11:42   ` Juan Quintela
2013-04-09 11:55     ` Paolo Bonzini
2013-04-09 12:17       ` Juan Quintela
2013-04-09 12:25         ` Paolo Bonzini
2013-04-08 11:29 ` [Qemu-devel] [PATCH 4/4] migration: simplify writev vs. non-writev logic Paolo Bonzini
2013-04-09 11:43   ` Juan Quintela
2013-04-09 11:53     ` Paolo Bonzini
2013-04-09 12:16       ` Juan Quintela
2013-04-09 12:22       ` Orit Wasserman
2013-04-09 12:58 ` [Qemu-devel] [PATCH 0/4] QEMUFile improvements and simplifications Juan Quintela
2013-04-10 12:48 ` Liuji (Jeremy)
2013-04-10 12:53   ` Paolo Bonzini
2013-04-10 18:29     ` Juan Quintela
2013-04-11 12:35     ` Liuji (Jeremy)
2013-04-10 12:55   ` Juan Quintela
2013-04-11 12:38     ` Liuji (Jeremy)

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=5163FDF6.1080600@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=owasserm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.