From: David Hildenbrand <david@redhat.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
Mike Kravetz <mike.kravetz@oracle.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
"Aneesh Kumar K . V" <aneesh.kumar@linux.ibm.com>,
Muchun Song <songmuchun@bytedance.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Andrew Morton <akpm@linux-foundation.org>,
Naoya Horiguchi <naoya.horiguchi@linux.dev>
Subject: Re: [PATCH] hugetlb: simplify hugetlb handling in follow_page_mask
Date: Mon, 5 Sep 2022 18:09:04 +0200 [thread overview]
Message-ID: <362e6361-e2b7-16eb-83c8-203738f7b5d0@redhat.com> (raw)
In-Reply-To: <bb05ac8a-6847-0dcc-1f71-dc7c3f141f11@csgroup.eu>
> 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
prev parent reply other threads:[~2022-09-05 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220829234053.159158-1-mike.kravetz@oracle.com>
[not found] ` <608934d4-466d-975e-6458-34a91ccb4669@redhat.com>
[not found] ` <Yw5AOZ/Kc5f3UP+s@monkey>
[not found] ` <Yw6Bpsow+gUMlHCU@monkey>
[not found] ` <739dc825-ece3-a59f-adc5-65861676e0ae@redhat.com>
[not found] ` <YxJQfGSsbXd3W4m/@monkey>
[not found] ` <323fdb0f-c5a5-e0e5-1ff4-ab971bc295cc@redhat.com>
2022-09-03 7:07 ` [PATCH] hugetlb: simplify hugetlb handling in follow_page_mask Christophe Leroy
2022-09-04 11:49 ` Michael Ellerman
2022-09-05 8:37 ` David Hildenbrand
2022-09-05 9:33 ` Christophe Leroy
2022-09-05 9:46 ` David Hildenbrand
2022-09-05 16:05 ` Christophe Leroy
2022-09-05 16:09 ` David Hildenbrand [this message]
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=362e6361-e2b7-16eb-83c8-203738f7b5d0@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mike.kravetz@oracle.com \
--cc=naoya.horiguchi@linux.dev \
--cc=songmuchun@bytedance.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;
as well as URLs for NNTP newsgroup(s).