All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gonglei <arei.gonglei@huawei.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: "chenliang (T)" <chenliang88@huawei.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	Juan Quintela <quintela@redhat.com>, "pl@kamp.de" <pl@kamp.de>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"aliguori@amazon.com" <aliguori@amazon.com>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 6/7] migraion: optimiztion xbzrle by reducing data copy
Date: Fri, 28 Feb 2014 19:06:53 +0800	[thread overview]
Message-ID: <53106DCD.9000806@huawei.com> (raw)
In-Reply-To: <20140228103022.GG2695@work-vm>

On 2014/2/28 18:30, Dr. David Alan Gilbert wrote:

> * Gonglei (Arei) (arei.gonglei@huawei.com) wrote:
>> Reducing data copy can reduce cpu overheah.
> 
> (Note a few typos in subject/title)
> 
>> Signed-off-by: ChenLiang <chenliang88@huawei.com>
>> Signed-off-by: Gonglei <arei.gonglei@huawei.com>
>> ---
>>  arch_init.c | 8 +++-----
>>  1 file changed, 3 insertions(+), 5 deletions(-)
>>
>> diff --git a/arch_init.c b/arch_init.c
>> index 2211e0b..cc88875 100644
>> --- a/arch_init.c
>> +++ b/arch_init.c
>> @@ -344,11 +344,8 @@ static int save_xbzrle_page(QEMUFile *f, uint8_t **current_data,
>>  
>>      prev_cached_page = get_cached_data(XBZRLE.cache, current_addr);
>>  
>> -    /* save current buffer into memory */
>> -    memcpy(XBZRLE.current_buf, *current_data, TARGET_PAGE_SIZE);
>> -
>>      /* XBZRLE encoding (if there is no overflow) */
>> -    encoded_len = xbzrle_encode_buffer(prev_cached_page, XBZRLE.current_buf,
>> +    encoded_len = xbzrle_encode_buffer(prev_cached_page, *current_data,
>>                                         TARGET_PAGE_SIZE, XBZRLE.encoded_buf,
>>                                         TARGET_PAGE_SIZE);
> 
> Is xbzrle_encode_buffer safe if the main memory is still being changed while
> it is run? Even with multiple CPUs changing it? Even on CPUs with looser
> memory ordering semantics?
> 

It's OK. We just need to assure the pages of cache and the pages which be sent coherence.

>>      if (encoded_len == 0) {
>> @@ -367,7 +364,8 @@ static int save_xbzrle_page(QEMUFile *f, uint8_t **current_data,
>>  
>>      /* we need to update the data in the cache, in order to get the same data */
>>      if (!last_stage) {
>> -        memcpy(prev_cached_page, XBZRLE.current_buf, TARGET_PAGE_SIZE);
>> +        xbzrle_decode_buffer(XBZRLE.encoded_buf, encoded_len, prev_cached_page,
>> +                                                              TARGET_PAGE_SIZE);
>>      }
>>  
>>      /* Send XBZRLE based compressed page */
>> -- 
>> 1.7.12.4
>>
>>
>> Best regards,
>> -Gonglei
>>
>>
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK


Best regards,
-Gonglei

      reply	other threads:[~2014-02-28 11:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-28  4:11 [Qemu-devel] [PATCH 6/7] migraion: optimiztion xbzrle by reducing data copy Gonglei (Arei)
2014-02-28 10:30 ` Dr. David Alan Gilbert
2014-02-28 11:06   ` Gonglei [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=53106DCD.9000806@huawei.com \
    --to=arei.gonglei@huawei.com \
    --cc=aliguori@amazon.com \
    --cc=chenliang88@huawei.com \
    --cc=dgilbert@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=pl@kamp.de \
    --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.