linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yu Zhao <yuzhao@google.com>
To: Aravinda Prasad <aravinda.prasad@intel.com>
Cc: damon@lists.linux.dev, linux-mm@kvack.org, sj@kernel.org,
	 linux-kernel@vger.kernel.org, s2322819@ed.ac.uk,
	sandeep4.kumar@intel.com,  ying.huang@intel.com,
	dave.hansen@intel.com, dan.j.williams@intel.com,
	 sreenivas.subramoney@intel.com, antti.kervinen@intel.com,
	 alexander.kanevskiy@intel.com, Alan Nair <alan.nair@intel.com>,
	 Juergen Gross <jgross@suse.com>,
	Ryan Roberts <ryan.roberts@arm.com>
Subject: Re: mm/DAMON: Profiling enhancements for DAMON
Date: Fri, 15 Dec 2023 01:33:18 -0700	[thread overview]
Message-ID: <CAOUHufZW8ZbNDnu3Cfc61oJ4FkXK+AbT90XpS5Ei++1_5mcFFQ@mail.gmail.com> (raw)
In-Reply-To: <20231215074619.173787-1-aravinda.prasad@intel.com>

On Fri, Dec 15, 2023 at 12:42 AM Aravinda Prasad
<aravinda.prasad@intel.com> wrote:
...

> This patch proposes profiling different levels of the application’s
> page table tree to detect whether a region is accessed or not. This
> patch is based on the observation that, when the accessed bit for a
> page is set, the accessed bits at the higher levels of the page table
> tree (PMD/PUD/PGD) corresponding to the path of the page table walk
> are also set. Hence, it is efficient to  check the accessed bits at
> the higher levels of the page table tree to detect whether a region
> is accessed or not.

This patch can crash on Xen. See commit 4aaf269c768d("mm: introduce
arch_has_hw_nonleaf_pmd_young()")

MGLRU already does this in the correct way. See mm/vmscan.c.

This patch also can cause USER DATA CORRUPTION. See commit
c11d34fa139e ("mm/damon/ops-common: atomically test and clear young on
ptes and pmds").

The quality of your patch makes me very much doubt the quality of your
paper, especially your results on Google's kstaled and MGLRU in table
6.2.


  reply	other threads:[~2023-12-15  8:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-15  7:46 Aravinda Prasad
2023-12-15  8:33 ` Yu Zhao [this message]
2023-12-15 10:07   ` Prasad, Aravinda
2023-12-16  5:41     ` Yu Zhao
2023-12-18 11:32       ` Prasad, Aravinda
2023-12-15 18:10 ` Dave Hansen
2023-12-18 11:41   ` Prasad, Aravinda
2023-12-15 20:11 ` SeongJae Park
2023-12-18 13:05   ` Prasad, Aravinda
2024-02-26  6:09 罗午阳
2024-03-04  1:54 罗午阳
2024-03-04  6:23 ` Prasad, Aravinda
2024-03-04  6:26   ` Prasad, Aravinda

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=CAOUHufZW8ZbNDnu3Cfc61oJ4FkXK+AbT90XpS5Ei++1_5mcFFQ@mail.gmail.com \
    --to=yuzhao@google.com \
    --cc=alan.nair@intel.com \
    --cc=alexander.kanevskiy@intel.com \
    --cc=antti.kervinen@intel.com \
    --cc=aravinda.prasad@intel.com \
    --cc=damon@lists.linux.dev \
    --cc=dan.j.williams@intel.com \
    --cc=dave.hansen@intel.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ryan.roberts@arm.com \
    --cc=s2322819@ed.ac.uk \
    --cc=sandeep4.kumar@intel.com \
    --cc=sj@kernel.org \
    --cc=sreenivas.subramoney@intel.com \
    --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