From: Donet Tom <donettom@linux.ibm.com>
To: Gregory Price <gourry@gourry.net>, Bharata B Rao <bharata@amd.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Jonathan.Cameron@huawei.com, dave.hansen@intel.com,
mgorman@techsingularity.net, mingo@redhat.com,
peterz@infradead.org, raghavendra.kt@amd.com, riel@surriel.com,
rientjes@google.com, sj@kernel.org, weixugc@google.com,
willy@infradead.org, ying.huang@linux.alibaba.com,
ziy@nvidia.com, dave@stgolabs.net, nifan.cxl@gmail.com,
xuezhengchu@huawei.com, yiannis@zptcorp.com,
akpm@linux-foundation.org, david@redhat.com, byungchul@sk.com,
kinseyho@google.com, joshua.hahnjy@gmail.com, yuanchu@google.com,
balbirs@nvidia.com, alok.rathore@samsung.com, shivankg@amd.com
Subject: Re: [RFC PATCH v6 2/5] mm: migrate: Add migrate_misplaced_folios_batch()
Date: Wed, 22 Apr 2026 09:34:27 +0530 [thread overview]
Message-ID: <45b93560-acdb-4552-bac5-bd085d778085@linux.ibm.com> (raw)
In-Reply-To: <aehCjOtPtt_wrQlv@gourry-fedora-PF4VCD3F>
Hi Gregory
On 4/22/26 9:07 AM, Gregory Price wrote:
> On Wed, Apr 22, 2026 at 08:56:59AM +0530, Bharata B Rao wrote:
>> On 21-Apr-26 9:35 PM, Gregory Price wrote:
>>> On Tue, Apr 21, 2026 at 08:55:02PM +0530, Donet Tom wrote:
>>>>> +/**
>>>>> + * migrate_misplaced_folios_batch() - Batch variant of migrate_misplaced_folio
>>>>> + * Attempts to migrate a folio list to the specified destination.
>>>>> + * @folio_list: Isolated list of folios to be batch-migrated.
>>>>> + * @node: The NUMA node ID to where the folios should be migrated.
>>>>> + *
>>>>> + * Caller is expected to have isolated the folios by calling
>>>>> + * migrate_misplaced_folio_prepare(), which will result in an
>>>>> + * elevated reference count on the folio. All the isolated folios
>>>>> + * in the list must belong to the same memcg so that NUMA_PAGE_MIGRATE
>>>>> + * stat can be attributed correctly to the memcg.
>> ^ This is the expectation from the caller. pghot caller ensures this.
>> I could add a debug check in this routine to verify if that is indeed so.
>>
> Wondering if the interface name should somehow reflect this as well, to
> make it a bit clearer.
I agree—this would make the interface clearer.
-Donet
>
> ~Gregory
next prev parent reply other threads:[~2026-04-22 4:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 9:50 [RFC PATCH v6 0/5] mm: Hot page tracking and promotion infrastructure Bharata B Rao
2026-03-23 9:51 ` [RFC PATCH v6 1/5] mm: migrate: Allow misplaced migration without VMA Bharata B Rao
2026-03-23 9:51 ` [RFC PATCH v6 2/5] mm: migrate: Add migrate_misplaced_folios_batch() Bharata B Rao
2026-03-26 5:50 ` Bharata B Rao
2026-04-21 15:25 ` Donet Tom
2026-04-21 16:05 ` Gregory Price
2026-04-22 3:26 ` Bharata B Rao
2026-04-22 3:37 ` Gregory Price
2026-04-22 4:04 ` Donet Tom [this message]
2026-04-22 4:15 ` Bharata B Rao
2026-03-23 9:51 ` [RFC PATCH v6 3/5] mm: Hot page tracking and promotion - pghot Bharata B Rao
2026-03-23 9:51 ` [RFC PATCH v6 4/5] mm: pghot: Precision mode for pghot Bharata B Rao
2026-03-26 10:41 ` Bharata B Rao
2026-03-23 9:51 ` [RFC PATCH v6 5/5] mm: sched: move NUMA balancing tiering promotion to pghot Bharata B Rao
2026-03-30 4:46 ` Bharata B Rao
2026-03-23 9:56 ` [RFC PATCH v6 0/5] mm: Hot page tracking and promotion infrastructure Bharata B Rao
2026-03-23 9:58 ` Bharata B Rao
2026-03-23 9:59 ` Bharata B Rao
2026-03-23 10:01 ` Bharata B Rao
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=45b93560-acdb-4552-bac5-bd085d778085@linux.ibm.com \
--to=donettom@linux.ibm.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=alok.rathore@samsung.com \
--cc=balbirs@nvidia.com \
--cc=bharata@amd.com \
--cc=byungchul@sk.com \
--cc=dave.hansen@intel.com \
--cc=dave@stgolabs.net \
--cc=david@redhat.com \
--cc=gourry@gourry.net \
--cc=joshua.hahnjy@gmail.com \
--cc=kinseyho@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@redhat.com \
--cc=nifan.cxl@gmail.com \
--cc=peterz@infradead.org \
--cc=raghavendra.kt@amd.com \
--cc=riel@surriel.com \
--cc=rientjes@google.com \
--cc=shivankg@amd.com \
--cc=sj@kernel.org \
--cc=weixugc@google.com \
--cc=willy@infradead.org \
--cc=xuezhengchu@huawei.com \
--cc=yiannis@zptcorp.com \
--cc=ying.huang@linux.alibaba.com \
--cc=yuanchu@google.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