From: Matthew Wilcox <willy@infradead.org>
To: Mina Almasry <almasrymina@google.com>
Cc: David Hildenbrand <david@redhat.com>,
Nathan Lewis <npl@google.com>, Yu Zhao <yuzhao@google.com>,
"Paul E . McKenney" <paulmckrcu@fb.com>,
Jonathan Corbet <corbet@lwn.net>,
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-fsdevel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v1] mm: Add /proc/$PID/pageflags
Date: Sun, 31 Oct 2021 02:28:56 +0000 [thread overview]
Message-ID: <YX3/aAYxsOey4FBS@casper.infradead.org> (raw)
In-Reply-To: <CAHS8izOkvuZ2pEGZXaYb0mfwC3xwpvXSgc9S+u_R-0zLWjzznQ@mail.gmail.com>
On Sat, Oct 30, 2021 at 03:06:31PM -0700, Mina Almasry wrote:
> Not quite sufficient, no. The process may have lots of non performance
> critical memory. The network service cares about specific memory
> ranges and wants to know if those are backed by hugepages.
Would it make sense to extend mincore() instead? We have 7 remaining
bits per byte.
But my question is, what information do you really want? Do you want
to know if the memory range is backed by huge pages, or do you want to
know if PMDs are being used to map the backing memory?
What information would you want to see if, say, 64kB entries are being
used on a 4kB ARM system where there's hardware support for those.
Other architectures also have support for TLB entries that are
intermediate between PTE and PMD sizes.
next prev parent reply other threads:[~2021-10-31 2:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 20:58 [PATCH v1] mm: Add /proc/$PID/pageflags Mina Almasry
2021-10-29 7:11 ` David Hildenbrand
2021-10-29 20:04 ` Mina Almasry
2021-10-29 21:37 ` David Hildenbrand
2021-10-30 22:06 ` Mina Almasry
2021-10-31 2:28 ` Matthew Wilcox [this message]
2021-11-02 11:42 ` David Hildenbrand
2021-11-02 18:38 ` Mina Almasry
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=YX3/aAYxsOey4FBS@casper.infradead.org \
--to=willy@infradead.org \
--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-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npl@google.com \
--cc=paulmckrcu@fb.com \
--cc=peterx@redhat.com \
--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).