linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Vishal Moola (Oracle)" <vishal.moola@gmail.com>
To: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org
Cc: Matthew Wilcox <willy@infradead.org>,
	David Hildenbrand <david@kernel.org>,
	Mike Rapoport <rppt@kernel.org>
Subject: [LSF/MM/BPF TOPIC] Separately allocating memdescs from struct page
Date: Wed, 25 Feb 2026 15:19:33 -0800	[thread overview]
Message-ID: <aZ-DhWZbTnTnBh-D@fedora> (raw)

As part of the overarching project to shrink struct page, we've been
creating memdescs that currently function as wrappers around it[1].
Until we separately allocate memdescs, we won't be able to shrink the
page.

We're getting close to being able to allocate memdescs separately from
struct page, and I'd like to propose the topic to discuss how we want
to go about it. We already have Matthew's PoC for ptdescs[2]. I've taken
that on, but we're still running into issues for now...

Heres a non-exhaustive list of things I'd like to discuss:
- What memdescs to separate allocate for shrinking the page right now
- What are the implications of separate allocations
- Should we separately allocate one at a time, or all at once
- How the APIs would look
- Are there other generic fields to be cautious about (i.e. memcg)

I imagine Matthew might have a broader State of the Page talk too, so
this would be more in-depth. Possibly focused on ptdesc & slab (as the
two we're actively looking at right now).

[1] https://kernelnewbies.org/MatthewWilcox/Memdescs
[2] https://lore.kernel.org/linux-mm/20251020001652.2116669-1-willy@infradead.org/


                 reply	other threads:[~2026-02-25 23:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=aZ-DhWZbTnTnBh-D@fedora \
    --to=vishal.moola@gmail.com \
    --cc=david@kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=rppt@kernel.org \
    --cc=willy@infradead.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