From: Linus Torvalds <torvalds@linux-foundation.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] hotfixes for 6.7-rc6
Date: Fri, 15 Dec 2023 12:11:42 -0800 [thread overview]
Message-ID: <CAHk-=wjWJgWzOf9MCuiE0oDsF6cCCn7KKDc_xDN6Q3kWNEHKLQ@mail.gmail.com> (raw)
In-Reply-To: <20231215071604.946a433bbc05a6409faf5a33@linux-foundation.org>
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
next prev parent reply other threads:[~2023-12-15 20:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 15:16 Andrew Morton
2023-12-15 20:06 ` pr-tracker-bot
2023-12-15 20:11 ` Linus Torvalds [this message]
2023-12-15 20:22 ` Andrew Morton
2023-12-16 4:56 ` Yu Zhao
2023-12-17 0:16 ` Linus Torvalds
2023-12-17 15:40 ` Matthew Wilcox
2023-12-18 5:46 ` Andrew Morton
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='CAHk-=wjWJgWzOf9MCuiE0oDsF6cCCn7KKDc_xDN6Q3kWNEHKLQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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