[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <25d3f071-3268-298b-e0c8-9c307d1015fe@redhat.com>
Date: Tue, 22 Oct 2019 08:52:28 +0200
From: David Hildenbrand <david@...hat.com>
To: linux-kernel@...r.kernel.org
Cc: linux-mm@...ck.org,
Alexander Duyck <alexander.h.duyck@...ux.intel.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Anshuman Khandual <anshuman.khandual@....com>,
Dan Williams <dan.j.williams@...el.com>,
Mel Gorman <mgorman@...hsingularity.net>,
Michal Hocko <mhocko@...e.com>,
Mike Rapoport <rppt@...ux.ibm.com>,
Mike Rapoport <rppt@...ux.vnet.ibm.com>,
Oscar Salvador <osalvador@...e.de>,
Pavel Tatashin <pasha.tatashin@...een.com>,
Pavel Tatashin <pavel.tatashin@...rosoft.com>,
Pingfan Liu <kernelfans@...il.com>, Qian Cai <cai@....pw>,
Vlastimil Babka <vbabka@...e.cz>,
Wei Yang <richard.weiyang@...il.com>
Subject: Re: [PATCH v2 0/2] mm: Memory offlining + page isolation cleanups
On 21.10.19 19:23, David Hildenbrand wrote:
> Two cleanups that popped up while working on (and discussing) virtio-mem:
> https://lkml.org/lkml/2019/9/19/463
>
> Tested with DIMMs on x86.
>
> As discussed with michal in v1, I'll soon look into removing the use
> of PG_reserved during memory onlining completely - most probably
> disallowing to offline memory blocks with holes, cleaning up the
> onlining+offlining code.
BTW, I remember that ZONE_DEVICE pages are still required to be set
PG_reserved. That has to be sorted out first. I remember that somebody
was working on it a while ago but didn't hear about that again. Will
look into that as well - should be as easy as adding a zone check (if
there isn't a pfn_to_online_page() check already). But of course, there
might be special cases ....
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists