From: Gregory Price <gourry@gourry.net>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: "Huang, Ying" <ying.huang@linux.alibaba.com>,
Joshua Hahn <joshua.hahnjy@gmail.com>,
lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, hyeonggon.yoo@sk.com,
honggyu.kim@sk.com, kernel-team@meta.com
Subject: Re: [LSF/MM/BPF TOPIC] Weighted interleave auto-tuning
Date: Fri, 14 Mar 2025 10:53:00 -0400 [thread overview]
Message-ID: <Z9RCzE7MqNEF9gPO@gourry-fedora-PF4VCD3F> (raw)
In-Reply-To: <20250314141541.00003fad@huawei.com>
On Fri, Mar 14, 2025 at 02:15:41PM +0000, Jonathan Cameron wrote:
> > > - Does this need to be in the kernel? A userspace daemon that monitors kernel
> > > metrics has the ability to make the changes (via the nodeN interfaces).
>
> If this was done in kernel, what metrics would make sense to drive this?
> Similar to hot page tracking we may run into contention with PMUs or similar and
> their other use cases.
>
Rather than directly affect weighted interleave, I think this stemmed
from the idea of a "smart policy" that adjusted allocations based on
bandwidth pressure and VMA permissions (code should be local, stack
should be local, heap could be interleaved - etc).
An example would be if DRAM bandwidth become pressured but CXL wasn't,
then maybe tossing some extra allocations directly to CXL would actually
decrease average latencies.
I'm not sure how we'd actually implement this in userland, and I think
this is ultimately MPOL_PONIES, but it's an interesting exploration.
Some of this context was lost as we worked on weighted interleave
auto-tuning.
~Gregory
next prev parent reply other threads:[~2025-03-14 14:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 18:50 Joshua Hahn
2025-03-13 15:57 ` Joshua Hahn
2025-03-14 10:08 ` Huang, Ying
2025-03-14 14:15 ` Jonathan Cameron
2025-03-14 14:53 ` Gregory Price [this message]
2025-03-14 15:11 ` Joshua Hahn
2025-03-14 15:02 ` Joshua Hahn
2025-03-27 11:11 ` Oscar Salvador
2025-03-27 12:39 ` Gregory Price
2025-03-27 15:46 ` Joshua Hahn
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=Z9RCzE7MqNEF9gPO@gourry-fedora-PF4VCD3F \
--to=gourry@gourry.net \
--cc=Jonathan.Cameron@huawei.com \
--cc=honggyu.kim@sk.com \
--cc=hyeonggon.yoo@sk.com \
--cc=joshua.hahnjy@gmail.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.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