DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shijith Thotton <sthotton@marvell.com>
To: <s.v.naga.harish.k@intel.com>, <jerinj@marvell.com>
Cc: Shijith Thotton <sthotton@marvell.com>, <dev@dpdk.org>,
	<pbhagavatula@marvell.com>
Subject: [PATCH v2 0/3] Rx adapter API to add Rx queues in burst
Date: Tue, 18 Feb 2025 14:45:39 +0530	[thread overview]
Message-ID: <20250218091543.282270-1-sthotton@marvell.com> (raw)
In-Reply-To: <20250207140910.721374-1-sthotton@marvell.com>

This patch series introduces the rte_event_eth_rx_adapter_queues_add()
API, allowing multiple Rx queues to be added to an Rx adapter in a
single burst. This enhancement benefits applications that require bulk
addition of Rx queues.  

To support this API, a new internal eventdev PMD operation for adding Rx
queues has been implemented. The second patch in the series enables this
operation for the CNXK PMD. 

Additionally, a unit test has been added to validate the API's
functionality.

RFC:
 - https://patches.dpdk.org/project/dpdk/patch/20241219073405.1724200-1-sthotton@marvell.com/

v1:
 - Updated documentation to explain the new API.

Shijith Thotton (3):
  eventdev/eth_rx: add API to burst add queues to Rx adapter
  event/cnxk: enable PMD op to burst add queues to Rx adapter
  test/event: unit test to burst add Rx queues to adapter

 app/test/test_event_eth_rx_adapter.c          |  86 ++++++++
 .../eventdev/event_ethernet_rx_adapter.rst    |  60 +++++-
 drivers/event/cnxk/cn10k_eventdev.c           |  82 ++++++--
 drivers/event/cnxk/cn20k_eventdev.c           | 195 +++++++++++++-----
 drivers/event/cnxk/cn9k_eventdev.c            |  38 +++-
 drivers/event/cnxk/cnxk_eventdev.h            |   8 +-
 drivers/event/cnxk/cnxk_eventdev_adptr.c      | 102 +++++----
 lib/eventdev/eventdev_pmd.h                   |  34 +++
 lib/eventdev/eventdev_trace.h                 |  14 ++
 lib/eventdev/eventdev_trace_points.c          |   3 +
 lib/eventdev/rte_event_eth_rx_adapter.c       | 155 ++++++++++++++
 lib/eventdev/rte_event_eth_rx_adapter.h       |  33 +++
 lib/eventdev/version.map                      |   3 +
 13 files changed, 686 insertions(+), 127 deletions(-)

-- 
2.25.1


  parent reply	other threads:[~2025-02-18  9:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-07 14:09 [PATCH " Shijith Thotton
2025-02-07 14:09 ` [PATCH 1/3] eventdev/eth_rx: add API to burst add queues to Rx adapter Shijith Thotton
2025-02-17 16:15   ` Naga Harish K, S V
2025-02-18  4:52     ` Shijith Thotton
2025-02-07 14:09 ` [PATCH 2/3] event/cnxk: enable PMD op " Shijith Thotton
2025-02-07 14:09 ` [PATCH 3/3] test/event: unit test to burst add Rx queues to adapter Shijith Thotton
2025-02-17 16:17 ` [PATCH 0/3] Rx adapter API to add Rx queues in burst Naga Harish K, S V
2025-02-18  4:44   ` Shijith Thotton
2025-02-18  9:15 ` Shijith Thotton [this message]
2025-02-18  9:15 ` [PATCH v2 1/3] eventdev/eth_rx: add API to burst add queues to Rx adapter Shijith Thotton
2025-02-20  4:59   ` Naga Harish K, S V
2025-02-20  6:28     ` Shijith Thotton
2025-02-18  9:15 ` [PATCH v2 2/3] event/cnxk: enable PMD op " Shijith Thotton
2025-02-18  9:15 ` [PATCH v2 3/3] test/event: unit test to burst add Rx queues to adapter Shijith Thotton

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=20250218091543.282270-1-sthotton@marvell.com \
    --to=sthotton@marvell.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=pbhagavatula@marvell.com \
    --cc=s.v.naga.harish.k@intel.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).