From: Andrew Morton <akpm@linux-foundation.org>
To: Barry Song <21cnbao@gmail.com>
Cc: Ryan Roberts <ryan.roberts@arm.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Barry Song <v-songbaohua@oppo.com>,
David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH] mm/vmscan: drop checking if _deferred_list is empty before using TTU_SYNC
Date: Mon, 1 Jul 2024 23:32:35 -0700 [thread overview]
Message-ID: <20240701233235.a1ae705c72ba6f81531c21fd@linux-foundation.org> (raw)
In-Reply-To: <CAGsJ_4y9yjFgccoja63Yw=SOv96d2+8sc4_9s7xfJ8mHh2BkOg@mail.gmail.com>
On Mon, 1 Jul 2024 21:35:41 +1200 Barry Song <21cnbao@gmail.com> wrote:
> > > +++ b/mm/vmscan.c
> > > @@ -1291,7 +1291,7 @@ static unsigned int shrink_folio_list(struct list_head *folio_list,
> > > * try_to_unmap acquire PTL from the first PTE,
> > > * eliminating the influence of temporary PTE values.
> > > */
> > > - if (folio_test_large(folio) && list_empty(&folio->_deferred_list))
> > > + if (folio_test_large(folio))
> >
> > As it stands, the list_empty() technically needs a data_race() annotation. I
> > think your original patch went into v6.10-rc1? If so, perhaps it makes sense to
> > try to get this into the next rc?
>
> Either way is fine. Hi Andrew, if you include it for the next RC, could you
> please add this tag?
>
> Fixes: 73bc32875ee9 ("mm: hold PTL from the first PTE while reclaiming
> a large folio")
Nope! That invites people to backport this change into kernels which
don't contain Ryan's 5ed890ce5147 ("mm: vmscan: avoid split during
shrink_folio_list()").
I'll simply queue this in the normal fashion.
> And an additional changelog:
>
> Additionally, the list_empty() technically requires a data_race() annotation.
Done, thanks.
next prev parent reply other threads:[~2024-07-02 6:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-29 23:41 Barry Song
2024-07-01 8:48 ` Ryan Roberts
2024-07-01 9:35 ` Barry Song
2024-07-02 6:32 ` Andrew Morton [this message]
2024-07-01 8:51 ` David Hildenbrand
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=20240701233235.a1ae705c72ba6f81531c21fd@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=21cnbao@gmail.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryan.roberts@arm.com \
--cc=v-songbaohua@oppo.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