On 25.02.20 22:46, Alexander Duyck wrote:
> On Tue, 2020-02-25 at 19:49 +0100, David Hildenbrand wrote:
>>>> /*
>>>> * Scan pfn range [start,end) to find movable/migratable pages (LRU pages,
>>>> - * non-lru movable pages and hugepages). We scan pfn because it's much
>>>> - * easier than scanning over linked list. This function returns the pfn
>>>> - * of the first found movable page if it's found, otherwise 0.
>>>> + * non-lru movable pages and hugepages).
>>>> + *
>>>> + * Returns:
>>>> + * 0 in case a movable page is found and movable_pfn was updated.
>>>> + * -ENOENT in case no movable page was found.
>>>> + * -EBUSY in case a definetly unmovable page was found.
>>>> */
>>>> -static unsigned long scan_movable_pages(unsigned long start, unsigned long end)
>>>> +static int scan_movable_pages(unsigned long start, unsigned long end,
>>>> + unsigned long *movable_pfn)
>>>> {
>>>> unsigned long pfn;
>>>>
>>>> @@ -1247,18 +1251,29 @@ static unsigned long scan_movable_pages(unsigned long start, unsigned long end)
>>>> continue;
>>>> page = pfn_to_page(pfn);
>>>> if (PageLRU(page))
>>>> - return pfn;
>>>> + goto found;
>>>> if (__PageMovable(page))
>>>> - return pfn;
>>>> + goto found;
>>>> +
>>>> + /*
>>>> + * Unmovable PageOffline() pages where somebody still holds
>>>> + * a reference count (after MEM_GOING_OFFLINE) can definetly
>>>> + * not be offlined.
>>>> + */
>>>> + if (PageOffline(page) && page_count(page))
>>>> + return -EBUSY;
>>>
>>> So the comment confused me a bit because technically this function isn't
>>> about offlining memory, it is about finding movable pages. I had to do a
>>> bit of digging to find the only consumer is __offline_pages, but if we are
>>> going to talk about "offlining" instead of "moving" in this function it
>>> might make sense to rename it.
>>
>> Well, it's contained in memory_hotplug.c, and the only user of moving
>> pages around in there is offlining code :) And it's job is to locate
>> movable pages, skip over some (temporary? unmovable ones) and (now)
>> indicate definitely unmovable ones.
>>
>> Any idea for a better name?
>> scan_movable_pages_and_stop_on_definitely_unmovable() is not so nice :)
>
> I dunno. What I was getting at is that the wording here would make it
> clearer if you simply stated that these pages "can definately not be
> moved". Saying you cannot offline a page that is PageOffline seems kind of
> redundant, then again calling it an Unmovable and then saying it cannot be
> moves is also redundant I suppose. In the end you don't move them, but
So, in summary, there are
- PageOffline() pages that are movable (balloon compaction).
- PageOffline() pages that cannot be moved and cannot be offlined (e.g.,
no balloon compaction enabled, XEN, HyperV, ...) . page_count(page) >=
0
- PageOffline() pages that cannot be moved, but can be offlined.
page_count(page) == 0.
> they can be switched to offline if the page count hits 0. When that
> happens you simply end up skipping over them in the code for
> __test_page_isolated_in_pageblock and __offline_isolated_pages.
Yes. The thing with the wording is that pages with (PageOffline(page) &&
!page_count(page)) can also not really be moved, but they can be skipped
when offlining. If we call that "moving them to /dev/null", then yes,
they can be moved to some degree :)
I can certainly do here e.g.,
/*
* PageOffline() pages that are not marked __PageMovable() and have a
* reference count > 0 (after MEM_GOING_OFFLINE) are definitely
* unmovable. If their reference count would be 0, they could be skipped
* when offlining memory sections.
*/
And maybe I'll add to the function doc, that unmovable pages that are
skipped in this function can include pages that can be skipped when
offlining (moving them to nirvana).
Other suggestions?
[...]
>>
>> [1] we detect a definite offlining blocker and
>>
>>>> + } while (!ret);
>>>> +
>>>> + if (ret != -ENOENT) {
>>>> + reason = "unmovable page";
>>
>> [2] we abort offlining
>>
>>>> + goto failed_removal_isolated;
>>>> }
>>>>
>>>> /*
>
> Yeah, this is the piece I misread. I knew the loop this was in previously
> was looping when returning -ENOENT so for some reason I had it in my head
> that you were still looping on -EBUSY.
Ah okay, I see. Yeah, that wouldn't make sense for the use case I have :)
>
> So the one question I would have is if at this point are we guaranteed
> that the balloon drivers have already taken care of the page count for all
> the pages they set to PageOffline? Based on the patch description I was
> thinking that this was going to be looping for a while waiting for the
> driver to clear the pages and then walking through them at the end of the
> loop via check_pages_isolated_cb.
So, e.g., the patch description states
"Let's allow to do that by allowing to isolate any PageOffline() page
when offlining. This way, we can reach the memory hotplug notifier
MEM_GOING_OFFLINE, where the driver can signal that he is fine with
offlining this page by dropping its reference count."
Any balloon driver that does not allow offlining (e.g., XEN, HyperV,
virtio-balloon), will always have a refcount of (at least) 1. Drivers
that want to make use of that (esp. virtio-mem, but eventually also
HyperV), will drop their refcount via the MEM_GOING_OFFLINE call.
So yes, at this point, all applicable users were notified via
MEM_GOING_OFFLINE and had their chance to decrement the refcount. If
they didn't, offlining will be aborted.
Thanks again!
--
Thanks,
David / dhildenb
