All of lore.kernel.org
 help / color / mirror / Atom feed
From: Salem Sol <salems@nvidia.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Xiaoyun Li <xiaoyun.li@intel.com>,
	NBU-Contact-Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v3 6/8] doc: update sample actions support in testpmd guide
Date: Thu, 1 Apr 2021 10:48:36 +0000	[thread overview]
Message-ID: <CY4PR1201MB0246772D4A9CCE0F3FCA0DD6AD7B9@CY4PR1201MB0246.namprd12.prod.outlook.com> (raw)
In-Reply-To: <405c8436-5d7d-ddfa-ea5e-21db82cfd06e@intel.com>

Sorry for the confusion, it was meant to show dependency on the whole series  which had two commits [1] and [2].
I will keep an eye for when the patches are merged to post the v4, thanks for the update.

[1]: https://patches.dpdk.org/project/dpdk/patch/1615907899-399082-1-git-send-email-jiaweiw@nvidia.com/
[2]: https://patches.dpdk.org/project/dpdk/patch/1617244796-358287-1-git-send-email-jiaweiw@nvidia.com/

-----Original Message-----
From: Ferruh Yigit <ferruh.yigit@intel.com> 
Sent: Thursday, April 1, 2021 1:43 PM
To: Salem Sol <salems@nvidia.com>; dev@dpdk.org
Cc: Xiaoyun Li <xiaoyun.li@intel.com>; NBU-Contact-Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v3 6/8] doc: update sample actions support in testpmd guide

External email: Use caution opening links or attachments


On 4/1/2021 11:39 AM, Salem Sol wrote:
> Hi Ferruh,
>
> Indeed this patch is dependent on [1], it's also mentioned in the cover letter, I will rebase and post V4 addressing all the comments once [1] is accepted.
>

Cover letter one links to a mlx doc patch, that was the source of the confusion.

And the dependent tespmd patch has a new version, which looks good and I am planning to get it today, in next a few hours, fyi.

> [1] 
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatc
> hes.dpdk.org%2Fproject%2Fdpdk%2Fpatch%2F1617180669-225007-1-git-send-e
> mail-jiaweiw%40nvidia.com%2F&amp;data=04%7C01%7Csalems%40nvidia.com%7C
> 44180cd39e2f49fe373308d8f4faf834%7C43083d15727340c1b7db39efd9ccc17a%7C
> 0%7C0%7C637528706034278930%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDA
> iLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=3obAy
> KaqOoxY7qpJCvyI3om%2FRwMaS2NaTr0S79PfimM%3D&amp;reserved=0
>
> Thanks,
>
> -----Original Message-----
> From: Ferruh Yigit <ferruh.yigit@intel.com>
> Sent: Wednesday, March 31, 2021 3:06 PM
> To: Salem Sol <salems@nvidia.com>; dev@dpdk.org
> Cc: Xiaoyun Li <xiaoyun.li@intel.com>; NBU-Contact-Thomas Monjalon 
> <thomas@monjalon.net>
> Subject: Re: [dpdk-dev] [PATCH v3 6/8] doc: update sample actions 
> support in testpmd guide
>
> External email: Use caution opening links or attachments
>
>
> On 3/17/2021 9:26 AM, Salem Sol wrote:
>> Update documentation for sample action usage in testpmd utilizing 
>> rte_flow_action_vxlan_encap and rte_flow_action_nvgre_encap and show 
>> the command line example.
>>
>
> This patch has dependency to [1], right, can you please confirm it?
>
> [1]:
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatc
> hes.dpdk.org%2Fproject%2Fdpdk%2Fpatch%2F1617180669-225007-1-git-send-e
> mail-jiaweiw%40nvidia.com%2F&amp;data=04%7C01%7Csalems%40nvidia.com%7C
> 44180cd39e2f49fe373308d8f4faf834%7C43083d15727340c1b7db39efd9ccc17a%7C
> 0%7C0%7C637528706034288924%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDA
> iLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=ae25l
> Npwcz33WuxNorJZ9%2B%2BPxviVpV%2BAWNT6OhUER04%3D&amp;reserved=0
>
>> Signed-off-by: Salem Sol <salems@nvidia.com>
>> ---
>>    doc/guides/testpmd_app_ug/testpmd_funcs.rst | 22 +++++++++++++++++++++
>>    1 file changed, 22 insertions(+)
>>
>> diff --git a/doc/guides/testpmd_app_ug/testpmd_funcs.rst
>> b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
>> index 3a31cc6237..392e3a31cf 100644
>> --- a/doc/guides/testpmd_app_ug/testpmd_funcs.rst
>> +++ b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
>> @@ -4901,6 +4901,28 @@ and also mirrored the packets with encapsulation header and sent to port id 0.
>>     testpmd> flow create 0 ingress transfer pattern eth / end actions
>>            sample ratio 1 index 0  / port_id id 2 / end
>>
>> +E-Switch Mirroring rule, the matched ingress packets are sent to 
>> +port id 2, and also mirrored the packets with VXLAN encapsulation header and sent to port id 0.
>> +
>
> Similar comment on 'E-Switch', the mirroring is generic feature but 'E-Switch'
> is vendor specific, can you please update testpmd in a generic way?
>
>> +::
>> +
>> + testpmd> set vxlan ip-version ipv4 vni 4 udp-src 4 udp-dst 4 ip-src
>> + testpmd> 127.0.0.1
>> +        ip-dst 128.0.0.1 eth-src 11:11:11:11:11:11 eth-dst
>> + 22:22:22:22:22:22
>> + testpmd> set sample_actions 0 vxlan_encap / port_id id 0 / end flow 
>> + testpmd> create 0 ingress transfer pattern eth / end actions
>> +        sample ratio 1 index 0  / port_id id 2 / end
>> +
>> +E-Switch Mirroring rule, the matched ingress packets are sent to 
>> +port id 2, and also mirrored the packets with NVGRE encapsulation header and sent to port id 0.
>> +
>> +::
>> +
>> + testpmd> set nvgre ip-version ipv4 tni 4 ip-src 127.0.0.1 ip-dst
>> + testpmd> 128.0.0.1
>> +        eth-src 11:11:11:11:11:11 eth-dst 22:22:22:22:22:22
>> + testpmd> set sample_actions 0 nvgre_encap / port_id id 0 / end flow 
>> + testpmd> create 0 ingress transfer pattern eth / end actions
>> +        sample ratio 1 index 0  / port_id id 2 / end
>> +
>>    BPF Functions
>>    --------------
>>
>>
>


  reply	other threads:[~2021-04-01 10:48 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17  9:26 [dpdk-dev] [PATCH v3 0/8] Add support for VXLAN and NVGRE encap as a sample actions Salem Sol
2021-03-17  9:26 ` [dpdk-dev] [PATCH v3 1/8] app/testpmd: store VXLAN/NVGRE encap data globally Salem Sol
2021-03-17 10:06   ` Slava Ovsiienko
2021-03-31 12:07   ` Ferruh Yigit
2021-04-01  4:13     ` Jiawei(Jonny) Wang
2021-04-06 14:44       ` Ferruh Yigit
2021-04-07  8:19         ` Salem Sol
2021-04-07  8:23           ` Ferruh Yigit
2021-04-07  8:35             ` Salem Sol
2021-04-07 11:30               ` Ferruh Yigit
2021-03-17  9:26 ` [dpdk-dev] [PATCH v3 2/8] net/mlx5: support VXLAN encap action in sample Salem Sol
2021-03-17 10:06   ` Slava Ovsiienko
2021-03-17  9:26 ` [dpdk-dev] [PATCH v3 3/8] net/mlx5: support NVGRE " Salem Sol
2021-03-17 10:07   ` Slava Ovsiienko
2021-03-17  9:26 ` [dpdk-dev] [PATCH v3 4/8] app/testpmd: support VXLAN encap for sample action Salem Sol
2021-03-17 10:07   ` Slava Ovsiienko
2021-03-17  9:26 ` [dpdk-dev] [PATCH v3 5/8] app/testpmd: support NVGRE " Salem Sol
2021-03-17 10:07   ` Slava Ovsiienko
2021-03-17  9:26 ` [dpdk-dev] [PATCH v3 6/8] doc: update sample actions support in testpmd guide Salem Sol
2021-03-17 10:07   ` Slava Ovsiienko
2021-03-31 12:05   ` Ferruh Yigit
2021-04-01 10:39     ` Salem Sol
2021-04-01 10:43       ` Ferruh Yigit
2021-04-01 10:48         ` Salem Sol [this message]
2021-03-17  9:26 ` [dpdk-dev] [PATCH v3 7/8] doc: update sample actions support in mlx5 guide Salem Sol
2021-03-17 10:08   ` Slava Ovsiienko
2021-03-17  9:26 ` [dpdk-dev] [PATCH v3 8/8] doc: update dpdk 21.05 release notes Salem Sol
2021-03-17 10:08   ` Slava Ovsiienko
2021-03-31 12:08   ` Ferruh Yigit

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=CY4PR1201MB0246772D4A9CCE0F3FCA0DD6AD7B9@CY4PR1201MB0246.namprd12.prod.outlook.com \
    --to=salems@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=thomas@monjalon.net \
    --cc=xiaoyun.li@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.