From: Yee Li <seven.yi.lee@gmail.com>
To: Joshua Hahn <joshua.hahnjy@gmail.com>
Cc: akpm@linux-foundation.org, david@kernel.org,
dan.j.williams@intel.com, ying.huang@linux.alibaba.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Jonathan.Cameron@huawei.com, linux-cxl@vger.kernel.org,
dave.jiang@intel.com, gourry@gourry.next
Subject: Re: [PATCH] mm/mempolicy: add sysfs interface to override NUMA node bandwidth
Date: Fri, 13 Mar 2026 11:39:41 +0800 [thread overview]
Message-ID: <06535c30-ce87-43b2-9670-53e56ca04c3c@gmail.com> (raw)
In-Reply-To: <20260312150022.1373486-1-joshua.hahnjy@gmail.com>
Hi Joshua,
Thanks for your feedback and kind wishes.
> I just wanted to touch on this. Is this true? Weighted interleave already
> exposes sysfs that lets the user set the weights they want. On one hand
> I think it would be helpful for there to be a tool to see what the
> effects of setting bandwidth information on a system could be, if it
> had other side effects. I'm not sure if there is a strong case to do this
> purely for weighted interleave auto-tuning, which already has a manual
> weight override and pretty simple calculations : -)
I agree — writing a small userspace tool to compute the weights based on
actual measured bandwidths (from mlc or stream) is a really good approach.
> Thank you for the helpful clarification. Just to be sure, are there
> other intended things that the user can test other than what weights
> weighted interleave would resolve to?
We can continue DRAM + CXL weighted interleave performance testing
later, following Gregory Price's experiments [1].
[1] Link:
https://lore.kernel.org/linux-mm/20240103224209.2541-1-gregory.price@memverge.com/
next prev parent reply other threads:[~2026-03-13 3:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 9:12 YeeLi
2026-03-12 9:42 ` Huang, Ying
2026-03-12 10:26 ` Yee Li
2026-03-12 11:58 ` Jonathan Cameron
2026-03-13 3:05 ` Yee Li
2026-03-12 15:00 ` Joshua Hahn
2026-03-12 15:05 ` Joshua Hahn
2026-03-13 3:39 ` Yee Li [this message]
2026-03-12 16:12 ` Gregory Price
2026-03-13 3:51 ` Yee Li
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=06535c30-ce87-43b2-9670-53e56ca04c3c@gmail.com \
--to=seven.yi.lee@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=david@kernel.org \
--cc=gourry@gourry.next \
--cc=joshua.hahnjy@gmail.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ying.huang@linux.alibaba.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