All of lore.kernel.org
 help / color / mirror / Atom feed
From: Orit Wasserman <owasserm@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: peter.maydell@linaro.org, aliguori@us.ibm.com,
	quintela@redhat.com, stefanha@gmail.com, qemu-devel@nongnu.org,
	mdroth@linux.vnet.ibm.com, blauwirbel@gmail.com,
	Petter Svard <petters@cs.umu.se>,
	Benoit Hudzia <benoit.hudzia@sap.com>,
	avi@redhat.com, Aidan Shribman <aidan.shribman@sap.com>,
	pbonzini@redhat.com, chegu_vinod@hp.com
Subject: Re: [Qemu-devel] [PATCH v16 8/9] Add set_cachesize command
Date: Tue, 10 Jul 2012 08:15:40 +0300	[thread overview]
Message-ID: <4FFBBA7C.6030609@redhat.com> (raw)
In-Reply-To: <4FFB4630.8010209@redhat.com>

On 07/09/2012 11:59 PM, Eric Blake wrote:
> On 07/09/2012 12:22 PM, Orit Wasserman wrote:
>> Change XBZRLE cache size in bytes (the size should be a power of 2).
>> If XBZRLE cache size is too small there will be many cache miss.
>>
>> Signed-off-by: Benoit Hudzia <benoit.hudzia@sap.com>
>> Signed-off-by: Petter Svard <petters@cs.umu.se>
>> Signed-off-by: Aidan Shribman <aidan.shribman@sap.com>
>> Signed-off-by: Orit Wasserman <owasserm@redhat.com>
> 
>> +++ b/qapi-schema.json
>> @@ -1390,6 +1390,22 @@
>>  { 'command': 'migrate_set_speed', 'data': {'value': 'int'} }
> 
> We are copying after bad practice, but...
> 
>>  
>>  ##
>> +# @migrate_set_cachesize
> 
> ...new QMP commands should prefer '-' over '_'.  While the HMP version
> is fine with migrate_set_cachesize, the QMP command should be
> migrate-set-cachesize (or even 'migrate-set-cache-size').
> 
I will change it
Thanks,
Orit
> 
>> +
>> +Set cache size to be used by XBZRLE migration, the cache size will be round down
> 
> s/round/rounded/
> 

  reply	other threads:[~2012-07-10  5:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-09 18:22 [Qemu-devel] [PATCH v16 0/9] XBZRLE delta for live migration of large memory app Orit Wasserman
2012-07-09 18:22 ` [Qemu-devel] [PATCH v16 1/9] Add migration capabilities Orit Wasserman
2012-07-09 18:22 ` [Qemu-devel] [PATCH v16 2/9] Add XBZRLE documentation Orit Wasserman
2012-07-09 18:22 ` [Qemu-devel] [PATCH v16 3/9] Add cache handling functions Orit Wasserman
2012-07-09 18:22 ` [Qemu-devel] [PATCH v16 4/9] Add uleb encoding/decoding functions Orit Wasserman
2012-07-09 18:22 ` [Qemu-devel] [PATCH v16 5/9] Change ram_save_block to return -1 if there are no more changes Orit Wasserman
2012-07-09 18:22 ` [Qemu-devel] [PATCH v16 6/9] Add xbzrle_encode_buffer and xbzrle_decode_buffer functions Orit Wasserman
2012-07-09 18:22 ` [Qemu-devel] [PATCH v16 7/9] Add XBZRLE to ram_save_block and ram_save_live Orit Wasserman
2012-07-09 18:22 ` [Qemu-devel] [PATCH v16 8/9] Add set_cachesize command Orit Wasserman
2012-07-09 20:59   ` Eric Blake
2012-07-10  5:15     ` Orit Wasserman [this message]
2012-07-09 18:22 ` [Qemu-devel] [PATCH v16 9/9] Add XBZRLE statistics 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=4FFBBA7C.6030609@redhat.com \
    --to=owasserm@redhat.com \
    --cc=aidan.shribman@sap.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=benoit.hudzia@sap.com \
    --cc=blauwirbel@gmail.com \
    --cc=chegu_vinod@hp.com \
    --cc=eblake@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=petters@cs.umu.se \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=stefanha@gmail.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.