From: "Huang, Ying" <ying.huang@intel.com>
To: Gregory Price <gourry@gourry.net>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, david@redhat.com, nphamcs@gmail.com,
nehagholkar@meta.com, abhishekd@meta.com,
Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [PATCH 0/3] mm,TPP: Enable promotion of unmapped pagecache
Date: Mon, 19 Aug 2024 15:46:00 +0800 [thread overview]
Message-ID: <875xrxhs5j.fsf@yhuang6-desk2.ccr.corp.intel.com> (raw)
In-Reply-To: <20240803094715.23900-1-gourry@gourry.net> (Gregory Price's message of "Sat, 3 Aug 2024 05:47:12 -0400")
Gregory Price <gourry@gourry.net> writes:
> Unmapped pagecache pages can be demoted to low-tier memory, but
> they can only be promoted if a process maps the pages into the
> memory space (so that NUMA hint faults can be caught). This can
> cause significant performance degradation as the pagecache ages
> and unmapped, cached files are accessed.
>
> This patch series enables the pagecache to request a promotion of
> a folio when it is accessed via the pagecache.
>
> We add a new `numa_hint_page_cache` counter in vmstat to capture
> information on when these migrations occur.
It appears that you will promote page cache page on the second access.
Do you have some better way to identify hot pages from the not-so-hot
pages? How to balance between unmapped and mapped pages? We have hot
page selection for hot pages.
[snip]
--
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2024-08-19 7:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240803094715.23900-1-gourry@gourry.net>
2024-08-08 23:20 ` Andrew Morton
2024-08-13 15:04 ` Gregory Price
2024-08-14 16:09 ` Gregory Price
2024-08-19 7:46 ` Huang, Ying [this message]
2024-08-19 15:15 ` Gregory Price
2024-09-02 6:53 ` Huang, Ying
2024-09-03 13:36 ` Gregory Price
2024-11-04 18:12 ` Gregory Price
2024-11-05 2:00 ` Huang, Ying
2024-11-05 15:16 ` Gregory Price
2024-11-08 18:00 ` Gregory Price
2024-11-11 1:35 ` Huang, Ying
2024-11-11 14:25 ` Gregory Price
2024-11-12 0:33 ` Huang, Ying
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=875xrxhs5j.fsf@yhuang6-desk2.ccr.corp.intel.com \
--to=ying.huang@intel.com \
--cc=abhishekd@meta.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=gourry@gourry.net \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nehagholkar@meta.com \
--cc=nphamcs@gmail.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