On Fri, 15 Dec 2023 12:11:42 -0800 Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: > On Fri, 15 Dec 2023 at 07:16, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> 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? I hope so, but I haven't heard specific plans. Things are still stabilizing, but it seems we're a fair way down that exponential curve. > 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? Hopefully Yu can talk to that. > Because I feel like we really don't want to keep this "two different > models" situation around forever. > Sure. Some diehards are still using slab :(
