From: Gregory Price <gourry@gourry.net>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: Rakie Kim <rakie.kim@sk.com>,
joshua.hahnjy@gmail.com, akpm@linux-foundation.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-cxl@vger.kernel.org, dan.j.williams@intel.com,
ying.huang@linux.alibaba.com, kernel_team@skhynix.com,
honggyu.kim@sk.com, yunjeong.mun@sk.com,
Keith Busch <kbusch@kernel.org>,
Jerome Glisse <jglisse@google.com>
Subject: Re: [RFC] Add per-socket weight support for multi-socket systems in weighted interleave
Date: Fri, 9 May 2025 12:29:53 -0400 [thread overview]
Message-ID: <aB4tgSP2r-2s-1ce@gourry-fedora-PF4VCD3F> (raw)
In-Reply-To: <20250509123131.0000051b@huawei.com>
On Fri, May 09, 2025 at 12:31:31PM +0100, Jonathan Cameron wrote:
> Anyhow, short term I'd like us to revisit what info we present from HMAT
> (and what we get from CXL topology descriptions which have pretty much everything we
> might want).
>
Generally I think if there is new data to enrich the environment, we
should try to collect that first before laying down requirements for new
interfaces / policies. So tl;dr: "This first, please!"
(I know we discussed this at LSFMM, dropped out of my memory banks)
~Gregory
next prev parent reply other threads:[~2025-05-09 16:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 9:35 rakie.kim
2025-05-07 16:38 ` Gregory Price
2025-05-08 6:30 ` Rakie Kim
2025-05-08 15:12 ` Gregory Price
2025-05-09 2:30 ` Rakie Kim
2025-05-09 5:49 ` Gregory Price
2025-05-12 8:22 ` Rakie Kim
2025-05-09 11:31 ` Jonathan Cameron
2025-05-09 16:29 ` Gregory Price [this message]
2025-05-12 8:23 ` Rakie Kim
2025-05-12 8:23 ` Rakie Kim
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=aB4tgSP2r-2s-1ce@gourry-fedora-PF4VCD3F \
--to=gourry@gourry.net \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=honggyu.kim@sk.com \
--cc=jglisse@google.com \
--cc=joshua.hahnjy@gmail.com \
--cc=kbusch@kernel.org \
--cc=kernel_team@skhynix.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rakie.kim@sk.com \
--cc=ying.huang@linux.alibaba.com \
--cc=yunjeong.mun@sk.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