From: Matthew Wilcox <willy@infradead.org>
To: Aneesh Kumar K V <aneesh.kumar@linux.ibm.com>
Cc: lsf-pc@lists.linux-foundation.org, Linux MM <linux-mm@kvack.org>,
Yu Zhao <yuzhao@google.com>, Dave Hansen <dave.hansen@intel.com>,
Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [LSF/MM/BPF TOPIC] Using hardware counters to determine hot/cold pages
Date: Fri, 17 Feb 2023 16:53:53 +0000 [thread overview]
Message-ID: <Y++xIZukBr56jKFT@casper.infradead.org> (raw)
In-Reply-To: <6bbf2c47-05ab-b78c-3165-2eff18962d6d@linux.ibm.com>
On Fri, Feb 17, 2023 at 05:28:09PM +0530, Aneesh Kumar K V wrote:
> PowerPC architecture (POWER10) supports a Hot/Cold page tracking
> facility that provides access counter and access affinity details at
> configurable page size granularity [1]. I have been looking at using
Does that advert contain any more information about this feature than:
Hot/Cold page tracking | Recording for memory management
because I'd like to understand what its limitations are -- can
it be a per-VMA option, for example? Or is it set at bootup like
CONFIG_PAGE_SIZE?
For file-backed memory, the page cache will use variable sized
folios, depending on what it determines to be a useful granularity.
I'm _expecting_ something of the same sort for anonymous memory, although
maybe we'll make that determination on a per-VMA basis and make all
folios within a VMA the same size.
next prev parent reply other threads:[~2023-02-17 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 11:58 [LSF/MM/BPF TOPIC] Using hardware counters to determine hot/cold pages Aneesh Kumar K V
2023-02-17 16:42 ` SeongJae Park
2023-02-19 14:29 ` Aneesh Kumar K.V
2023-02-19 20:31 ` SeongJae Park
2023-02-17 16:53 ` Matthew Wilcox [this message]
2023-02-19 14:43 ` Aneesh Kumar K.V
2023-02-17 22:00 ` Yang Shi
2023-02-19 14:45 ` Aneesh Kumar K.V
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=Y++xIZukBr56jKFT@casper.infradead.org \
--to=willy@infradead.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=dave.hansen@intel.com \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.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).