From: Wei Yang <richard.weiyang@gmail.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: quintela@redhat.com, Wei Yang <richardw.yang@linux.intel.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] migration/xbzrle: cleanup the handling cache miss condition
Date: Sun, 9 Jun 2019 19:49:45 +0000 [thread overview]
Message-ID: <20190609194945.hpovxgad75565hlw@master> (raw)
In-Reply-To: <20190607190114.GA2631@work-vm>
On Fri, Jun 07, 2019 at 08:01:14PM +0100, Dr. David Alan Gilbert wrote:
>* Wei Yang (richardw.yang@linux.intel.com) wrote:
>> For cache miss condition not in last_stage, we need to insert data into
>> cache. When this step succeed, current_data should be updated. While no
>> matter these checks pass or not, -1 is returned.
>>
>> Based on this, the logic in cache miss handling could be simplified a
>> little.
>>
>> Signed-off-by: Wei Yang <richardw.yang@linux.intel.com>
>> ---
>> migration/ram.c | 17 ++++++++---------
>> 1 file changed, 8 insertions(+), 9 deletions(-)
>>
>> diff --git a/migration/ram.c b/migration/ram.c
>> index 878cd8de7a..67ba075cc4 100644
>> --- a/migration/ram.c
>> +++ b/migration/ram.c
>> @@ -1572,15 +1572,14 @@ static int save_xbzrle_page(RAMState *rs, uint8_t **current_data,
>> if (!cache_is_cached(XBZRLE.cache, current_addr,
>> ram_counters.dirty_sync_count)) {
>> xbzrle_counters.cache_miss++;
>> - if (!last_stage) {
>> - if (cache_insert(XBZRLE.cache, current_addr, *current_data,
>> - ram_counters.dirty_sync_count) == -1) {
>> - return -1;
>> - } else {
>> - /* update *current_data when the page has been
>> - inserted into cache */
>> - *current_data = get_cached_data(XBZRLE.cache, current_addr);
>> - }
>> + if (!last_stage &&
>> + !cache_insert(XBZRLE.cache, current_addr, *current_data,
>> + ram_counters.dirty_sync_count)) {
>> + /*
>> + * update *current_data when the page has been inserted into
>> + * cache
>> + */
>> + *current_data = get_cached_data(XBZRLE.cache, current_addr);
>
>No this change doesn't gain anything and I find the original easier to
>read.
>
>This function is really subtle, every time I do anything with it I have
>to think really hard about it, so ease of reading is more important.
>
Yep, I agree ease of reading is more important.
Since the original version looks better, I will keep current code. :-)
>Dave
>
>> }
>> return -1;
>> }
>> --
>> 2.19.1
>>
>--
>Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
--
Wei Yang
Help you, Help me
prev parent reply other threads:[~2019-06-09 19:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 1:31 [Qemu-devel] [PATCH 0/2] xbzrle: improve readability a little Wei Yang
2019-06-06 1:31 ` [Qemu-devel] [PATCH 1/2] migration/xbzrle: update cache and current_data in one place Wei Yang
2019-06-07 18:57 ` Dr. David Alan Gilbert
2019-06-09 19:46 ` Wei Yang
2019-06-06 1:31 ` [Qemu-devel] [PATCH 2/2] migration/xbzrle: cleanup the handling cache miss condition Wei Yang
2019-06-07 19:01 ` Dr. David Alan Gilbert
2019-06-09 19:49 ` Wei Yang [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=20190609194945.hpovxgad75565hlw@master \
--to=richard.weiyang@gmail.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=richardw.yang@linux.intel.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).