[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<170252162566.2494.10156204711336606229.git-patchwork-notify@kernel.org>
Date: Thu, 14 Dec 2023 02:40:25 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Alexander Lobakin <aleksander.lobakin@...el.com>
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, michal.kubiak@...el.com, przemyslaw.kitszel@...el.com,
vladimir.oltean@....com, andrew@...n.ch, mkubecek@...e.cz, jiri@...nulli.us,
paul.greenwalt@...el.com, anthony.l.nguyen@...el.com,
intel-wired-lan@...ts.osuosl.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 0/2] idpf: add get/set for Ethtool's header split
ringparam
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Tue, 12 Dec 2023 15:27:50 +0100 you wrote:
> Currently, the header split feature (putting headers in one smaller
> buffer and then the data in a separate bigger one) is always enabled
> in idpf when supported.
> One may want to not have fragmented frames per each packet, for example,
> to avoid XDP frags. To better optimize setups for particular workloads,
> add ability to switch the header split state on and off via Ethtool's
> ringparams, as well as to query the current status.
> There's currently only GET in the Ethtool Netlink interface for now,
> so add SET first. I suspect idpf is not the only one supporting this.
>
> [...]
Here is the summary with links:
- [net-next,1/2] ethtool: add SET for TCP_DATA_SPLIT ringparam
https://git.kernel.org/netdev/net-next/c/50d73710715d
- [net-next,2/2] idpf: add get/set for Ethtool's header split ringparam
https://git.kernel.org/netdev/net-next/c/9b1aa3ef2328
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists