[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f065d998-7fa3-ef9a-c2f4-5b9116f5596b@redhat.com>
Date: Fri, 18 Oct 2019 10:38:21 +0200
From: David Hildenbrand <david@...hat.com>
To: Michal Hocko <mhocko@...nel.org>
Cc: Naoya Horiguchi <n-horiguchi@...jp.nec.com>, Qian Cai <cai@....pw>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
Mike Kravetz <mike.kravetz@...cle.com>
Subject: Re: memory offline infinite loop after soft offline
On 18.10.19 10:24, Michal Hocko wrote:
> On Fri 18-10-19 10:13:36, David Hildenbrand wrote:
> [...]
>> However, if the compound page spans multiple pageblocks
>
> Although hugetlb pages spanning pageblocks are possible this shouldn't
> matter in__test_page_isolated_in_pageblock because this function doesn't
> really operate on pageblocks as the name suggests. It is simply
> traversing all valid RAM ranges (see walk_system_ram_range).
As long as the hugepages don't span memory blocks/sections, you are
right. I have no experience with gigantic pages in this regard.
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists