netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Gerhard Engleder <gerhard@engleder-embedded.com>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org, davem@davemloft.net,
	kuba@kernel.org, edumazet@google.com, pabeni@redhat.com,
	bjorn@kernel.org, magnus.karlsson@intel.com,
	maciej.fijalkowski@intel.com, jonathan.lemon@gmail.com
Subject: Re: [PATCH net-next v4 0/6] tsnep: XDP socket zero-copy support
Date: Tue, 25 Apr 2023 01:50:20 +0000	[thread overview]
Message-ID: <168238742034.25988.7042719252736011480.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230421194656.48063-1-gerhard@engleder-embedded.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri, 21 Apr 2023 21:46:50 +0200 you wrote:
> Implement XDP socket zero-copy support for tsnep driver. I tried to
> follow existing drivers like igc as far as possible. But one main
> difference is that tsnep does not need any reconfiguration for XDP BPF
> program setup. So I decided to keep this behavior no matter if a XSK
> pool is used or not. As a result, tsnep starts using the XSK pool even
> if no XDP BPF program is available.
> 
> [...]

Here is the summary with links:
  - [net-next,v4,1/6] tsnep: Replace modulo operation with mask
    https://git.kernel.org/netdev/net-next/c/42fb2962b4a6
  - [net-next,v4,2/6] tsnep: Rework TX/RX queue initialization
    https://git.kernel.org/netdev/net-next/c/33b0ee02c84c
  - [net-next,v4,3/6] tsnep: Add functions for queue enable/disable
    https://git.kernel.org/netdev/net-next/c/2ea0a282ba09
  - [net-next,v4,4/6] tsnep: Move skb receive action to separate function
    https://git.kernel.org/netdev/net-next/c/c2d64697f41b
  - [net-next,v4,5/6] tsnep: Add XDP socket zero-copy RX support
    https://git.kernel.org/netdev/net-next/c/3fc2333933fd
  - [net-next,v4,6/6] tsnep: Add XDP socket zero-copy TX support
    https://git.kernel.org/netdev/net-next/c/cd275c236b3f

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-04-25  1:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-21 19:46 [PATCH net-next v4 0/6] tsnep: XDP socket zero-copy support Gerhard Engleder
2023-04-21 19:46 ` [PATCH net-next v4 1/6] tsnep: Replace modulo operation with mask Gerhard Engleder
2023-04-21 19:46 ` [PATCH net-next v4 2/6] tsnep: Rework TX/RX queue initialization Gerhard Engleder
2023-04-21 19:46 ` [PATCH net-next v4 3/6] tsnep: Add functions for queue enable/disable Gerhard Engleder
2023-04-21 19:46 ` [PATCH net-next v4 4/6] tsnep: Move skb receive action to separate function Gerhard Engleder
2023-04-21 19:46 ` [PATCH net-next v4 5/6] tsnep: Add XDP socket zero-copy RX support Gerhard Engleder
2023-04-21 19:46 ` [PATCH net-next v4 6/6] tsnep: Add XDP socket zero-copy TX support Gerhard Engleder
2023-04-25  1:50 ` 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=168238742034.25988.7042719252736011480.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bjorn@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gerhard@engleder-embedded.com \
    --cc=jonathan.lemon@gmail.com \
    --cc=kuba@kernel.org \
    --cc=maciej.fijalkowski@intel.com \
    --cc=magnus.karlsson@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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).