[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230125171159.355a770a2e34f78d7664e1f0@linux-foundation.org>
Date: Wed, 25 Jan 2023 17:11:59 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Mel Gorman <mgorman@...hsingularity.net>
Cc: Vlastimil Babka <vbabka@...e.cz>,
Jiri Slaby <jirislaby@...nel.org>,
Maxim Levitsky <mlevitsk@...hat.com>,
Michal Hocko <mhocko@...nel.org>,
Pedro Falcato <pedro.falcato@...il.com>,
Paolo Bonzini <pbonzini@...hat.com>,
Chuyi Zhou <zhouchuyi@...edance.com>,
Linux-MM <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 0/4] Fix excessive CPU usage during compaction
On Wed, 25 Jan 2023 13:44:30 +0000 Mel Gorman <mgorman@...hsingularity.net> wrote:
> Commit 7efc3b726103 ("mm/compaction: fix set skip in fast_find_migrateblock")
> fixed a problem where pageblocks found by fast_find_migrateblock() were
> ignored. Unfortunately there were numerous bug reports complaining about high
> CPU usage and massive stalls once 6.1 was released. Due to the severity,
> the patch was reverted by Vlastimil as a short-term fix[1] to -stable and
> is currently sitting in the Andrew's git branch mm/mm-hotfixes-unstable.
>
> The underlying problem for each of the bugs is suspected to be the
> repeated scanning of the same pageblocks. This series should guarantee
> forward progress even with commit 7efc3b726103. More information is in
> the changelog for patch 4.
>
> If this series is accepted and merged after the revert of 7efc3b726103
> then a "revert of the revert" will be needed.
If we drop Vlastimil's reversion and apply this, the whole series
should be cc:stable and it isn't really designed for that.
So I think either
a) drop Vlastimil's reversion and persuade Mel to send us a minimal
version of patch #4 for -stable consumption. Patches 1-3 of this
series come later.
b) go ahead with Vlastimil's revert for -stable, queue up this
series for 6.3-rc1 and redo the original "fix set skip in
fast_find_migrateblock" some time in the future.
If we go with b) then the Fixes: tag in "[PATCH 4/4] mm, compaction:
Finish pageblocks on complete migration failure" is inappropriate -
fixing a reverted commit which Vlastimil's revert already fixed.
I'll plan on b) for now.
Powered by blists - more mailing lists