From: SeongJae Park <sj@kernel.org>
To: SeongJae Park <sj@kernel.org>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org,
damon@lists.linux.dev, linux-kernel@vger.kernel.org,
Mel Gorman <mgorman@suse.de>,
Huang Ying <ying.huang@linux.alibaba.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
David Hildenbrand <david@kernel.org>,
Akinobu Mita <akinobu.mita@gmail.com>,
Andrew Paniakin <apanyaki@amazon.com>
Subject: Re: [LSF/MM/BPF TOPIC] Allowing NUMA hinting faults or alternatives to DAMON
Date: Wed, 6 May 2026 10:08:39 -0700 [thread overview]
Message-ID: <20260506170840.10882-1-sj@kernel.org> (raw)
In-Reply-To: <20260218054320.4570-1-sj@kernel.org>
Hello,
Slides for this topic is available at [1].
[1] https://lore.kernel.org/linux-mm/20260504070208.7106-1-sj@kernel.org/
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-05-06 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 5:43 [LSF/MM/BPF TOPIC] Allowing NUMA hinting faults or alternatives to DAMON SeongJae Park
2026-05-06 17:08 ` SeongJae Park [this message]
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=20260506170840.10882-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akinobu.mita@gmail.com \
--cc=apanyaki@amazon.com \
--cc=damon@lists.linux.dev \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mgorman@suse.de \
--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