From: William Kucharski <william.kucharski@oracle.com>
To: Mina Almasry <almasrymina@google.com>
Cc: Matthew Wilcox <willy@infradead.org>,
Jonathan Corbet <corbet@lwn.net>,
David Hildenbrand <david@redhat.com>,
"Paul E . McKenney" <paulmckrcu@fb.com>,
Yu Zhao <yuzhao@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Xu <peterx@redhat.com>,
Ivan Teterevkov <ivan.teterevkov@nutanix.com>,
Florian Schmidt <florian.schmidt@nutanix.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH v7] mm: Add PM_THP_MAPPED to /proc/pid/pagemap
Date: Tue, 11 Jan 2022 23:35:02 +0000 [thread overview]
Message-ID: <FD103257-48FC-4441-BB32-58C14C0CDE3F@oracle.com> (raw)
In-Reply-To: <CAHS8izNw87-L=rEwJF7_9WCaAcXLn2dUe68h_SbLErJoSUDzzg@mail.gmail.com>
> On Jan 4, 2022, at 4:04 PM, Mina Almasry <almasrymina@google.com> wrote:
>
> On Mon, Dec 13, 2021 at 4:22 PM Mina Almasry <almasrymina@google.com> wrote:
>>
>> On Sat, Nov 27, 2021 at 8:10 PM Matthew Wilcox <willy@infradead.org> wrote:
>>>
>>> On Mon, Nov 22, 2021 at 04:01:02PM -0800, Mina Almasry wrote:
>>>> Add PM_THP_MAPPED 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.
>>>
>>> But what is userspace going to _do_ differently if the kernel hasn't
>>> backed the memory with huge pages?
>>
>> Sorry for the late reply here.
>>
>> My plan is to expose this information as metrics right now and:
>> 1. Understand the kind of hugepage backing we're actually getting if any.
>> 2. If there are drops in hugepage backing we can investigate the
>> cause, whether it's due to normal memory fragmentation or some
>> bug/issue.
>> 3. Schedule machines for reboots to defragment the memory if the
>> hugepage backing is too low.
>> 4. Possibly motivate future work to improve hugepage backing if our
>> numbers are too low.
>
> Friendly ping on this. It has been reviewed by a few folks and after
> Matthew had questions about the use case which I've answered in the
> email above. Matthew, are you opposed to this patch?
I realize I'm jumping in late on this, but while (1) and (2) are
understandable, this bothers me:
> 3. Schedule machines for reboots to defragment the memory if the
> hugepage backing is too low.
If it's important enough to reboot the machine, shouldn't one be using
hugetlbfs instead?
It seems like user space is trying to track something it shouldn't be concerned
about, rather like if user space were concerned about precisely where in physical
memory its pages were mapped.
prev parent reply other threads:[~2022-01-11 23:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 0:01 Mina Almasry
2021-11-23 1:10 ` Peter Xu
2021-11-23 1:50 ` David Rientjes
2021-11-23 12:05 ` David Hildenbrand
2021-11-23 20:51 ` Matthew Wilcox
2021-11-23 21:10 ` Mina Almasry
2021-11-23 21:30 ` Matthew Wilcox
2021-11-23 21:47 ` Mina Almasry
2021-11-23 22:03 ` Matthew Wilcox
2021-11-23 22:23 ` Mina Almasry
2021-11-23 22:59 ` Matthew Wilcox
2021-11-23 23:16 ` Mina Almasry
2021-11-28 4:10 ` Matthew Wilcox
2021-12-14 0:22 ` Mina Almasry
2022-01-04 23:04 ` Mina Almasry
2022-01-05 4:39 ` Matthew Wilcox
2022-01-11 23:35 ` William Kucharski [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=FD103257-48FC-4441-BB32-58C14C0CDE3F@oracle.com \
--to=william.kucharski@oracle.com \
--cc=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-doc@vger.kernel.org \
--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