From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f196.google.com (mail-wr0-f196.google.com [209.85.128.196]) by dpdk.org (Postfix) with ESMTP id 269D71B8CB for ; Tue, 26 Jun 2018 17:14:38 +0200 (CEST) Received: by mail-wr0-f196.google.com with SMTP id c13-v6so7700060wrq.2 for ; Tue, 26 Jun 2018 08:14:38 -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=+4VgX+ERtDHR4dwOKONJC9HwxTyBtub165viRVoUhS0=; b=IbhD5vFpuuMPbsfblCWg5800yzRNAbOtU+lFbGLq2TgIGwxbv6esqJweYSrvCwywSA V8TtDx9XZLTOZ2usy8+VJOrWlCvBjK5uyXkjJizOjY8AteR6CEp215+OCj6Mh1pOBk/4 F+ORGNhlB2GrHsI/j6WVgsBsaJ0Y79/BpDk1jupGtGOJcu8a2fJgwkGWuZaYDF5Bw3md TPwD4oSy4JVvXJNsTBLTf1ESC5EKgr5SSGY1vgzkCUn2h/vjdvfVj8VA3iO0/PlK51yi Naa9q4MDGI2A67v211jiDAAUwBlG6O2JZCwFmDibXtRAbMRwFqWFp1t8Ol4d+449/oJK m5yg== 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=+4VgX+ERtDHR4dwOKONJC9HwxTyBtub165viRVoUhS0=; b=DK5xZMflC48KwiMbjJJ/nd0LE/Sr0RYHDpDkfVQ/OWT8bskMf1hAMhhWjNpLNhg1PV tNMQVEMg54xQ6yDrJLB5C3Hg+AanjXLvQ6peKYcLtxFiQcyT+QIjSUruxQCsfPYkbjFv ERHCHGxCHTmH+cFDcgafaYy7diu6/4uGCY9F5OalnO7EGzYbD5SH6/W7XWsl1eKxZKP4 IG5e2gOKV2oyTXtr4K0Ekwmr5NmxIWYZBG7wLkiAoDE1ENZXC7ps1z3WYHGb+3Zrf3H1 AWvUDkl7EGTXbrTF76edqR2N7jLzxTr2ckXdt1LJW6qQqr3egaKl9/eXjhxe78Z91K0a /GOg== X-Gm-Message-State: APt69E3tqlsOC7MuCw+JGGwXNqLQftqi5DLqcawLIRg+pEUFYHAlkG1W gqSCkWs/wbWAzbY4Ou9GNqlJ X-Google-Smtp-Source: AAOMgpcGOEN+oOBpTJqhv5a50aYJpYcTKYlKJknW/pTwM92mfZLB/lbHtKejioAPDGv6ZVbGQ4kStw== X-Received: by 2002:a5d:41c5:: with SMTP id e5-v6mr1845410wrq.25.1530026077821; Tue, 26 Jun 2018 08:14:37 -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 b15-v6sm2504121wri.14.2018.06.26.08.14.36 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 26 Jun 2018 08:14:36 -0700 (PDT) Date: Tue, 26 Jun 2018 17:15:02 +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: <20180626151502.pt2x2v4orl33pom2@laranjeiro-vm.dev.6wind.com> References: <1abcbded-425c-c137-af00-7d8f17805cb9@intel.com> <20180622083158.2teseqebd5qnmvoj@laranjeiro-vm.dev.6wind.com> <833f6445-bcc2-ae2e-1dc7-45f33e0d8e8e@intel.com> <20180622090859.ewqrwyyvtjj463or@laranjeiro-vm.dev.6wind.com> <92ca13ed-6025-9186-0cb0-b787af470dec@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <92ca13ed-6025-9186-0cb0-b787af470dec@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: Tue, 26 Jun 2018 15:14:38 -0000 On Fri, Jun 22, 2018 at 11:19:14AM +0100, Mohammad Abdul Awal wrote: > On 22/06/2018 10:08, Nélio Laranjeiro wrote: > > On Fri, Jun 22, 2018 at 09:51:15AM +0100, Mohammad Abdul Awal wrote: > > > > > > On 22/06/2018 09:31, Nélio Laranjeiro wrote: > > > > 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. > > > I understand that the same IPv4 tunnel will be used for both flows in your > > > example above.  I have the following questions. > > > > > > 1) How can we create two or more IPv4 (or IPv6) tunnel? > > > 1) How can we make the flows to use different IPv4 tunnels? > > > As an example, > > > > > > 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> set vxlan ipv4 4 4 4 127.0.0.1 128.0.0.1 33:33:33:33:33:33 44:44:44:44:44:44 > > > testpmd> flow create 0 ingress pattern end actions vxlan_encap / queue index 0 / end > > > testpmd> flow create 0 ingress pattern end actions vxlan_encap / queue index 0 / end > > > > > Doing this, the flows will use the same tunnel, you must do: > > > > 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 ipv4 4 4 4 127.0.0.1 128.0.0.1 33:33:33:33:33:33 44:44:44:44:44:44 > > testpmd> flow create 0 ingress pattern end actions vxlan_encap / queue index 0 / end > > > > to have what you want. > OK, thanks for the clarification. So, since there will be only one global > instance of the tunnel,  for any subsequent "set vxlan" operations, the > tunnel created from the last last operation will be used. May be it should > be cleared in the description/documentation? Will add it in the v5. > > > Is it possible? > > Regards, > > > Thanks, -- Nélio Laranjeiro 6WIND