DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH 0/5] use RTE_DIM where possible
Date: Tue, 16 Apr 2024 08:19:26 -0700	[thread overview]
Message-ID: <20240416152124.69590-1-stephen@networkplumber.org> (raw)

There is macro for computing the number of elements in an array RTE_DIM.
But it is not used in many places where it could be.
Based on similar coccinelle script in Linux.

Stephen Hemminger (5):
  cocci: add script to use RTE_DIM
  app: use RTE_DIM
  lib: use RTE_DIM
  examples _use RTE_DIM
  drivers/net: use RTE_DIM

 app/test-flow-perf/main.c              |  4 +--
 app/test/test_ethdev_link.c            |  3 +-
 app/test/test_security_inline_macsec.c | 47 +++++++++++++-------------
 devtools/cocci/rte-dim.cocci           | 23 +++++++++++++
 drivers/net/ark/ark_pktchkr.c          |  2 +-
 drivers/net/ark/ark_pktgen.c           |  2 +-
 drivers/net/bnxt/bnxt_hwrm.c           | 12 +++----
 drivers/net/e1000/em_rxtx.c            |  3 +-
 drivers/net/iavf/iavf_ipsec_crypto.c   |  3 +-
 drivers/net/igc/igc_ethdev.c           |  3 +-
 drivers/net/ipn3ke/ipn3ke_tm.c         |  3 +-
 drivers/net/ngbe/ngbe_ethdev.c         |  6 ++--
 drivers/net/octeontx/octeontx_stats.h  |  3 +-
 drivers/net/txgbe/txgbe_ethdev.c       |  9 ++---
 drivers/net/txgbe/txgbe_ethdev_vf.c    |  3 +-
 examples/l3fwd/main.c                  |  3 +-
 examples/qos_sched/init.c              |  3 +-
 lib/cmdline/cmdline_vt100.c            |  4 ++-
 lib/latencystats/rte_latencystats.c    |  3 +-
 19 files changed, 73 insertions(+), 66 deletions(-)
 create mode 100644 devtools/cocci/rte-dim.cocci

-- 
2.43.0


             reply	other threads:[~2024-04-16 15:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16 15:19 Stephen Hemminger [this message]
2024-04-16 15:19 ` [PATCH 1/5] cocci: add script to use RTE_DIM Stephen Hemminger
2024-04-16 15:19 ` [PATCH 2/5] app: " Stephen Hemminger
2024-04-16 15:30   ` Tyler Retzlaff
2024-04-17  6:13   ` [EXTERNAL] " Akhil Goyal
2024-04-16 15:19 ` [PATCH 3/5] lib: " Stephen Hemminger
2024-04-16 15:32   ` Tyler Retzlaff
2024-04-16 15:19 ` [PATCH 4/5] examples _use RTE_DIM Stephen Hemminger
2024-04-16 15:32   ` Tyler Retzlaff
2024-04-16 15:19 ` [PATCH 5/5] drivers/net: use RTE_DIM Stephen Hemminger
2024-04-16 16:29   ` Ferruh Yigit
2024-04-16 17:32     ` Stephen Hemminger
2024-04-17  8:00       ` Ferruh Yigit

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=20240416152124.69590-1-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    /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).