From: Marco Elver <elver@google.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Andrey Konovalov <andreyknvl@gmail.com>,
glider@google.com, dvyukov@google.com, eugenis@google.com,
Oscar Salvador <osalvador@suse.de>,
Vlastimil Babka <vbabka@suse.cz>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: regression/bisected commit 773688a6cb24b0b3c2ba40354d883348a2befa38 make my system completely unusable under high load
Date: Mon, 19 Feb 2024 10:52:17 +0100 [thread overview]
Message-ID: <CANpmjNPsdM2HrRFgEHYxX1seT2fbOFDuO6Ci-qF3X2y=9_PD1A@mail.gmail.com> (raw)
In-Reply-To: <CABXGCsO5dcEuorLAXR3CFzDVyAWNk4_YfqCh=UJddfzpWF7hNg@mail.gmail.com>
On Mon, 19 Feb 2024 at 10:48, Mikhail Gavrilov
<mikhail.v.gavrilov@gmail.com> wrote:
>
> On Sat, Feb 3, 2024 at 1:14 AM Mikhail Gavrilov
> <mikhail.v.gavrilov@gmail.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
next prev parent reply other threads:[~2024-02-19 9:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 10:46 Mikhail Gavrilov
2024-01-19 10:54 ` Marco Elver
2024-01-19 10:59 ` Marco Elver
2024-01-19 17:54 ` Mikhail Gavrilov
2024-01-29 22:25 ` Mikhail Gavrilov
2024-01-29 23:14 ` Andrey Konovalov
2024-02-01 22:08 ` Mikhail Gavrilov
2024-02-02 9:00 ` Marco Elver
2024-02-02 16:35 ` Mikhail Gavrilov
2024-02-02 16:47 ` Marco Elver
2024-02-02 17:19 ` Marco Elver
2024-02-02 20:14 ` Mikhail Gavrilov
2024-02-19 9:48 ` Mikhail Gavrilov
2024-02-19 9:52 ` Marco Elver [this message]
2024-02-19 10:09 ` Vlastimil Babka
2024-02-19 23:28 ` Andrew Morton
2024-02-19 23:50 ` Vlastimil Babka
2024-02-20 5:37 ` Mikhail Gavrilov
2024-02-20 17:30 ` Andrew Morton
2024-02-20 18:16 ` Vlastimil Babka
2024-02-20 18:51 ` Marco Elver
2024-02-26 9:25 ` Marco Elver
2024-02-26 10:12 ` Vlastimil Babka
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='CANpmjNPsdM2HrRFgEHYxX1seT2fbOFDuO6Ci-qF3X2y=9_PD1A@mail.gmail.com' \
--to=elver@google.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=dvyukov@google.com \
--cc=eugenis@google.com \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=osalvador@suse.de \
--cc=vbabka@suse.cz \
/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