From: Ori Kam <orika@nvidia.com>
To: andreyv@nvidia.com, mdr@ashroe.eu
Cc: alexr@nvidia.com, andrey.vesnovaty@gmail.com,
arybchenko@solarflare.com, dev@dpdk.org, elibr@nvidia.com,
ferruh.yigit@intel.com, orika@nvidia.com, ozsh@nvidia.com,
roniba@nvidia.com, thomas@nvidia.net, viacheslavo@nvidia.com
Subject: [dpdk-dev] [RFC v3 0/2] introduce stateful flow table
Date: Wed, 4 Nov 2020 15:17:35 +0200 [thread overview]
Message-ID: <20201104131737.10006-1-orika@nvidia.com> (raw)
In-Reply-To: <20200909203008.25563-1-andreyv@nvidia.com>
The RFC introduces Stateful Flow Table (SFT) API and changes needed in
both ethdev an RTE flow to support SFT functionality.
SFT library provides a framework for applications that need to maintain
context across different packets of the connection.
The goals of the SFT library:
- Accelerate flow recognition & its context retrieval for further
lookaside processing.
- Enable context-aware flow handling offload.
Change log:
v3:
- add change log.
- change to RFC
v2:
- Add queue approach in the SFT.
- Move to ethdev.
- update based on ML commentes.
*** BLURB HERE ***
Andrey Vesnovaty (1):
ethdev: add item/action for SFT
Ori Kam (1):
ethdev: introduce sft lib
lib/librte_ethdev/meson.build | 3 +
lib/librte_ethdev/rte_ethdev_version.map | 19 +
lib/librte_ethdev/rte_flow.h | 75 ++
lib/librte_ethdev/rte_sft.c | 9 +
lib/librte_ethdev/rte_sft.h | 877 +++++++++++++++++++++++
lib/librte_ethdev/rte_sft_driver.h | 201 ++++++
6 files changed, 1184 insertions(+)
create mode 100644 lib/librte_ethdev/rte_sft.c
create mode 100644 lib/librte_ethdev/rte_sft.h
create mode 100644 lib/librte_ethdev/rte_sft_driver.h
--
2.25.1
next prev parent reply other threads:[~2020-11-04 13:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 20:30 [dpdk-dev] [RFC 0/3] introduce Stateful Flow Table Andrey Vesnovaty
2020-09-09 20:30 ` [dpdk-dev] [RFC 1/3] ethdev: add item/action for SFT Andrey Vesnovaty
2020-09-16 15:46 ` Ori Kam
2020-09-18 7:04 ` Andrew Rybchenko
2020-09-09 20:30 ` [dpdk-dev] [RFC 2/3] ethdev: support SFT APIs Andrey Vesnovaty
2020-09-09 20:30 ` [dpdk-dev] [RFC 3/3] sft: introduce API Andrey Vesnovaty
2020-09-16 18:33 ` Ori Kam
2020-09-18 7:43 ` Andrew Rybchenko
2020-11-02 10:49 ` Andrey Vesnovaty
2020-09-18 13:34 ` Kinsella, Ray
2020-09-15 11:59 ` [dpdk-dev] [RFC 0/3] introduce Stateful Flow Table Andrey Vesnovaty
2020-11-04 12:59 ` [dpdk-dev] [PATCH v2 0/2] introduce stateful flow table Ori Kam
2020-11-04 12:59 ` [dpdk-dev] [PATCH v2 1/2] ethdev: add item/action for SFT Ori Kam
2020-11-04 12:59 ` [dpdk-dev] [PATCH v2 2/2] ethdev: introduce sft lib Ori Kam
2020-11-04 13:17 ` Ori Kam [this message]
2020-11-04 13:17 ` [dpdk-dev] [RFC v3 1/2] ethdev: add item/action for SFT Ori Kam
2020-11-04 13:17 ` [dpdk-dev] [RFC v3 2/2] ethdev: introduce sft lib Ori Kam
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=20201104131737.10006-1-orika@nvidia.com \
--to=orika@nvidia.com \
--cc=alexr@nvidia.com \
--cc=andrey.vesnovaty@gmail.com \
--cc=andreyv@nvidia.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=elibr@nvidia.com \
--cc=ferruh.yigit@intel.com \
--cc=mdr@ashroe.eu \
--cc=ozsh@nvidia.com \
--cc=roniba@nvidia.com \
--cc=thomas@nvidia.net \
--cc=viacheslavo@nvidia.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).