Received-SPF: pass (google.com: domain of linux-kernel+bounces-1617-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Precedence: bulk
MIME-Version: 1.0
References: <20231215071604.946a433bbc05a6409faf5a33@linux-foundation.org>
In-Reply-To: <20231215071604.946a433bbc05a6409faf5a33@linux-foundation.org>
From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Fri, 15 Dec 2023 12:11:42 -0800
Message-ID: <CAHk-=wjWJgWzOf9MCuiE0oDsF6cCCn7KKDc_xDN6Q3kWNEHKLQ@mail.gmail.com>
Subject: Re: [GIT PULL] hotfixes for 6.7-rc6
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"

On Fri, 15 Dec 2023 at 07:16, Andrew Morton <akpm@linux-foundation.org> wrote:
>
> Yu Zhao (4):
>       mm/mglru: fix underprotected page cache
>       mm/mglru: try to stop at high watermarks
>       mm/mglru: respect min_ttl_ms with memcgs
>       mm/mglru: reclaim offlined memcgs harder

Entirely unrelated to this pull request (which I already pulled and
pushed out, as noted by pr-tracker-bot), since I looked at these it
just reminded me about a question I've had for a while...

Do we have any long-term (or even short-term?) plans to just make
mglru be the one and only model?

Yes, right now it's not just a Kconfig choice, but a real technical
issue too: it depends on having enough flags available, so we have
that "cannot use it on 32-bit with sparsemem".

But I'm hoping there is a plan or a workaround for that?

Because I feel like we really don't want to keep this "two different
models" situation around forever.

                     Linus