From mboxrd@z Thu Jan 1 00:00:00 1970 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) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=7vCZukwhpfBJ7L0fPLh6YJouvPaTMNbiVFghP3iEIeE=; b=qM0aB7lDpb+zWwSG8cWV3HCuCBhe/oUGuvBmzSHJXPVnsT2DfY6Y3DDx/36vwhbUvx xM3B7oxKMiXeZ/LDJ40ND1dzjvZJacliVs6Lbah+QSWIhGP0ClVRTeJh7mQEYziiXw+/ wO0WJ3eE4DDmPlcz+EbBx3eyVhf6zYwEvQbBV3X0L5CY2ztdPlnqq5u+SklS89u9sPCd u20sBL8Jeo56xnuUUE5LzD6sfvRoSMHyfJ6DiR81tsFPV8+6dBlSF+WGkwU1dDsgZ4u6 /ClCrYD3QOkc/Ya+1kthxHCfDdVkAiPZ31vM4EX9u3/PL1zvPIB07eMoYQ3ygQs8rLQf wQ3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=7vCZukwhpfBJ7L0fPLh6YJouvPaTMNbiVFghP3iEIeE=; b=ZNrxRpdGUkJlZFfcAER9GHaracMAPIeFptzWWZlU0VpZbqlEIJmBD11FwdDnmjpbGm sGyHaOmbfqSZm2siSvjBqCmI1GT8E1iTHBTCxiXI21lSNvTP1fs6tWC6+p8aa3rW4BHl FwKBi8FqiUmd7htP2IANlYjZZuYvwMxBHZU9cnctD7IP0WHKeYGMfAtGeO9BoRD42Zs/ +cJdQHrH5uYs1yMneWwoYVlVWWTkP80oGrm5cx8eaYhIie5IrpBCyEEc6eHGvglVwBJ+ Rr7wmWdeFck9XGuiCVzVuAw/Wl4aPbI2Tqdx/c/U5gVEp6YgOPlpcO4621ZUkhJZPNI/ DuLg== X-Gm-Message-State: APt69E3ESXcwYBdaSsb85HyP4P759dzwQNcYrQleLchrosdlFl0EsONH ZzrzRSWPXQgOzgqipE/I4N4u X-Google-Smtp-Source: AAOMgpfD6D4WjSYCorqjq1D3De53wDTM3DitBM15+RG2WYERfZToZk2qi5hsLGMZ4wNHKHt9q51o6g== X-Received: by 2002:adf:fac6:: with SMTP id a6-v6mr710975wrs.74.1529656303444; Fri, 22 Jun 2018 01:31:43 -0700 (PDT) Received: from laranjeiro-vm.dev.6wind.com (host.78.145.23.62.rev.coltfrance.com. [62.23.145.78]) by smtp.gmail.com with ESMTPSA id s13-v6sm7301580wrq.48.2018.06.22.01.31.42 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 22 Jun 2018 01:31:42 -0700 (PDT) Date: Fri, 22 Jun 2018 10:31:58 +0200 From: =?iso-8859-1?Q?N=E9lio?= Laranjeiro To: Mohammad Abdul Awal Cc: dev@dpdk.org, Adrien Mazarguil , Wenzhuo Lu , Jingjing Wu , Bernard Iremonger , Ori Kam , Stephen Hemminger 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-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1abcbded-425c-c137-af00-7d8f17805cb9@intel.com> User-Agent: NeoMutt/20170113 (1.7.2) Subject: Re: [dpdk-dev] [PATCH v4 0/2] app/testpmd implement VXLAN/NVGRE Encap/Decap X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2018 08:31:43 -0000 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