From: "Huang\, Ying" <ying.huang@intel.com>
To: SeongJae Park <sj38.park@gmail.com>
Cc: Mel Gorman <mgorman@suse.de>, SeongJae Park <sjpark@amazon.com>,
Mel Gorman <mgorman@techsingularity.net>,
Peter Zijlstra <peterz@infradead.org>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@redhat.com>,
Rik van Riel <riel@surriel.com>,
Daniel Jordan <daniel.m.jordan@oracle.com>,
Tejun Heo <tj@kernel.org>, Dave Hansen <dave.hansen@intel.com>,
Tim Chen <tim.c.chen@intel.com>, Aubrey Li <aubrey.li@intel.com>
Subject: Re: [RFC] autonuma: Support to scan page table asynchronously
Date: Mon, 20 Apr 2020 10:32:53 +0800 [thread overview]
Message-ID: <877dyaubsa.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20200418094811.4757-1-sj38.park@gmail.com> (SeongJae Park's message of "Sat, 18 Apr 2020 11:48:11 +0200")
SeongJae Park <sj38.park@gmail.com> writes:
>
> DAMON allows users to know which address ranges have which access frequency.
> Thus, I think DAMON could be used for detection of hot pages, which will be
> good migration candidates, instead of the NUMA hinting fault based referenced
> pages detection.
>
> The benefits I expect from this change are better accuracy and less overhead.
> As we can know not only referenced pages but hot pages, migration will be more
> effective.
The purpose of AutoNUMA scanning isn't to find the hot pages, but the
pages that are accessed across NUMA node. PTE accessed bit cannot
provide information of accessing CPU, so it's not enough for AutoNUMA.
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2020-04-20 2:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 8:19 [RFC] autonuma: Support to scan page table asynchronously Huang Ying
2020-04-14 12:06 ` Mel Gorman
2020-04-15 8:14 ` Huang, Ying
2020-04-17 7:05 ` SeongJae Park
2020-04-17 10:04 ` Peter Zijlstra
2020-04-17 10:21 ` SeongJae Park
2020-04-17 12:16 ` Mel Gorman
2020-04-17 12:21 ` Peter Zijlstra
2020-04-17 12:44 ` SeongJae Park
2020-04-17 14:46 ` Mel Gorman
2020-04-18 9:48 ` SeongJae Park
2020-04-20 2:32 ` Huang, Ying [this message]
2020-04-15 11:32 ` Peter Zijlstra
2020-04-16 1:24 ` Huang, Ying
2020-04-17 10:06 ` Peter Zijlstra
2020-04-20 3:26 ` 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=877dyaubsa.fsf@yhuang-dev.intel.com \
--to=ying.huang@intel.com \
--cc=aubrey.li@intel.com \
--cc=daniel.m.jordan@oracle.com \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mgorman@techsingularity.net \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=sj38.park@gmail.com \
--cc=sjpark@amazon.com \
--cc=tim.c.chen@intel.com \
--cc=tj@kernel.org \
/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).