From: Jason Xing <kerneljasonxing@gmail.com>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, bjorn@kernel.org, magnus.karlsson@intel.com,
maciej.fijalkowski@intel.com, jonathan.lemon@gmail.com,
sdf@fomichev.me, ast@kernel.org, daniel@iogearbox.net,
hawk@kernel.org, john.fastabend@gmail.com, joe@dama.to,
willemdebruijn.kernel@gmail.com
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org,
Jason Xing <kernelxing@tencent.com>
Subject: [PATCH net-next v6 0/2] net: xsk: update tx queue consumer
Date: Thu, 3 Jul 2025 22:17:10 +0800 [thread overview]
Message-ID: <20250703141712.33190-1-kerneljasonxing@gmail.com> (raw)
From: Jason Xing <kernelxing@tencent.com>
Patch 1 makes sure the consumer is updated at the end of generic xmit.
Patch 2 adds corresponding test.
Jason Xing (2):
net: xsk: update tx queue consumer immediately after transmission
selftests/bpf: add a new test to check the consumer update case
net/xdp/xsk.c | 17 ++++---
tools/testing/selftests/bpf/xskxceiver.c | 56 +++++++++++++++++++++++-
tools/testing/selftests/bpf/xskxceiver.h | 1 +
3 files changed, 66 insertions(+), 8 deletions(-)
--
2.41.3
next reply other threads:[~2025-07-03 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 14:17 Jason Xing [this message]
2025-07-03 14:17 ` [PATCH net-next v6 1/2] net: xsk: update tx queue consumer immediately after transmission Jason Xing
2025-07-03 14:17 ` [PATCH net-next v6 2/2] selftests/bpf: add a new test to check the consumer update case Jason Xing
2025-07-03 15:10 ` Maciej Fijalkowski
2025-07-03 15:45 ` Stanislav Fomichev
2025-07-09 1:40 ` [PATCH net-next v6 0/2] net: xsk: update tx queue consumer 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=20250703141712.33190-1-kerneljasonxing@gmail.com \
--to=kerneljasonxing@gmail.com \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=joe@dama.to \
--cc=john.fastabend@gmail.com \
--cc=jonathan.lemon@gmail.com \
--cc=kernelxing@tencent.com \
--cc=kuba@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=willemdebruijn.kernel@gmail.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.