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] [PATCH v2 1/2] ethdev: add item/action for SFT
Date: Wed, 4 Nov 2020 14:59:17 +0200 [thread overview]
Message-ID: <20201104125918.9751-2-orika@nvidia.com> (raw)
In-Reply-To: <20201104125918.9751-1-orika@nvidia.com>
From: Andrey Vesnovaty <andreyv@nvidia.com>
Attach SFT flow context to packet with SFT action.
Match on SFT flow context (attached to packet),
with SFT item.
Signed-off-by: Andrey Vesnovaty <andreyv@nvidia.com>
---
lib/librte_ethdev/rte_flow.h | 75 ++++++++++++++++++++++++++++++++++++
1 file changed, 75 insertions(+)
diff --git a/lib/librte_ethdev/rte_flow.h b/lib/librte_ethdev/rte_flow.h
index da8bfa5489..7ca47cc87c 100644
--- a/lib/librte_ethdev/rte_flow.h
+++ b/lib/librte_ethdev/rte_flow.h
@@ -537,6 +537,14 @@ enum rte_flow_item_type {
*/
RTE_FLOW_ITEM_TYPE_ECPRI,
+ /**
+ * [META]
+ *
+ * Matches SFT context.
+ *
+ * See struct rte_flow_item_sft.
+ */
+ RTE_FLOW_ITEM_TYPE_SFT,
};
/**
@@ -1579,6 +1587,48 @@ static const struct rte_flow_item_ecpri rte_flow_item_ecpri_mask = {
};
#endif
+/**
+ * @warning
+ * @b EXPERIMENTAL: this structure may change without prior notice
+ *
+ * RTE_FLOW_ITEM_TYPE_SFT
+ *
+ * Matches context of flow that wasw created by SFT.
+ *
+ * The structure describes SFT flow context.
+ * All the fields of the structure, except @p fid, should be considered as
+ * user defined.
+ * The @p fid assigned by RTE SFT & used as unique flow identifier.
+ * SFT context attached to packet by action ``SFT`` (see RTE_FLOW_ACTION_SFT),
+ * which sends the packet to the SFT module.
+ *
+ * SFT default context defined as context attached to packet when there is no
+ * entry for the flow in SFT. The @p state has application reserved value
+ * meaning that SFT context for the packet undefined since entry wasn't found
+ * in SFT. If state 'undefined' then @p zone should be valid othervice @p fid
+ * should be valid.
+ *
+ * Context considered virtual since the method of storing this info on packet
+ * is PMD/implementation specific & may involve mapping methods if there is
+ * 'not enough bits' to store entire contents of struct rte_flow_item_sft.
+ *
+ * Maximal value/size of each field depends on HW capabilities and considered
+ * as implementation specific.
+ */
+RTE_STD_C11
+struct rte_flow_item_sft {
+ union {
+ uint32_t fid; /**< SFT flow identifier. */
+ uint32_t zone; /**< Zone assigned to flow. */
+ };
+ uint32_t fid_valid:1; /**< The fid member is valid. */
+ uint32_t zone_valid:1; /**< The zone member is valid. */
+ uint32_t reserved:30; /**< Reserved. */
+ uint8_t state; /**< User defined flow state. */
+ uint8_t user_data_size; /**< user_data buffer size. */
+ uint8_t *user_data; /**< Arbitrary user data. */
+};
+
/**
* Matching pattern item definition.
*
@@ -2132,6 +2182,15 @@ enum rte_flow_action_type {
* see enum RTE_ETH_EVENT_FLOW_AGED
*/
RTE_FLOW_ACTION_TYPE_AGE,
+
+ /**
+ * RTE_FLOW_ACTION_TYPE_SFT
+ *
+ * Direct the packet to SFT module.
+ *
+ * See struct rte_flow_action_sft.
+ */
+ RTE_FLOW_ACTION_TYPE_SFT,
};
/**
@@ -2721,6 +2780,22 @@ rte_flow_dynf_metadata_set(struct rte_mbuf *m, uint32_t v)
*RTE_FLOW_DYNF_METADATA(m) = v;
}
+/**
+ * @warning
+ * @b EXPERIMENTAL: this structure may change without prior notice
+ *
+ * RTE_FLOW_ACTION_TYPE_SFT
+ *
+ * Performs lookup by *zone* and 5-tuple in SFT.
+ * If entry is found the related SFT context will be attached otherwise,
+ * default SFT context will be attached.
+ *
+ * This action may result in termination of actions that following this action.
+ */
+struct rte_flow_action_sft {
+ uint32_t zone; /**< Zone for lookup in SFT */
+};
+
/*
* Definition of a single action.
*
--
2.25.1
next prev parent reply other threads:[~2020-11-04 12:59 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 ` Ori Kam [this message]
2020-11-04 12:59 ` [dpdk-dev] [PATCH v2 2/2] ethdev: introduce sft lib Ori Kam
2020-11-04 13:17 ` [dpdk-dev] [RFC v3 0/2] introduce stateful flow table Ori Kam
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=20201104125918.9751-2-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).