From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?iso-8859-1?Q?N=E9lio?= Laranjeiro Subject: Re: [PATCH v4 0/2] app/testpmd implement VXLAN/NVGRE Encap/Decap Date: Fri, 22 Jun 2018 10:31:58 +0200 Message-ID: <20180622083158.2teseqebd5qnmvoj@laranjeiro-vm.dev.6wind.com> References: <1abcbded-425c-c137-af00-7d8f17805cb9@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: dev@dpdk.org, Adrien Mazarguil , Wenzhuo Lu , Jingjing Wu , Bernard Iremonger , Ori Kam , Stephen Hemminger To: Mohammad Abdul Awal Return-path: Received: from mail-wr0-f193.google.com (mail-wr0-f193.google.com [209.85.128.193]) by dpdk.org (Postfix) with ESMTP id C3BC71BB20 for ; Fri, 22 Jun 2018 10:31:43 +0200 (CEST) Received: by mail-wr0-f193.google.com with SMTP id e18-v6so5817993wrs.5 for ; Fri, 22 Jun 2018 01:31:43 -0700 (PDT) Content-Disposition: inline In-Reply-To: <1abcbded-425c-c137-af00-7d8f17805cb9@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Fri, Jun 22, 2018 at 08:42:10AM +0100, Mohammad Abdul Awal wrote: > Hi Nelio, > > > On 21/06/2018 08:13, Nelio Laranjeiro wrote: > > This series adds an easy and maintainable configuration version support for > > those two actions for 18.08 by using global variables in testpmd to store the > > necessary information for the tunnel encapsulation. Those variables are used > > in conjunction of RTE_FLOW_ACTION_{VXLAN,NVGRE}_ENCAP action to create easily > > the action for flows. > > > > A common way to use it: > > > > set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 11:11:11:11:11:11 22:22:22:22:22:22 > > flow create 0 ingress pattern end actions vxlan_encap / queue index 0 / end > > This way we can define only one tunnel for all the flows. This is not a > convenient for testing a scenario (e.g. mutiport or switch) with multiple > tunnels. Isn't it? Hi Awal. The "set vxlan" command will just configure the outer VXLAN tunnel to be used, when the "flow" command is invoked, it will use the VXLAN tunnel information and create a valid VXLAN_ENCAP action. For instance: testpmd> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 11:11:11:11:11:11 22:22:22:22:22:22 testpmd> flow create 0 ingress pattern end actions vxlan_encap / queue index 0 / end testpmd> set vxlan ipv6 4 34 42 ::1 ::2222 80:12:13:14:15:16 22:22:22:22:22:22 testpmd> flow create 0 ingress pattern end actions vxlan_encap / queue index 0 / end will create two VLXAN_ENCAP flow one with IPv4 tunnel the second one with an IPv6. Whereas: testpmd> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 11:11:11:11:11:11 22:22:22:22:22:22 testpmd> flow create 0 ingress pattern eth / ipv4 src is 10.2.3.4 / end actions vxlan_encap / queue index 0 / end testpmd> flow create 0 ingress pattern eth / ipv4 src is 20.2.3.4 / end actions vxlan_encap / queue index 0 / end will encapsulate the packets having as IPv4 source IP 10.2.3.4 and 20.2.3.4 with the same VXLAN tunnel headers. Regards, -- Nélio Laranjeiro 6WIND