From: Yang Shi <yang.shi@linux.alibaba.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>,
Andrew Morton <akpm@linux-foundation.org>
Cc: kirill.shutemov@linux.intel.com, gavin.dg@linux.alibaba.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: thp: fix potential clearing to referenced flag in page_idle_clear_pte_refs_one()
Date: Thu, 8 Feb 2018 20:47:35 -0800 [thread overview]
Message-ID: <a19c08ad-ce34-3a9f-0c7c-6ca912660456@linux.alibaba.com> (raw)
In-Reply-To: <20180209043325.l6b6hwgeomqldeb6@node.shutemov.name>
On 2/8/18 8:33 PM, Kirill A. Shutemov wrote:
> On Thu, Feb 08, 2018 at 02:39:26PM -0800, Andrew Morton wrote:
>> On Tue, 6 Feb 2018 08:06:36 +0800 Yang Shi <yang.shi@linux.alibaba.com> wrote:
>>
>>> For PTE-mapped THP, the compound THP has not been split to normal 4K
>>> pages yet, the whole THP is considered referenced if any one of sub
>>> page is referenced.
>>>
>>> When walking PTE-mapped THP by pvmw, all relevant PTEs will be checked
>>> to retrieve referenced bit. But, the current code just returns the
>>> result of the last PTE. If the last PTE has not referenced, the
>>> referenced flag will be cleared.
>>>
>>> So, here just break pvmw walk once referenced PTE is found if the page
>>> is a part of THP.
>>>
>>> ...
>>>
>>> --- a/mm/page_idle.c
>>> +++ b/mm/page_idle.c
>>> @@ -67,6 +67,14 @@ static bool page_idle_clear_pte_refs_one(struct page *page,
>>> if (pvmw.pte) {
>>> referenced = ptep_clear_young_notify(vma, addr,
>>> pvmw.pte);
>>> + /*
>>> + * For PTE-mapped THP, one sub page is referenced,
>>> + * the whole THP is referenced.
>>> + */
>>> + if (referenced && PageTransCompound(pvmw.page)) {
>>> + page_vma_mapped_walk_done(&pvmw);
>>> + break;
>>> + }
>> This means that the function will no longer clear the referenced bits
>> in all the ptes. What effect does this have and should we document
>> this in some fashion?
> Yeah, the patch is wrong. We need to get all ptes for THP cleared.
>
> What about something like this instead (untested):
Thanks, Kirill. It looks correct. All ptes should be cleared.
I'm going to prepare v2 patch.
Regards,
Yang
>
> diff --git a/mm/page_idle.c b/mm/page_idle.c
> index 0a49374e6931..6876522c9dce 100644
> --- a/mm/page_idle.c
> +++ b/mm/page_idle.c
> @@ -65,10 +65,10 @@ static bool page_idle_clear_pte_refs_one(struct page *page,
> while (page_vma_mapped_walk(&pvmw)) {
> addr = pvmw.address;
> if (pvmw.pte) {
> - referenced = ptep_clear_young_notify(vma, addr,
> + referenced |= ptep_clear_young_notify(vma, addr,
> pvmw.pte);
> } else if (IS_ENABLED(CONFIG_TRANSPARENT_HUGEPAGE)) {
> - referenced = pmdp_clear_young_notify(vma, addr,
> + referenced |= pmdp_clear_young_notify(vma, addr,
> pvmw.pmd);
> } else {
> /* unexpected pmd-mapped page? */
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2018-02-09 4:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 0:06 Yang Shi
2018-02-08 22:39 ` Andrew Morton
2018-02-09 4:33 ` Kirill A. Shutemov
2018-02-09 4:47 ` Yang Shi [this message]
2018-02-09 8:16 ` Kirill A. Shutemov
2018-02-09 19:14 ` Yang Shi
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=a19c08ad-ce34-3a9f-0c7c-6ca912660456@linux.alibaba.com \
--to=yang.shi@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=gavin.dg@linux.alibaba.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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