From: Matthew Wilcox <willy@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Yu Zhao <yuzhao@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Jesse Barnes <jsbarnes@google.com>,
Suren Baghdasaryan <surenb@google.com>,
Guru Anbalagane <gurua@google.com>,
David Rientjes <rientjes@google.com>
Subject: Re: [GIT PULL] hotfixes for 6.7-rc6
Date: Sun, 17 Dec 2023 15:40:19 +0000 [thread overview]
Message-ID: <ZX8WY7s76KYr3jRE@casper.infradead.org> (raw)
In-Reply-To: <CAHk-=wgWwyvzcG9YiEAv2X7XivH-zqLLxeJ+A6EpMp+EA3o_iw@mail.gmail.com>
On Sat, Dec 16, 2023 at 04:16:45PM -0800, Linus Torvalds wrote:
> On Fri, 15 Dec 2023 at 20:57, Yu Zhao <yuzhao@google.com> wrote:
> >
> > There has been a short-term plan, i.e., moving some of folio->flags to
> > the lower bits of folio->lru so that we can drop the Kconfig
> > constraint. I have discussed this with Willy but never acted on it. My
> > priority has been to surface more of our ideas that can potentially
> > save users money on memory to the community. I'm CC'ing our team
> > leads. Please feel free to let us know your preference on the
> > priority.
>
> This is definitely a "eventually" thing on my wishlist, so I was more
> just wanting to hear that there is a plan, and somebody working on
> it..
"eventually" we should get rid of LRUs altogether. They're no good for
a modern CPU.
https://lore.kernel.org/linux-mm/ZTc7SHQ4RbPkD3eZ@casper.infradead.org/
I don't have much more in the way of thoughts on what this might look
like beyond that email. I'm inclined towards something incredibly simple
like taking each 4MB chunk of memory in turn; freeing inactive pages
and marking active pages as inactive.
next prev parent reply other threads:[~2023-12-17 15:40 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
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 [this message]
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=ZX8WY7s76KYr3jRE@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=gurua@google.com \
--cc=jsbarnes@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=surenb@google.com \
--cc=torvalds@linux-foundation.org \
--cc=yuzhao@google.com \
/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