From: SeongJae Park <sjpark@amazon.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: SeongJae Park <sjpark@amazon.com>,
"Huang, Ying" <ying.huang@intel.com>,
Mel Gorman <mgorman@techsingularity.net>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@redhat.com>,
Mel Gorman <mgorman@suse.de>, 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: Re: Re: [RFC] autonuma: Support to scan page table asynchronously
Date: Fri, 17 Apr 2020 12:21:29 +0200 [thread overview]
Message-ID: <20200417102129.23399-1-sjpark@amazon.com> (raw)
In-Reply-To: <20200417100417.GT20730@hirez.programming.kicks-ass.net> (raw)
On Fri, 17 Apr 2020 12:04:17 +0200 Peter Zijlstra <peterz@infradead.org> wrote:
> On Fri, Apr 17, 2020 at 09:05:08AM +0200, SeongJae Park wrote:
> > I think the main idea of DAMON[1] might be able to applied here. Have you
> > considered it?
> >
> > [1] https://lore.kernel.org/linux-mm/20200406130938.14066-1-sjpark@amazon.com/
>
> I've ignored that entire thing after you said the information it
> provides was already available through the PMU.
Sorry if my answer made you confused. What I wanted to say was that the
fundamental access checking mechanism that DAMON depends on is PTE Accessed bit
for now, but it could be modified to use PMU or other features instead. In
other words, PMU on some architectures could provide the fundamental, low level
information for DAMON, as PTE Accessed bit does. What DAMON does are efficient
control of the fundamental access checking features and making of elaborated
final informations, which PMU itself doesn't provide.
Thanks,
SeongJae Park
next prev parent reply other threads:[~2020-04-17 10:22 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 [this message]
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
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=20200417102129.23399-1-sjpark@amazon.com \
--to=sjpark@amazon.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=tim.c.chen@intel.com \
--cc=tj@kernel.org \
--cc=ying.huang@intel.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).