From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-doc@vger.kernel.org, chenhao288@hisilicon.com,
huangguangbin2@huawei.com, idosch@nvidia.com, corbet@lwn.net
Subject: Re: [PATCH net-next 0/2] ethtool: add header/data split indication
Date: Fri, 28 Jan 2022 15:10:17 +0000 [thread overview]
Message-ID: <164338261734.2420.245861558495547207.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220127184300.490747-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 27 Jan 2022 10:42:58 -0800 you wrote:
> TCP ZC Rx requires data to be placed neatly into pages, separate
> from the networking headers. This is not supported by most devices
> so to make deployment easy this set adds a way for the driver to
> report support for this feature thru ethtool.
>
> The larger scope of configuring splitting headers and data, or DMA
> scatter seems dauntingly broad, so this set focuses specifically
> on the question "is this device usable with TCP ZC Rx?".
>
> [...]
Here is the summary with links:
- [net-next,1/2] ethtool: add header/data split indication
https://git.kernel.org/netdev/net-next/c/9690ae604290
- [net-next,2/2] bnxt: report header-data split state
https://git.kernel.org/netdev/net-next/c/b370517e5233
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-01-28 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 18:42 [PATCH net-next 0/2] ethtool: add header/data split indication Jakub Kicinski
2022-01-27 18:42 ` [PATCH net-next 1/2] " Jakub Kicinski
2022-01-27 18:43 ` [PATCH net-next 2/2] bnxt: report header-data split state Jakub Kicinski
2022-01-28 15:10 ` patchwork-bot+netdevbpf [this message]
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=164338261734.2420.245861558495547207.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=chenhao288@hisilicon.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=huangguangbin2@huawei.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).