[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3360625b-2f95-45d8-8aa2-a7c5a4811786@redhat.com>
Date: Thu, 22 May 2025 18:08:46 +0200
From: David Hildenbrand <david@...hat.com>
To: Gregory Price <gourry@...rry.net>
Cc: Bharata B Rao <bharata@....com>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, Jonathan.Cameron@...wei.com, dave.hansen@...el.com,
hannes@...xchg.org, mgorman@...hsingularity.net, mingo@...hat.com,
peterz@...radead.org, raghavendra.kt@....com, riel@...riel.com,
rientjes@...gle.com, sj@...nel.org, weixugc@...gle.com, willy@...radead.org,
ying.huang@...ux.alibaba.com, ziy@...dia.com, dave@...olabs.net,
nifan.cxl@...il.com, joshua.hahnjy@...il.com, xuezhengchu@...wei.com,
yiannis@...corp.com, akpm@...ux-foundation.org
Subject: Re: [RFC PATCH v0 1/2] migrate: implement
migrate_misplaced_folio_batch
On 22.05.25 18:03, Gregory Price wrote:
> On Thu, May 22, 2025 at 05:59:01PM +0200, David Hildenbrand wrote:
>>> +int migrate_misplaced_folio_batch(struct list_head *folio_list, int node)
>>
>> "migrate_misplaced_folios" ?
>>
>> :)
>
> something something brevity is the soul of wit
>
> I think i went with _batch to match surrounding code (been a while since
> I wrote this), but I don't have strong feelings either way.
I think we have migrate_pages_batch() and migrate_pages_sync() because
... they are called from migrate_pages() :)
For something that "simply" calls migrate_pages() right now, probably we
should just call migrate_folios().
But maybe you were referring to yet another set of "_batch" functions.
--
Cheers,
David / dhildenb
Powered by blists - more mailing lists