All of lore.kernel.org
 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, bpf@vger.kernel.org
Subject: Re: [PATCH net 0/6][pull request] Intel Wired LAN Driver Updates 2021-12-17
Date: Sat, 18 Dec 2021 12:30:10 +0000	[thread overview]
Message-ID: <163983061078.29880.10453820135462050582.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211217193114.392106-1-anthony.l.nguyen@intel.com>

Hello:

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

On Fri, 17 Dec 2021 11:31:08 -0800 you wrote:
> Maciej Fijalkowski says:
> 
> It seems that previous [0] Rx fix was not enough and there are still
> issues with AF_XDP Rx ZC support in ice driver. Elza reported that for
> multiple XSK sockets configured on a single netdev, some of them were
> becoming dead after a while. We have spotted more things that needed to
> be addressed this time. More of information can be found in particular
> commit messages.
> 
> [...]

Here is the summary with links:
  - [net,1/6] ice: xsk: return xsk buffers back to pool when cleaning the ring
    https://git.kernel.org/netdev/net/c/afe8a3ba85ec
  - [net,2/6] ice: xsk: allocate separate memory for XDP SW ring
    https://git.kernel.org/netdev/net/c/617f3e1b588c
  - [net,3/6] ice: remove dead store on XSK hotpath
    https://git.kernel.org/netdev/net/c/0708b6facb4d
  - [net,4/6] ice: xsk: do not clear status_error0 for ntu + nb_buffs descriptor
    https://git.kernel.org/netdev/net/c/8b51a13c37c2
  - [net,5/6] ice: xsk: allow empty Rx descriptors on XSK ZC data path
    https://git.kernel.org/netdev/net/c/8bea15ab7485
  - [net,6/6] ice: xsk: fix cleaned_count setting
    https://git.kernel.org/netdev/net/c/dcbaf72aa423

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-12-18 12:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17 19:31 [PATCH net 0/6][pull request] Intel Wired LAN Driver Updates 2021-12-17 Tony Nguyen
2021-12-17 19:31 ` [PATCH net 1/6] ice: xsk: return xsk buffers back to pool when cleaning the ring Tony Nguyen
2021-12-17 19:31 ` [PATCH net 2/6] ice: xsk: allocate separate memory for XDP SW ring Tony Nguyen
2021-12-17 19:31 ` [PATCH net 3/6] ice: remove dead store on XSK hotpath Tony Nguyen
2021-12-17 19:31 ` [PATCH net 4/6] ice: xsk: do not clear status_error0 for ntu + nb_buffs descriptor Tony Nguyen
2021-12-17 19:31 ` [PATCH net 5/6] ice: xsk: allow empty Rx descriptors on XSK ZC data path Tony Nguyen
2021-12-17 19:31 ` [PATCH net 6/6] ice: xsk: fix cleaned_count setting Tony Nguyen
2021-12-18 12:30 ` 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=163983061078.29880.10453820135462050582.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@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=kuba@kernel.org \
    --cc=maciej.fijalkowski@intel.com \
    --cc=magnus.karlsson@intel.com \
    --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 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.