From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net-next v2 0/3] net: use READ_ONCE/WRITE_ONCE for ring index accesses
Date: Tue, 11 Apr 2023 18:50:35 -0700 [thread overview]
Message-ID: <20230412015038.674023-1-kuba@kernel.org> (raw)
Small follow up to the lockless ring stop/start macros.
Update the doc and the drivers suggested by Eric:
https://lore.kernel.org/all/CANn89iJrBGSybMX1FqrhCEMWT3Nnz2=2+aStsbbwpWzKHjk51g@mail.gmail.com/
v2:
- convert xdp paths in bnxt as well
v1: https://lore.kernel.org/all/20230411013323.513688-1-kuba@kernel.org/
Jakub Kicinski (3):
net: docs: update the sample code in driver.rst
bnxt: use READ_ONCE/WRITE_ONCE for ring indexes
mlx4: use READ_ONCE/WRITE_ONCE for ring indexes
Documentation/networking/driver.rst | 61 ++++++++-----------
drivers/net/ethernet/broadcom/bnxt/bnxt.c | 6 +-
drivers/net/ethernet/broadcom/bnxt/bnxt.h | 9 ++-
drivers/net/ethernet/broadcom/bnxt/bnxt_xdp.c | 6 +-
drivers/net/ethernet/mellanox/mlx4/en_tx.c | 8 ++-
5 files changed, 42 insertions(+), 48 deletions(-)
--
2.39.2
next reply other threads:[~2023-04-12 1:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 1:50 Jakub Kicinski [this message]
2023-04-12 1:50 ` [PATCH net-next v2 1/3] net: docs: update the sample code in driver.rst Jakub Kicinski
2023-04-12 1:50 ` [PATCH net-next v2 2/3] bnxt: use READ_ONCE/WRITE_ONCE for ring indexes Jakub Kicinski
2023-04-12 1:59 ` Michael Chan
2023-04-12 8:15 ` David Laight
2023-04-13 11:38 ` Paolo Abeni
2023-04-13 14:20 ` David Laight
2023-04-12 1:50 ` [PATCH net-next v2 3/3] mlx4: " Jakub Kicinski
2023-04-12 6:07 ` Tariq Toukan
2023-04-13 11:50 ` [PATCH net-next v2 0/3] net: use READ_ONCE/WRITE_ONCE for ring index accesses 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=20230412015038.674023-1-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.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).