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
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org,
Jason Xing <kernelxing@tencent.com>
Subject: [PATCH net-next v2 0/3] xsk: introduce atomic for cq in generic path
Date: Tue, 25 Nov 2025 16:54:28 +0800 [thread overview]
Message-ID: <20251125085431.4039-1-kerneljasonxing@gmail.com> (raw)
From: Jason Xing <kernelxing@tencent.com>
In the hot path (that is __xsk_generic_xmit()), playing with spin lock
is time consuming. So this series replaces spin lock with atomic
operations to get better performance.
---
V2
Link: https://lore.kernel.org/all/20251124080858.89593-1-kerneljasonxing@gmail.com/
1. use separate functions rather than branches within shared routines. (Maciej)
2. make each patch as simple as possible for easier review
Jason Xing (3):
xsk: add atomic cached_prod for copy mode
xsk: use atomic operations around cached_prod for copy mode
xsk: remove spin lock protection of cached_prod
include/net/xsk_buff_pool.h | 5 -----
net/xdp/xsk.c | 23 +++++------------------
net/xdp/xsk_buff_pool.c | 1 -
net/xdp/xsk_queue.h | 27 +++++++++++++++++++++++----
4 files changed, 28 insertions(+), 28 deletions(-)
--
2.41.3
next reply other threads:[~2025-11-25 8:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 8:54 Jason Xing [this message]
2025-11-25 8:54 ` [PATCH net-next v2 1/3] xsk: add atomic cached_prod for copy mode Jason Xing
2025-11-25 8:54 ` [PATCH net-next v2 2/3] xsk: use atomic operations around " Jason Xing
2025-11-27 11:35 ` Paolo Abeni
2025-11-27 13:55 ` Jason Xing
2025-11-27 15:32 ` Paolo Abeni
2025-11-27 23:48 ` Jason Xing
2025-11-25 8:54 ` [PATCH net-next v2 3/3] xsk: remove spin lock protection of cached_prod Jason Xing
2025-11-27 11:29 ` Paolo Abeni
2025-11-27 13:18 ` Jason Xing
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=20251125085431.4039-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=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 \
/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.