bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
	maciej.fijalkowski@intel.com, magnus.karlsson@intel.com,
	ast@kernel.org, daniel@iogearbox.net, hawk@kernel.org,
	john.fastabend@gmail.com, andrii@kernel.org, kpsingh@kernel.org,
	kafai@fb.com, yhs@fb.com, songliubraving@fb.com,
	bpf@vger.kernel.org
Subject: Re: [PATCH net-next 0/9][pull request] 100GbE Intel Wired LAN Driver Updates 2021-10-15
Date: Sat, 16 Oct 2021 08:00:15 +0000	[thread overview]
Message-ID: <163437121507.28528.14004144964081319278.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211015162908.145341-1-anthony.l.nguyen@intel.com>

Hello:

This series was applied to netdev/net-next.git (master)
by Tony Nguyen <anthony.l.nguyen@intel.com>:

On Fri, 15 Oct 2021 09:28:59 -0700 you wrote:
> This series contains updates to ice driver only.
> 
> Maciej makes improvements centered around XDP. Changes include removing
> an unused field from the ring structure, creating separate Tx and Rx
> ring structures, and using ice_for_each macros for iterating rings.
> Some calls and parameters are changed to reduce unneeded overhead for
> further optimization. New fields are added for tracking to aid in
> improving workloads. He also unifies XDP indexing to a single
> methodology and adds a fallback patch when XDP Tx queue per CPU is not
> met.
> 
> [...]

Here is the summary with links:
  - [net-next,1/9] ice: remove ring_active from ice_ring
    https://git.kernel.org/netdev/net-next/c/e93d1c37a85b
  - [net-next,2/9] ice: move ice_container_type onto ice_ring_container
    https://git.kernel.org/netdev/net-next/c/dc23715cf30a
  - [net-next,3/9] ice: split ice_ring onto Tx/Rx separate structs
    https://git.kernel.org/netdev/net-next/c/e72bba21355d
  - [net-next,4/9] ice: unify xdp_rings accesses
    https://git.kernel.org/netdev/net-next/c/0bb4f9ecadd4
  - [net-next,5/9] ice: do not create xdp_frame on XDP_TX
    https://git.kernel.org/netdev/net-next/c/a55e16fa330a
  - [net-next,6/9] ice: propagate xdp_ring onto rx_ring
    https://git.kernel.org/netdev/net-next/c/eb087cd82864
  - [net-next,7/9] ice: optimize XDP_TX workloads
    https://git.kernel.org/netdev/net-next/c/9610bd988df9
  - [net-next,8/9] ice: introduce XDP_TX fallback path
    https://git.kernel.org/netdev/net-next/c/22bf877e528f
  - [net-next,9/9] ice: make use of ice_for_each_* macros
    https://git.kernel.org/netdev/net-next/c/2faf63b650bb

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-10-16  8:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-15 16:28 [PATCH net-next 0/9][pull request] 100GbE Intel Wired LAN Driver Updates 2021-10-15 Tony Nguyen
2021-10-15 16:29 ` [PATCH net-next 1/9] ice: remove ring_active from ice_ring Tony Nguyen
2021-10-15 16:29 ` [PATCH net-next 2/9] ice: move ice_container_type onto ice_ring_container Tony Nguyen
2021-10-15 16:29 ` [PATCH net-next 3/9] ice: split ice_ring onto Tx/Rx separate structs Tony Nguyen
2021-10-15 16:29 ` [PATCH net-next 4/9] ice: unify xdp_rings accesses Tony Nguyen
2021-10-15 16:29 ` [PATCH net-next 5/9] ice: do not create xdp_frame on XDP_TX Tony Nguyen
2021-10-15 16:29 ` [PATCH net-next 6/9] ice: propagate xdp_ring onto rx_ring Tony Nguyen
2021-10-15 16:29 ` [PATCH net-next 7/9] ice: optimize XDP_TX workloads Tony Nguyen
2021-10-15 16:29 ` [PATCH net-next 8/9] ice: introduce XDP_TX fallback path Tony Nguyen
2021-10-15 16:29 ` [PATCH net-next 9/9] ice: make use of ice_for_each_* macros Tony Nguyen
2021-10-16  8:00 ` 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=163437121507.28528.14004144964081319278.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=anthony.l.nguyen@intel.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=hawk@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=kuba@kernel.org \
    --cc=maciej.fijalkowski@intel.com \
    --cc=magnus.karlsson@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=songliubraving@fb.com \
    --cc=yhs@fb.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).