From: David Hildenbrand <david@redhat.com>
To: Eric Ren <renzhengeek@gmail.com>, linux-kernel@vger.kernel.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>, Zi Yan <ziy@nvidia.com>,
Gavin Shan <gshan@redhat.com>, Hui Zhu <teawater@gmail.com>,
Sebastien Boeuf <sebastien.boeuf@intel.com>,
Pankaj Gupta <pankaj.gupta.linux@gmail.com>,
Wei Yang <richard.weiyang@linux.alibaba.com>,
virtualization@lists.linux-foundation.org, linux-mm@kvack.org
Subject: Re: [PATCH v1 2/2] virtio-mem: prepare fake page onlining code for granularity smaller than MAX_ORDER - 1
Date: Thu, 9 Dec 2021 12:52:56 +0100 [thread overview]
Message-ID: <858b3185-6770-6c46-5efb-53698c913eec@redhat.com> (raw)
In-Reply-To: <a4e2099d-b543-e2e3-f189-0cdfcc38420e@gmail.com>
Hi Eric,
thanks for the review!
>> if (PageDirty(page)) {
>> - virtio_mem_clear_fake_offline(pfn + i, max_nr_pages,
>> - false);
>> - generic_online_page(page, MAX_ORDER - 1);
>> + virtio_mem_clear_fake_offline(pfn + i, 1 << order, false);
>> + generic_online_page(page, order);
>> } else {
>> - virtio_mem_clear_fake_offline(pfn + i, max_nr_pages,
>> - true);
>> - free_contig_range(pfn + i, max_nr_pages);
>> - adjust_managed_page_count(page, max_nr_pages);
>> + virtio_mem_clear_fake_offline(pfn + i, 1 << order, true);
>> + free_contig_range(pfn + i, 1 << order);
>> + adjust_managed_page_count(page, 1 << order);
> In the loop, pfn + i, 1 << order are repeatedly calculated. 1 << order
> is a step size, pfn + i is each step position.
> Better to figure the numer once each iter?
The compiler better be smart enough to calculate such constants once :)
>
> LGTL.
> LGTM.
> Reviewed-by: Eric Ren <renzhengeek@gmail.com>
Thanks!
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2021-12-09 11:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 13:42 [PATCH v1 0/2] virtio-mem: prepare " David Hildenbrand
2021-11-26 13:42 ` [PATCH v1 1/2] virtio-mem: prepare page onlining code " David Hildenbrand
2021-12-09 11:26 ` Eric Ren
2021-11-26 13:42 ` [PATCH v1 2/2] virtio-mem: prepare fake " David Hildenbrand
2021-12-09 11:51 ` Eric Ren
2021-12-09 11:52 ` David Hildenbrand [this message]
2021-11-29 16:47 ` [PATCH v1 0/2] virtio-mem: prepare " Zi Yan
2021-11-30 14:51 ` David Hildenbrand
2021-11-30 23:56 ` Michael S. Tsirkin
2021-12-01 8:24 ` David Hildenbrand
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=858b3185-6770-6c46-5efb-53698c913eec@redhat.com \
--to=david@redhat.com \
--cc=gshan@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mst@redhat.com \
--cc=pankaj.gupta.linux@gmail.com \
--cc=renzhengeek@gmail.com \
--cc=richard.weiyang@linux.alibaba.com \
--cc=sebastien.boeuf@intel.com \
--cc=teawater@gmail.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=ziy@nvidia.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