DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Qi Zhang <qi.z.zhang@intel.com>
Cc: qiming.yang@intel.com, zhichaox.zeng@intel.com, dev@dpdk.org,
	orika@nvidia.com, david.marchand@redhat.com,
	john.mcnamara@intel.com
Subject: Re: [PATCH v5 5/5] doc: add generic flow doc for ice PMD
Date: Fri, 13 Oct 2023 15:17:29 +0200	[thread overview]
Message-ID: <1730069.QkHrqEjB74@thomas> (raw)
In-Reply-To: <20230926112931.4191107-6-qi.z.zhang@intel.com>

26/09/2023 13:29, Qi Zhang:
> +Generic Flow Support
> +~~~~~~~~~~~~~~~~~~~~
> +
> +The ice PMD provides support for the Generic Flow API (RTE_FLOW), enabling
> +users to offload various flow classification tasks to the E810 NIC.
> +The E810 NIC's  packet processing pipeline consists of the following stages:
> +
> +Switch: Supports exact match and limited wildcard matching with a large flow
> +capacity.
> +
> +ACL: Supports wildcard matching with a smaller flow capacity (DCF mode only).
> +
> +FDIR: Supports exact match with a large flow capacity (PF mode only).
> +
> +Hash: Supports RSS (PF mode only)
> +
> +The ice PMD utilizes the ice_flow_engine structure to represent each of these
> +stages and leverages the rte_flow rule's ``group`` attribute for selecting the
> +appropriate engine for Switch, ACL, and FDIR operations:
> +
> +Group 0 maps to Switch
> +Group 1 maps to ACL
> +Group 2 maps to FDIR
> +
> +In the case of RSS, it will only be selected if a ``RTE_FLOW_ACTION_RSS`` action
> +is targeted to no queue group, and the group attribute is ignored.
> +
> +For each engine, a list of supported patterns is maintained in a global array
> +named ``ice_<engine>_supported_pattern``. The Ice PMD will reject any rule with
> +a pattern that is not included in the supported list.

Why not choosing the right engine automatically?

You are defining an API (group number specialization)
which is specific to this driver.
Don't you care about portability of DPDK applications?



  parent reply	other threads:[~2023-10-13 13:17 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-14 20:26 [PATCH 0/2] refactor rte_flow Qi Zhang
2023-08-14 20:26 ` [PATCH 1/2] net/ice: remove pipeline mode Qi Zhang
2023-08-14 20:26 ` [PATCH 2/2] net/ice: map group to pipeline stage Qi Zhang
2023-09-11 16:51 ` [PATCH v2 0/2] refactor rte_flow Qi Zhang
2023-09-11 16:51   ` [PATCH v2 1/2] net/ice: remove pipeline mode Qi Zhang
2023-09-11 16:51   ` [PATCH v2 2/2] net/ice: map group to pipeline stage Qi Zhang
2023-09-12 10:00 ` [PATCH v3 0/5] refactor rte_flow Qi Zhang
2023-09-12 10:00   ` [PATCH v3 1/5] net/ice: remove pipeline mode Qi Zhang
2023-09-12 10:00   ` [PATCH v3 2/5] net/ice: refine flow engine disabling Qi Zhang
2023-09-12 10:00   ` [PATCH v3 3/5] net/ice: map group to pipeline stage Qi Zhang
2023-09-12 10:00   ` [PATCH v3 4/5] net/ice: refine supported flow pattern name Qi Zhang
2023-09-12 10:00   ` [PATCH v3 5/5] doc: add generic flow doc for ice PMD Qi Zhang
2023-09-25 10:33 ` [PATCH v4 0/5] net/ice: refactor rte_flow Qi Zhang
2023-09-25 10:33   ` [PATCH v4 1/5] net/ice: remove pipeline mode Qi Zhang
2023-09-25 10:33   ` [PATCH v4 2/5] net/ice: refine flow engine disabling Qi Zhang
2023-09-25 10:33   ` [PATCH v4 3/5] net/ice: map group to pipeline stage Qi Zhang
2023-09-25 10:33   ` [PATCH v4 4/5] net/ice: refine supported flow pattern name Qi Zhang
2023-09-25 10:33   ` [PATCH v4 5/5] doc: add generic flow doc for ice PMD Qi Zhang
2023-09-26 11:29 ` [PATCH v5 0/5] net/ice: refactor rte_flow Qi Zhang
2023-09-26 11:29   ` [PATCH v5 1/5] net/ice: remove pipeline mode Qi Zhang
2023-09-26 11:29   ` [PATCH v5 2/5] net/ice: refine flow engine disabling Qi Zhang
2023-09-26 11:29   ` [PATCH v5 3/5] net/ice: map group to pipeline stage Qi Zhang
2023-09-26 11:29   ` [PATCH v5 4/5] net/ice: refine supported flow pattern name Qi Zhang
2023-09-26 11:29   ` [PATCH v5 5/5] doc: add generic flow doc for ice PMD Qi Zhang
2023-09-27  2:42     ` Zeng, ZhichaoX
2023-09-27  3:08       ` Zhang, Qi Z
2023-10-13 13:17     ` Thomas Monjalon [this message]
2023-10-26 10:43       ` Zhang, Qi Z

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=1730069.QkHrqEjB74@thomas \
    --to=thomas@monjalon.net \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=orika@nvidia.com \
    --cc=qi.z.zhang@intel.com \
    --cc=qiming.yang@intel.com \
    --cc=zhichaox.zeng@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).