From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Chaoyong He <chaoyong.he@corigine.com>, dev@dpdk.org
Cc: oss-drivers@corigine.com, niklas.soderlund@corigine.com
Subject: Re: [PATCH] doc: add supported APIs section to nfp guide
Date: Thu, 19 Jan 2023 09:18:44 +0000 [thread overview]
Message-ID: <ea9e6c0a-5c54-5509-707c-118d614f43e0@amd.com> (raw)
In-Reply-To: <20221201013848.19843-1-chaoyong.he@corigine.com>
On 12/1/2022 1:38 AM, Chaoyong He wrote:
> Add a new section 'Supported APIs', inculding the supported
> APIs/items/actions of rte_flow.
>
Isn't this information already exists in
'doc/guides/nics/features/nfp.ini'? Why to duplicate here?
> Signed-off-by: Chaoyong He <chaoyong.he@corigine.com>
> Reviewed-by: Niklas Söderlund <niklas.soderlund@corigine.com>
> ---
> doc/guides/nics/nfp.rst | 71 +++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 71 insertions(+)
>
> diff --git a/doc/guides/nics/nfp.rst b/doc/guides/nics/nfp.rst
> index b74067c875..615f7dab9f 100644
> --- a/doc/guides/nics/nfp.rst
> +++ b/doc/guides/nics/nfp.rst
> @@ -213,3 +213,74 @@ PF vNIC.
> The ctrl vNIC service handling various control message, like the creation and
> configuration of representor port, the pattern and action of flow rules, the
> statistics of flow rules, and so on.
> +
> +Supported APIs
> +--------------
> +
> +rte_flow APIs
> +~~~~~~~~~~~~~
> +
> +Listed below are the rte_flow functions supported:
> +* ``rte_flow_ops_get``
> +* ``rte_flow_validate``
> +* ``rte_flow_create``
> +* ``rte_flow_destroy``
> +* ``rte_flow_flush``
> +* ``nfp_flow_query``
> +* ``rte_flow_tunnel_action_decap_release``
> +* ``rte_flow_tunnel_decap_set``
> +* ``rte_flow_tunnel_item_release``
> +* ``rte_flow_tunnel_match``
> +
> +rte_flow Items
> +~~~~~~~~~~~~~~
> +
> +Refer to "Table 1.2 rte_flow items availability in networking drivers" in
> +`Overview of Networking Drivers <https://doc.dpdk.org/guides/nics/overview.html>`.
> +
> +Listed below are the rte_flow items supported:
> +
> +* ``eth``
> +* ``geneve``
> +* ``gre``
> +* ``gre_key``
> +* ``ipv4``
> +* ``ipv6``
> +* ``port_id``
> +* ``sctp``
> +* ``tcp``
> +* ``udp``
> +* ``vlan``
> +* ``vxlan``
> +
> +rte_flow Actions
> +~~~~~~~~~~~~~~~~
> +
> +Refer to "Table 1.3 rte_flow actions availability in networking drivers" in
> +`Overview of Networking Drivers <https://doc.dpdk.org/guides/nics/overview.html>`.
> +
> +Listed below are the rte_flow actions supported:
> +
> +* ``count``
> +* ``drop``
> +* ``jump``
> +* ``of_pop_vlan``
> +* ``of_push_vlan``
> +* ``of_set_vlan_pcp``
> +* ``of_set_vlan_vid``
> +* ``raw_decap``
> +* ``raw_encap``
> +* ``port_id``
> +* ``set_ipv4_dscp``
> +* ``set_ipv4_dst``
> +* ``set_ipv4_src``
> +* ``set_ipv6_dscp``
> +* ``set_ipv6_dst``
> +* ``set_ipv6_src``
> +* ``set_mac_dst``
> +* ``set_mac_src``
> +* ``set_tp_dst``
> +* ``set_tp_src``
> +* ``set_ttl``
> +* ``vxlan_decap``
> +* ``vxlan_encap``
next prev parent reply other threads:[~2023-01-19 9:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 1:38 Chaoyong He
2023-01-19 9:18 ` Ferruh Yigit [this message]
2023-01-24 2:44 ` Chaoyong He
2023-01-24 9:13 ` Ferruh Yigit
2023-02-08 17:05 ` Niklas Soderlund
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=ea9e6c0a-5c54-5509-707c-118d614f43e0@amd.com \
--to=ferruh.yigit@amd.com \
--cc=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=niklas.soderlund@corigine.com \
--cc=oss-drivers@corigine.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).