public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Vimlesh Kumar <vimleshk@marvell.com>
To: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <sedara@marvell.com>, <srasheed@marvell.com>, <hgani@marvell.com>,
	"Vimlesh Kumar" <vimleshk@marvell.com>
Subject: [PATCH net v2 0/4] avoid compiler and IQ/OQ reordering
Date: Fri, 27 Feb 2026 09:13:56 +0000	[thread overview]
Message-ID: <20260227091402.1773833-1-vimleshk@marvell.com> (raw)

Utilize READ_ONCE and WRITE_ONCE APIs to prevent compiler
optimization and reordering. Ensure IO queue OUT/IN_CNT
registers are flushed. Relocate IQ/OQ IN/OUT_CNTS updates
to occur before NAPI completion, and replace napi_complete
with napi_complete_done.

Vimlesh Kumar (4):
  octeon_ep: Relocate counter updates before NAPI
  octeon_ep: avoid compiler and IQ/OQ reordering
  octeon_ep_vf: Relocate counter updates before NAPI
  octeon_ep_vf: avoid compiler and IQ/OQ reordering

V1: https://lore.kernel.org/all/20260212121634.360252-1-vimleshk@marvell.com/ 

 .../ethernet/marvell/octeon_ep/octep_main.c   | 40 +++++++++++++------
 .../net/ethernet/marvell/octeon_ep/octep_rx.c | 27 +++++++++----
 .../marvell/octeon_ep_vf/octep_vf_main.c      | 38 +++++++++++++-----
 .../marvell/octeon_ep_vf/octep_vf_rx.c        | 28 +++++++++----
 4 files changed, 95 insertions(+), 38 deletions(-)

-- 
2.47.3


             reply	other threads:[~2026-02-27  9:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27  9:13 Vimlesh Kumar [this message]
2026-02-27  9:13 ` [PATCH net v2 1/4] octeon_ep: Relocate counter updates before NAPI Vimlesh Kumar
2026-02-27  9:13 ` [PATCH net v2 2/4] octeon_ep: avoid compiler and IQ/OQ reordering Vimlesh Kumar
2026-02-27  9:13 ` [PATCH net v2 3/4] octeon_ep_vf: Relocate counter updates before NAPI Vimlesh Kumar
2026-02-27  9:14 ` [PATCH net v2 4/4] octeon_ep_vf: avoid compiler and IQ/OQ reordering Vimlesh Kumar
2026-03-03 10:40 ` [PATCH net v2 0/4] " 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=20260227091402.1773833-1-vimleshk@marvell.com \
    --to=vimleshk@marvell.com \
    --cc=hgani@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sedara@marvell.com \
    --cc=srasheed@marvell.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