From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: SeongJae Park <sj@kernel.org>
Cc: akpm@linux-foundation.org, mike.kravetz@oracle.com,
songmuchun@bytedance.com, damon@lists.linux.dev,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] mm/damon: Use set_huge_pte_at() to make huge pte old
Date: Tue, 21 Jun 2022 16:45:39 +0800 [thread overview]
Message-ID: <f79ad32f-50a3-be1a-0cac-d00f579e7077@linux.alibaba.com> (raw)
In-Reply-To: <20220620172742.48766-1-sj@kernel.org>
Hi SeongJae,
On 6/21/2022 1:27 AM, SeongJae Park wrote:
> Hi Baolin,
>
> On Mon, 20 Jun 2022 10:34:42 +0800 Baolin Wang <baolin.wang@linux.alibaba.com> wrote:
>
>> The huge_ptep_set_access_flags() can not make the huge pte old according
>> to the discussion [1], that means we will always mornitor the young state
>> of the hugetlb though we stopped accessing the hugetlb, as a result DAMON
>> will get inaccurate accessing statistics.
>>
>> So changing to use set_huge_pte_at() to make the huge pte old to fix this
>> issue.
>>
>> [1] https://lore.kernel.org/all/Yqy97gXI4Nqb7dYo@arm.com/
>>
>> Fixes: 49f4203aae06 ("mm/damon: add access checking for hugetlb pages")
>
> As the commit has merged in from v5.17, I guess it would be better to do below?
>
> Cc: <stable@vger.kernel.org>
Yes, thanks for reminding. Hope Andrew can help to add the stable tag
when picking up this patch.
>
>> Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
>
> Other than that,
>
> Reviewed-by: SeongJae Park <sj@kernel.org>
Thanks.
next prev parent reply other threads:[~2022-06-21 8:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 2:34 Baolin Wang
2022-06-20 17:27 ` SeongJae Park
2022-06-21 8:45 ` Baolin Wang [this message]
2022-06-21 23:41 ` Mike Kravetz
2022-06-22 3:09 ` Muchun Song
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=f79ad32f-50a3-be1a-0cac-d00f579e7077@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=sj@kernel.org \
--cc=songmuchun@bytedance.com \
--cc=stable@vger.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