[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <362e6361-e2b7-16eb-83c8-203738f7b5d0@redhat.com>
Date: Mon, 5 Sep 2022 18:09:04 +0200
From: David Hildenbrand <david@...hat.com>
To: Christophe Leroy <christophe.leroy@...roup.eu>,
Mike Kravetz <mike.kravetz@...cle.com>
Cc: "linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-ia64@...r.kernel.org" <linux-ia64@...r.kernel.org>,
Baolin Wang <baolin.wang@...ux.alibaba.com>,
"Aneesh Kumar K . V" <aneesh.kumar@...ux.ibm.com>,
Naoya Horiguchi <naoya.horiguchi@...ux.dev>,
Michael Ellerman <mpe@...erman.id.au>,
Muchun Song <songmuchun@...edance.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: [PATCH] hugetlb: simplify hugetlb handling in follow_page_mask
> Yes I think the assumption is correct for user pages hence for GUP.
>
> By the way the discussion started with PTDUMP. For PTDUMP we need huge
> page directories to be taken into account. And for anything that
> involves kernel pages like VMAP or VMALLOC.
Yes, makes perfect sense to me now that you explained how/where hugepd
is actually used -- thanks!
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists