[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a10a9239-ea4b-4a78-a5e6-d38d6ba749a9@redhat.com>
Date: Tue, 23 Dec 2025 11:27:45 +0100
From: Paolo Abeni <pabeni@...hat.com>
To: Byungchul Park <byungchul@...com>, Vlastimil Babka <vbabka@...e.cz>
Cc: linux-mm@...ck.org, akpm@...ux-foundation.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, kernel_team@...ynix.com, harry.yoo@...cle.com,
ast@...nel.org, daniel@...earbox.net, davem@...emloft.net, kuba@...nel.org,
hawk@...nel.org, john.fastabend@...il.com, sdf@...ichev.me,
saeedm@...dia.com, leon@...nel.org, tariqt@...dia.com, mbloch@...dia.com,
andrew+netdev@...n.ch, edumazet@...gle.com, david@...hat.com,
lorenzo.stoakes@...cle.com, Liam.Howlett@...cle.com, rppt@...nel.org,
surenb@...gle.com, mhocko@...e.com, horms@...nel.org, jackmanb@...gle.com,
hannes@...xchg.org, ziy@...dia.com, ilias.apalodimas@...aro.org,
willy@...radead.org, brauner@...nel.org, kas@...nel.org, yuzhao@...gle.com,
usamaarif642@...il.com, baolin.wang@...ux.alibaba.com,
almasrymina@...gle.com, toke@...hat.com, asml.silence@...il.com,
bpf@...r.kernel.org, linux-rdma@...r.kernel.org, sfr@...b.auug.org.au,
dw@...idwei.uk, ap420073@...il.com, dtatulea@...dia.com
Subject: Re: [PATCH v2 0/1] finalize removing the page pool members in struct
page
On 12/18/25 1:17 AM, Byungchul Park wrote:
> On Wed, Dec 17, 2025 at 02:43:07PM +0100, Vlastimil Babka wrote:
>> On 12/16/25 04:03, Byungchul Park wrote:
>>> Since this patch requires to use newly introduced APIs in net tree, I've
>>> been waiting for those to be ready in mm tree. Now that mm tree has
>>> been rebased so as to include the APIs, this patch can be merged to mm
>>> tree.
>>>
>>> This patch has been carried out in a separate thread so far for the
>>> reviews [1]:
>>>
>>> [1] https://lore.kernel.org/all/20251119012709.35895-1-byungchul@sk.com/
>>> ---
>>> Changes from v1:
>>> 1. Drop the finalizing patch removing the pp fields of struct
>>> page since I found that there is still code accessing a pp
>>> field via struct page. I will retry the finalizing patch
>>> after resolving the issue.
>>
>> Could we just make that necessary change of
>> drivers/net/ethernet/intel/ice/ice_ethtool.c part of this series and do it
>> all at once? We're changing both mm and net anyway.
>
> Yes. That's what I think it'd better do. 1/2 can be merged separately
> and Andrew took it. I'd like to re-post 'ice fix' + 2/2 in a series if
> it's allowed.
>
>> Also which tree will carry the series? I assume net will want to, as the
>
> I'm trying to apply changes focused on mm to mm tree, and changes
> focused on net to net tree. However, yeah, it'd make things simpler if
> I can go with a single series for mm tree.
I *think* that the ice patch should go via the net-next tree (and
ideally via the iwl tree first). Also it looks like both patches could
cause quite a bit of conflicts, as the page pool code and the ice driver
are touched frequently.
Perhaps the easier/cleaner way to handle this is publishing a stable
branch somewhere based on the most recent common ancestor and let both
the mm and the net-next tree pull from it? Other opinions welcome!
Anyway the net-next tree is and will be closed up to Jan 2.
Cheers,
Paolo
Powered by blists - more mailing lists