[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANpmjNPsdM2HrRFgEHYxX1seT2fbOFDuO6Ci-qF3X2y=9_PD1A@mail.gmail.com>
Date: Mon, 19 Feb 2024 10:52:17 +0100
From: Marco Elver <elver@...gle.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@...il.com>, Andrew Morton <akpm@...ux-foundation.org>
Cc: Andrey Konovalov <andreyknvl@...il.com>, glider@...gle.com, dvyukov@...gle.com,
eugenis@...gle.com, Oscar Salvador <osalvador@...e.de>, Vlastimil Babka <vbabka@...e.cz>,
Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
Linux Memory Management List <linux-mm@...ck.org>
Subject: Re: regression/bisected commit 773688a6cb24b0b3c2ba40354d883348a2befa38
make my system completely unusable under high load
On Mon, 19 Feb 2024 at 10:48, Mikhail Gavrilov
<mikhail.v.gavrilov@...il.com> wrote:
>
> On Sat, Feb 3, 2024 at 1:14 AM Mikhail Gavrilov
> <mikhail.v.gavrilov@...il.com> wrote:
> >
> > You are right.
> > Thanks for digging into it!
> >
>
> This [2] revert is still not merged at least I checked on 4f5e5092fdbf.
> Is there any plan to merge it or find another approach?
>
> [2] https://lore.kernel.org/all/20240118110216.2539519-2-elver@google.com/
I think it's already in -mm and -next. It just takes time, which is a
good thing, after all we want to let -next testing confirm nothing is
wrong with it.
Andrew, is this planned for the next merge window or as a "hot fix"
for the current rc? Given it has the right "Fixes" tags it will make
it to stable kernels eventually, but I also think that the previous
"slow" version is almost unusable on big systems, so it may be
worthwhile considering the current rc.
Thanks,
-- Marco
Powered by blists - more mailing lists