From: Jakub Kicinski <kuba@kernel.org>
To: Jijie Shao <shaojijie@huawei.com>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>,
<andrew+netdev@lunn.ch>, <horms@kernel.org>,
<shenjian15@huawei.com>, <liuyonglong@huawei.com>,
<chenhao418@huawei.com>, <lantao5@huawei.com>,
<huangdonghua3@h-partners.com>, <yangshuaisong@h-partners.com>,
<jonathan.cameron@huawei.com>, <salil.mehta@huawei.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next 3/3] net: hibmcge: support pagepool for rx
Date: Mon, 17 Nov 2025 17:49:57 -0800 [thread overview]
Message-ID: <20251117174957.631e7b40@kernel.org> (raw)
In-Reply-To: <20251114092222.2071583-4-shaojijie@huawei.com>
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.
--
pw-bot: cr
next prev parent reply other threads:[~2025-11-18 1:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 9:22 [PATCH net-next 0/3] net: hibmcge: Add tracepoint and pagepool for hibmcge driver Jijie Shao
2025-11-14 9:22 ` [PATCH net-next 1/3] net: hibmcge: Add tracepoint function to print some fields of rx_desc Jijie Shao
2025-11-14 9:22 ` [PATCH net-next 2/3] net: hibmcge: reduce packet drop under stress testing Jijie Shao
2025-11-14 9:22 ` [PATCH net-next 3/3] net: hibmcge: support pagepool for rx Jijie Shao
2025-11-18 1:49 ` Jakub Kicinski [this message]
2025-11-18 2:34 ` Jijie Shao
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=20251117174957.631e7b40@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=chenhao418@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=huangdonghua3@h-partners.com \
--cc=jonathan.cameron@huawei.com \
--cc=lantao5@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyonglong@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=salil.mehta@huawei.com \
--cc=shaojijie@huawei.com \
--cc=shenjian15@huawei.com \
--cc=yangshuaisong@h-partners.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).