From: Andrew Morton <akpm@linux-foundation.org>
To: Mina Almasry <almasrymina@google.com>
Cc: David Hildenbrand <david@redhat.com>,
Matthew Wilcox <willy@infradead.org>,
"Paul E . McKenney" <paulmckrcu@fb.com>,
Yu Zhao <yuzhao@google.com>, Jonathan Corbet <corbet@lwn.net>,
Peter Xu <peterx@redhat.com>,
Ivan Teterevkov <ivan.teterevkov@nutanix.com>,
Florian Schmidt <florian.schmidt@nutanix.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v5] mm: Add PM_HUGE_THP_MAPPING to /proc/pid/pagemap
Date: Mon, 15 Nov 2021 17:41:48 -0800 [thread overview]
Message-ID: <20211115174148.cdaeef3a026fe3143e6699cc@linux-foundation.org> (raw)
In-Reply-To: <20211110221120.3833294-1-almasrymina@google.com>
On Wed, 10 Nov 2021 14:11:20 -0800 Mina Almasry <almasrymina@google.com> wrote:
> Add PM_HUGE_THP MAPPING to allow userspace to detect whether a given virt
> address is currently mapped by a transparent huge page or not. Example
> use case is a process requesting THPs from the kernel (via a huge tmpfs
> mount for example), for a performance critical region of memory. The
> userspace may want to query whether the kernel is actually backing this
> memory by hugepages or not.
>
> PM_HUGE_THP_MAPPING bit is set if the virt address is mapped at the PMD
> level and the underlying page is a transparent huge page.
>
> A few options were considered:
> 1. Add /proc/pid/pageflags that exports the same info as
> /proc/kpageflags. This is not appropriate because many kpageflags are
> inappropriate to expose to userspace processes.
> 2. Simply get this info from the existing /proc/pid/smaps interface.
> There are a couple of issues with that:
> 1. /proc/pid/smaps output is human readable and unfriendly to
> programatically parse.
> 2. /proc/pid/smaps is slow. The cost of reading /proc/pid/smaps into
> userspace buffers is about ~800us per call, and this doesn't
> include parsing the output to get the information you need. The
> cost of querying 1 virt address in /proc/pid/pagemaps however is
> around 5-7us.
>
> Tested manually by adding logging into transhuge-stress, and by
> allocating THP and querying the PM_HUGE_THP_MAPPING flag at those
> virtual addresses.
>
> --- a/tools/testing/selftests/vm/transhuge-stress.c
> +++ b/tools/testing/selftests/vm/transhuge-stress.c
> @@ -16,6 +16,12 @@
> #include <string.h>
> #include <sys/mman.h>
>
> +/*
> + * We can use /proc/pid/pagemap to detect whether the kernel was able to find
> + * hugepages or no. This can be very noisy, so is disabled by default.
> + */
> +#define NO_DETECT_HUGEPAGES
> +
>
> ...
>
> +#ifndef NO_DETECT_HUGEPAGES
> + if (!PAGEMAP_THP(ent[0]))
> + fprintf(stderr, "WARNING: detected non THP page\n");
> +#endif
This looks like a developer thing. Is there any point in leaving it in
the mainline code?
prev parent reply other threads:[~2021-11-16 1:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 22:11 [PATCH v5] mm: Add PM_HUGE_THP_MAPPING to /proc/pid/pagemap Mina Almasry
2021-11-16 1:41 ` Andrew Morton [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=20211115174148.cdaeef3a026fe3143e6699cc@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=almasrymina@google.com \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=florian.schmidt@nutanix.com \
--cc=ivan.teterevkov@nutanix.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paulmckrcu@fb.com \
--cc=peterx@redhat.com \
--cc=willy@infradead.org \
--cc=yuzhao@google.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).