All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: mkubecek@suse.cz, andrew@lunn.ch, jiri@resnulli.us,
	przemyslaw.kitszel@intel.com, linux-kernel@vger.kernel.org,
	edumazet@google.com, michal.kubiak@intel.com,
	anthony.l.nguyen@intel.com, paul.greenwalt@intel.com,
	vladimir.oltean@nxp.com, kuba@kernel.org, netdev@vger.kernel.org,
	pabeni@redhat.com, davem@davemloft.net,
	intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] [PATCH net-next 0/2] idpf: add get/set for Ethtool's header split ringparam
Date: Thu, 14 Dec 2023 02:40:25 +0000	[thread overview]
Message-ID: <170252162566.2494.10156204711336606229.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231212142752.935000-1-aleksander.lobakin@intel.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.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


_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, michal.kubiak@intel.com,
	przemyslaw.kitszel@intel.com, vladimir.oltean@nxp.com,
	andrew@lunn.ch, mkubecek@suse.cz, jiri@resnulli.us,
	paul.greenwalt@intel.com, anthony.l.nguyen@intel.com,
	intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] idpf: add get/set for Ethtool's header split ringparam
Date: Thu, 14 Dec 2023 02:40:25 +0000	[thread overview]
Message-ID: <170252162566.2494.10156204711336606229.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231212142752.935000-1-aleksander.lobakin@intel.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.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



  parent reply	other threads:[~2023-12-14  2:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12 14:27 [Intel-wired-lan] [PATCH net-next 0/2] idpf: add get/set for Ethtool's header split ringparam Alexander Lobakin
2023-12-12 14:27 ` Alexander Lobakin
2023-12-12 14:27 ` [Intel-wired-lan] [PATCH net-next 1/2] ethtool: add SET for TCP_DATA_SPLIT ringparam Alexander Lobakin
2023-12-12 14:27   ` Alexander Lobakin
2023-12-12 14:27 ` [Intel-wired-lan] [PATCH net-next 2/2] idpf: add get/set for Ethtool's header split ringparam Alexander Lobakin
2023-12-12 14:27   ` Alexander Lobakin
2023-12-12 18:16 ` [Intel-wired-lan] [PATCH net-next 0/2] " Jakub Kicinski
2023-12-12 18:16   ` Jakub Kicinski
2023-12-14  2:40 ` patchwork-bot+netdevbpf [this message]
2023-12-14  2:40   ` patchwork-bot+netdevbpf

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=170252162566.2494.10156204711336606229.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=aleksander.lobakin@intel.com \
    --cc=andrew@lunn.ch \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.kubiak@intel.com \
    --cc=mkubecek@suse.cz \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=paul.greenwalt@intel.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=vladimir.oltean@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.