linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wenchao Hao <haowenchao22@gmail.com>
To: Baolin Wang <baolin.wang@linux.alibaba.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org,  linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/compaction: do not break pages whose order is larger than target order
Date: Fri, 25 Apr 2025 22:57:54 +0800	[thread overview]
Message-ID: <CAOptpSMZtw8xEHqgu-ufdQouiAHpitkQtBdFXmEbRGQ+FSAWYA@mail.gmail.com> (raw)
In-Reply-To: <8905cbf7-7507-44de-8721-b3e75e80732b@linux.alibaba.com>

On Fri, Apr 25, 2025 at 2:53 PM Baolin Wang
<baolin.wang@linux.alibaba.com> wrote:
>
>
>
> On 2025/4/24 23:38, Wenchao Hao wrote:
> > When scanning free pages for memory compaction, if the compaction target
> > order is explicitly specified, do not split pages in buddy whose order
> > are larger than compaction target order.
>
> We've already checked this in suitable_migration_target(), so how did
> you observe that there are still attempts to isolate such non-suitable
> free large folios? Please explain your usecase in detail.
>

I found such non-suitable during testing proactive compaction on
android device (6.6 kernel), and I want to use proactive compaction
to produce order4 pages for mthp.

The test device did not include your patch "mm: compaction: limit the suitable
target page order to be less than cc->order".

However, from the analysis of the code flow, even if it is included,
similar non-suitable free large folios may still appear.

suitable_migration_target() only check before isolate_freepages_block(), and
check is based on the starting page of pageblock.

If the target order is relatively small(order4 for example), just one check in
suitable_migration_target() is not enough, because there may be other free
folios which are larger than order4 in this pageblock.

> > Signed-off-by: Wenchao Hao <haowenchao22@gmail.com>
> > ---
> >   mm/compaction.c | 11 +++++++++++
> >   1 file changed, 11 insertions(+)
> >
> > diff --git a/mm/compaction.c b/mm/compaction.c
> > index 3925cb61dbb8..b0ed0831c400 100644
> > --- a/mm/compaction.c
> > +++ b/mm/compaction.c
> > @@ -656,6 +656,17 @@ static unsigned long isolate_freepages_block(struct compact_control *cc,
> >
> >               /* Found a free page, will break it into order-0 pages */
> >               order = buddy_order(page);
> > +
> > +             /*
> > +              * Do not break free pages whose order is larger than
> > +              * compact's desired order
> > +              */
> > +             if (cc->order != -1 && order >= cc->order) {
> > +                     blockpfn += (1 << order) - 1;
> > +                     page += (1 << order) - 1;
> > +                     goto isolate_fail;
> > +             }
> > +
> >               isolated = __isolate_free_page(page, order);
> >               if (!isolated)
> >                       break;


      reply	other threads:[~2025-04-25 14:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-24 15:38 Wenchao Hao
2025-04-24 19:42 ` Johannes Weiner
2025-04-25 14:28   ` Wenchao Hao
2025-04-25 15:32     ` Johannes Weiner
2025-04-25 17:24       ` Wenchao Hao
2025-04-29 16:44   ` Zi Yan
2025-04-25  6:53 ` Baolin Wang
2025-04-25 14:57   ` Wenchao Hao [this message]

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=CAOptpSMZtw8xEHqgu-ufdQouiAHpitkQtBdFXmEbRGQ+FSAWYA@mail.gmail.com \
    --to=haowenchao22@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=baolin.wang@linux.alibaba.com \
    --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