linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Barry Song <21cnbao@gmail.com>
To: Ryan Roberts <ryan.roberts@arm.com>
Cc: akpm@linux-foundation.org, 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 21:35:41 +1200	[thread overview]
Message-ID: <CAGsJ_4y9yjFgccoja63Yw=SOv96d2+8sc4_9s7xfJ8mHh2BkOg@mail.gmail.com> (raw)
In-Reply-To: <bfdf6970-48cc-477a-b726-5e0da242da93@arm.com>

On Mon, Jul 1, 2024 at 8:48 PM Ryan Roberts <ryan.roberts@arm.com> wrote:
>
> On 30/06/2024 00:41, Barry Song wrote:
> > From: Barry Song <v-songbaohua@oppo.com>
> >
> > The optimization of list_empty(&folio->_deferred_list) aimed to prevent
> > increasing the PTL duration when a large folio is partially unmapped,
> > for example, from subpage 0 to subpage (nr - 2).
> >
> > But Ryan's commit 5ed890ce5147 ("mm: vmscan: avoid split during
> > shrink_folio_list()") actually splits this kind of large folios. This
> > makes the "optimization" useless.
> >
> > Signed-off-by: Barry Song <v-songbaohua@oppo.com>
> > Cc: David Hildenbrand <david@redhat.com>
> > Cc: Ryan Roberts <ryan.roberts@arm.com>
>
> Reviewed-by: Ryan Roberts <ryan.roberts@arm.com>
>
> > ---
> >  -v1
> >  * I remember David and Ryan once suggested that this check could be dropped
> >    while the patch was being pulled into mm-unstable. However, for some reason,
> >    I forgot to request squashing this change.
> >
> >  mm/vmscan.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/mm/vmscan.c b/mm/vmscan.c
> > index 3d4c681c6d40..0761f91b407f 100644
> > --- a/mm/vmscan.c
> > +++ 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")

And an additional changelog:

Additionally, the list_empty() technically requires a data_race() annotation.

>
> >                               flags |= TTU_SYNC;
> >
> >                       try_to_unmap(folio, flags);
>

Thanks
Barry


  reply	other threads:[~2024-07-01  9:35 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 [this message]
2024-07-02  6:32     ` Andrew Morton
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='CAGsJ_4y9yjFgccoja63Yw=SOv96d2+8sc4_9s7xfJ8mHh2BkOg@mail.gmail.com' \
    --to=21cnbao@gmail.com \
    --cc=akpm@linux-foundation.org \
    --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