From: SeongJae Park <sj@kernel.org>
To: SeongJae Park <sj@kernel.org>
Cc: Bijan Tabatabai <bijan311@gmail.com>,
damon@lists.linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
david@redhat.com, ziy@nvidia.com, matthew.brost@intel.com,
joshua.hahnjy@gmail.com, rakie.kim@sk.com, byungchul@sk.com,
gourry@gourry.net, ying.huang@linux.alibaba.com,
apopple@nvidia.com, bijantabatab@micron.com,
venkataravis@micron.com, emirakhur@micron.com,
ajayjoshi@micron.com, vtavarespetr@micron.com
Subject: Re: [RFC PATCH v2 0/2] mm/damon/paddr: Allow interleaving in migrate_{hot,cold} actions
Date: Sat, 21 Jun 2025 10:36:39 -0700 [thread overview]
Message-ID: <20250621173639.35906-1-sj@kernel.org> (raw)
In-Reply-To: <20250620231324.99607-1-sj@kernel.org>
On Fri, 20 Jun 2025 16:13:24 -0700 SeongJae Park <sj@kernel.org> wrote:
> On Fri, 20 Jun 2025 16:47:26 -0500 Bijan Tabatabai <bijan311@gmail.com> wrote:
[...]
> > That sounds good to me! Having a prototype from you for the sysfs
> > interface would certainly be helpful, but if you're busy, I can take a
> > pass at it as well.
>
> Great. I will try to do this by this weekend.
I just posted an RFC for this:
https://lore.kernel.org/20250621173131.23917-1-sj@kernel.org
Note that I didn't run exhaustive tests with it, so it may have silly bugs. I
believe it could let you knwo what I'm thinking better than my cheap talks,
though ;)
Thanks,
SJ
[...]
next prev parent reply other threads:[~2025-06-21 17:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 18:04 [RFC PATCH v2 0/2] mm/damon/paddr: Allow interleaving in migrate_{hot,cold} actions Bijan Tabatabai
2025-06-20 18:04 ` [RFC PATCH v2 1/2] mm/mempolicy: Expose get_il_weight() to MM Bijan Tabatabai
2025-06-23 19:06 ` Gregory Price
2025-06-23 19:14 ` David Hildenbrand
2025-06-23 19:38 ` Gregory Price
2025-06-24 10:58 ` Huang, Ying
2025-06-20 18:04 ` [RFC PATCH v2 2/2] mm/damon/paddr: Allow multiple migrate targets Bijan Tabatabai
2025-06-21 18:02 ` SeongJae Park
2025-06-21 18:11 ` SeongJae Park
2025-06-23 14:08 ` Joshua Hahn
2025-06-23 16:50 ` SeongJae Park
2025-06-23 14:27 ` Bijan Tabatabai
2025-06-23 16:52 ` SeongJae Park
2025-06-23 14:16 ` Bijan Tabatabai
2025-06-23 17:52 ` SeongJae Park
2025-06-23 23:15 ` Bijan Tabatabai
2025-06-24 0:34 ` SeongJae Park
2025-06-24 16:01 ` Bijan Tabatabai
2025-06-24 22:33 ` SeongJae Park
2025-06-20 20:21 ` [RFC PATCH v2 0/2] mm/damon/paddr: Allow interleaving in migrate_{hot,cold} actions SeongJae Park
2025-06-20 21:47 ` Bijan Tabatabai
2025-06-20 23:13 ` SeongJae Park
2025-06-21 17:36 ` SeongJae Park [this message]
2025-06-23 14:39 ` Bijan Tabatabai
2025-06-23 16:32 ` SeongJae Park
2025-06-23 19:28 ` Gregory Price
2025-06-23 23:21 ` Bijan Tabatabai
2025-06-26 19:13 ` Gregory Price
2025-06-23 13:45 ` Joshua Hahn
2025-06-23 14:57 ` Bijan Tabatabai
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=20250621173639.35906-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=ajayjoshi@micron.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=bijan311@gmail.com \
--cc=bijantabatab@micron.com \
--cc=byungchul@sk.com \
--cc=damon@lists.linux.dev \
--cc=david@redhat.com \
--cc=emirakhur@micron.com \
--cc=gourry@gourry.net \
--cc=joshua.hahnjy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.brost@intel.com \
--cc=rakie.kim@sk.com \
--cc=venkataravis@micron.com \
--cc=vtavarespetr@micron.com \
--cc=ying.huang@linux.alibaba.com \
--cc=ziy@nvidia.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;
as well as URLs for NNTP newsgroup(s).