From: Gregory Price <gourry@gourry.net>
To: Jonathan Cameron <jonathan.cameron@huawei.com>
Cc: Hannes Reinecke <hare@suse.de>,
lsf-pc <lsf-pc@lists.linux-foundation.org>,
linux-cxl@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [LSF/MM/BPF TOPIC] Strategies for memory deallocation/movement for Dynamic Capacity Pooling
Date: Mon, 13 Apr 2026 17:10:57 -0400 [thread overview]
Message-ID: <ad1b4dVCgG27A5AK@gourry-fedora-PF4VCD3F> (raw)
In-Reply-To: <20260413164359.00001c86@huawei.com>
On Mon, Apr 13, 2026 at 04:43:59PM +0100, Jonathan Cameron wrote:
> >
> > So quite some things to discuss; however, not sure if this isn't too
> > much of an arcane topic which should rather be directed at places like
> > LPC. But I'll let the PC decide.
>
> Superficially feels a bit arcane, particularly as we are currently
> kicking untagged memory into the long grass as there are too many
> open questions on how to present it at all (e.g. related to Gregory's
> recent work on private nodes). On recent CXL sync calls the proposal
> has been to do tagged memory first and only support allocation of
> all memory with a given tag in one go and full release.
>
General consensus after last few months seems to be:
"While technically possible, untagged memory a bad idea for $REASONS"
I do not thing the private node case changes this, if anything it only
changes where the capacity ends up.
~Gregory
next prev parent reply other threads:[~2026-04-13 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 7:59 [LSF/MM/BPF TOPIC] Strategies for memory deallocation/movement for Dynamic Capacity Pooling Hannes Reinecke
2026-04-13 15:43 ` Jonathan Cameron
2026-04-13 21:10 ` Gregory Price [this message]
2026-04-14 7:08 ` Hannes Reinecke
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=ad1b4dVCgG27A5AK@gourry-fedora-PF4VCD3F \
--to=gourry@gourry.net \
--cc=hare@suse.de \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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