[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <327ac0a2-35a7-4bde-aa7b-941bef2a5996@huawei.com>
Date: Tue, 18 Nov 2025 10:34:04 +0800
From: Jijie Shao <shaojijie@...wei.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: <shaojijie@...wei.com>, <davem@...emloft.net>, <edumazet@...gle.com>,
<pabeni@...hat.com>, <andrew+netdev@...n.ch>, <horms@...nel.org>,
<shenjian15@...wei.com>, <liuyonglong@...wei.com>, <chenhao418@...wei.com>,
<lantao5@...wei.com>, <huangdonghua3@...artners.com>,
<yangshuaisong@...artners.com>, <jonathan.cameron@...wei.com>,
<salil.mehta@...wei.com>, <netdev@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next 3/3] net: hibmcge: support pagepool for rx
on 2025/11/18 9:49, Jakub Kicinski wrote:
> On Fri, 14 Nov 2025 17:22:22 +0800 Jijie Shao wrote:
>> Support pagepool for rx, retaining the original
>> packet receiving process.
> Why retain the legacy path? Page pool is 7 years old, all major NIC
> vendors had dropped the support for non-page pool Rx path at this point.
> If there are bugs or performance regressions we will fix them and send
> the fixes to stable.
I have seen some drivers that retain the legacy packet receiving path.
The community does not recommend this practice now, and I will remove the legacy path in v2.
Thanks,
Jijie Shao
Powered by blists - more mailing lists