DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Chaoyong He <chaoyong.he@corigine.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	Ajit Khaparde <ajit.khaparde@broadcom.com>
Cc: oss-drivers <oss-drivers@corigine.com>,
	Niklas Soderlund <niklas.soderlund@corigine.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: Re: [PATCH] doc: add supported APIs section to nfp guide
Date: Tue, 24 Jan 2023 09:13:20 +0000	[thread overview]
Message-ID: <3d0f8f39-6200-837c-95b3-53344779dd69@amd.com> (raw)
In-Reply-To: <SJ0PR13MB5545A1C4B89D111B972C91829EC99@SJ0PR13MB5545.namprd13.prod.outlook.com>

On 1/24/2023 2:44 AM, Chaoyong He wrote:
>> 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?
>>
> 
> Oh, one customer say they wants this section like the `bnxt.rst`, so we added this.
> 

You are right, and I think that is a duplication for bnxt too, cc'ed
Ajit for comment.


>>> 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``
> 


  reply	other threads:[~2023-01-24  9:13 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
2023-01-24  2:44   ` Chaoyong He
2023-01-24  9:13     ` Ferruh Yigit [this message]
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=3d0f8f39-6200-837c-95b3-53344779dd69@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=chaoyong.he@corigine.com \
    --cc=dev@dpdk.org \
    --cc=niklas.soderlund@corigine.com \
    --cc=oss-drivers@corigine.com \
    --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).