All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oscar Salvador <osalvador@suse.de>
To: Joshua Hahn <joshua.hahnjy@gmail.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, gourry@gourry.net,
	ying.huang@linux.alibaba.com, hyeonggon.yoo@sk.com,
	honggyu.kim@sk.com, kernel-team@meta.com
Subject: Re: [LSF/MM/BPF TOPIC] Weighted interleave auto-tuning
Date: Thu, 27 Mar 2025 12:11:55 +0100	[thread overview]
Message-ID: <Z-Uye2V-6Urz2IIA@localhost.localdomain> (raw)
In-Reply-To: <20250109185048.28587-1-joshua.hahnjy@gmail.com>

On Thu, Jan 09, 2025 at 01:50:48PM -0500, Joshua Hahn wrote:
> Hello everyone, I hope everyone has had a great start to 2025!

Hi Joshua,

as discussed in the LSFMM about how you can react to nodes becoming
memory{aware,less}, you can register a hotplug memory notifier, as
memory-tiering currently does.

The current use of the hotplug memory notifier by some consumers (e.g:
memory-tiering, slub, etc) is a bit suboptimal, as they only care about
nodes changing its memory state, yet they get notified for every
{online,offline}_pages operation.

I came up with [1]

I did not publish it yet upstream because I wanted to discuss it a bit
with David, but you can give it a try to see if it works for you.
But till it is upstream, you will have to use the hotplug memory
notifier.

[1] https://github.com/leberus/linux.git numa-node-notifier 

-- 
Oscar Salvador
SUSE Labs


  parent reply	other threads:[~2025-03-27 11:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-09 18:50 [LSF/MM/BPF TOPIC] Weighted interleave auto-tuning 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
2025-03-14 15:11       ` Joshua Hahn
2025-03-14 15:02     ` Joshua Hahn
2025-03-27 11:11 ` Oscar Salvador [this message]
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=Z-Uye2V-6Urz2IIA@localhost.localdomain \
    --to=osalvador@suse.de \
    --cc=gourry@gourry.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.