DPDK patches and discussions
 help / color / mirror / Atom feed
From: Dariusz Sosnowski <dsosnowski@nvidia.com>
To: Alexander Kozyrev <akozyrev@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Ori Kam <orika@nvidia.com>,
	"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
	Matan Azrad <matan@nvidia.com>,
	"ferruh.yigit@amd.com" <ferruh.yigit@amd.com>,
	"stephen@networkplumber.org" <stephen@networkplumber.org>
Subject: RE: [PATCH v2 0/7] ethdev: jump to table support
Date: Wed, 25 Sep 2024 19:28:33 +0000	[thread overview]
Message-ID: <CH3PR12MB84602FAFCDD24D54F4A8689FA4692@CH3PR12MB8460.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20240925180532.3958656-1-akozyrev@nvidia.com>

> -----Original Message-----
> From: Alexander Kozyrev <akozyrev@nvidia.com>
> Sent: Wednesday, September 25, 2024 20:05
> To: dev@dpdk.org
> Cc: Dariusz Sosnowski <dsosnowski@nvidia.com>; Ori Kam
> <orika@nvidia.com>; NBU-Contact-Thomas Monjalon (EXTERNAL)
> <thomas@monjalon.net>; Matan Azrad <matan@nvidia.com>;
> ferruh.yigit@amd.com; stephen@networkplumber.org
> Subject: [PATCH v2 0/7] ethdev: jump to table support
> 
> Introduce new Flow API JUMP_TO_TABLE_INDEX action.
> It allows bypassing a hierarchy of groups and going directly to a specified flow
> table. That gives a user the flexibility to jump between different priorities in a
> group and eliminates the need to do a table lookup in the group hierarchy.
> The JUMP_TO_TABLE_INDEX action forwards a packet to the specified rule
> index inside the index-based flow table.
> 
> The current index-based flow table doesn't do any matching on the packet and
> executes the actions immediately.
> Add a new index-based flow table with pattern matching.
> The JUMP_TO_TABLE_INDEX can redirect a packet to another matching criteria
> at the specified index in this case.
> 
> RFC:
> https://patchwork.dpdk.org/project/dpdk/patch/20240822202753.3856703-
> 1-akozyrev@nvidia.com/
> v2: added trace point to flow insertion by index functions.
> 
> Alexander Kozyrev (7):
>   ethdev: add insertion by index with pattern
>   app/testpmd: add index with pattern insertion type
>   ethdev: add flow rule insertion by index with pattern
>   app/testpmd: add insertion by index with pattern option
>   ethdev: add jump to table index action
>   app/testpmd: add jump to table index action
>   ethdev: add trace points to flow insertion by index
> 
>  app/test-pmd/cmdline_flow.c            | 44 +++++++++++++-
>  app/test-pmd/config.c                  | 22 +++++--
>  app/test-pmd/testpmd.h                 |  2 +-
>  doc/guides/prog_guide/rte_flow.rst     | 20 +++++++
>  doc/guides/rel_notes/release_24_11.rst | 13 +++++
>  lib/ethdev/ethdev_trace.h              | 44 ++++++++++++++
>  lib/ethdev/ethdev_trace_points.c       |  6 ++
>  lib/ethdev/rte_flow.c                  | 72 ++++++++++++++++++++++-
>  lib/ethdev/rte_flow.h                  | 81 ++++++++++++++++++++++++++
>  lib/ethdev/rte_flow_driver.h           | 14 +++++
>  lib/ethdev/version.map                 |  1 +
>  11 files changed, 309 insertions(+), 10 deletions(-)
> 
> --
> 2.18.2

Series-acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>

Best regards,
Dariusz Sosnowski

  parent reply	other threads:[~2024-09-25 19:28 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19  0:48 [PATCH 0/6] " Alexander Kozyrev
2024-09-19  0:48 ` [PATCH 1/6] ethdev: add insertion by index with pattern Alexander Kozyrev
2024-09-25 15:01   ` Dariusz Sosnowski
2024-09-19  0:48 ` [PATCH 2/6] app/testpmd: add index with pattern insertion type Alexander Kozyrev
2024-09-25 15:01   ` Dariusz Sosnowski
2024-09-19  0:48 ` [PATCH 3/6] ethdev: add flow rule insertion by index with pattern Alexander Kozyrev
2024-09-25 15:00   ` Dariusz Sosnowski
2024-09-19  0:48 ` [PATCH 4/6] app/testpmd: add insertion by index with pattern option Alexander Kozyrev
2024-09-25 15:01   ` Dariusz Sosnowski
2024-09-19  0:48 ` [PATCH 5/6] ethdev: add jump to table index action Alexander Kozyrev
2024-09-25 15:01   ` Dariusz Sosnowski
2024-09-19  0:48 ` [PATCH 6/6] app/testpmd: " Alexander Kozyrev
2024-09-25 15:02   ` Dariusz Sosnowski
2024-09-25 18:05 ` [PATCH v2 0/7] ethdev: jump to table support Alexander Kozyrev
2024-09-25 18:05   ` [PATCH v2 1/7] ethdev: add insertion by index with pattern Alexander Kozyrev
2024-09-26  8:23     ` Ori Kam
2024-09-25 18:05   ` [PATCH v2 2/7] app/testpmd: add index with pattern insertion type Alexander Kozyrev
2024-09-26  8:24     ` Ori Kam
2024-09-25 18:05   ` [PATCH v2 3/7] ethdev: add flow rule insertion by index with pattern Alexander Kozyrev
2024-09-26  8:26     ` Ori Kam
2024-09-25 18:05   ` [PATCH v2 4/7] app/testpmd: add insertion by index with pattern option Alexander Kozyrev
2024-09-26  8:48     ` Ori Kam
2024-09-25 18:05   ` [PATCH v2 5/7] ethdev: add jump to table index action Alexander Kozyrev
2024-09-26  8:49     ` Ori Kam
2024-09-25 18:05   ` [PATCH v2 6/7] app/testpmd: " Alexander Kozyrev
2024-09-26  8:49     ` Ori Kam
2024-09-25 18:05   ` [PATCH v2 7/7] ethdev: add trace points to flow insertion by index Alexander Kozyrev
2024-09-26  8:50     ` Ori Kam
2024-09-25 19:28   ` Dariusz Sosnowski [this message]
2024-09-27  1:51   ` [PATCH v2 0/7] ethdev: jump to table support 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=CH3PR12MB84602FAFCDD24D54F4A8689FA4692@CH3PR12MB8460.namprd12.prod.outlook.com \
    --to=dsosnowski@nvidia.com \
    --cc=akozyrev@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    /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).