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 923491BB20 for ; Fri, 22 Jun 2018 11:08:44 +0200 (CEST) Received: by mail-wr0-f196.google.com with SMTP id k16-v6so5949207wro.0 for ; Fri, 22 Jun 2018 02:08:44 -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=rrePr+VZirfI01USNFoXrDPzgo7TEJC64kGxyd5GlLg=; b=HwsMJQlWAOKbUeBZcAbms7jcCXPiB8CV6qcWdCx/wOzJhimRAPb41HIVtzn/UpdVoz a/NbseVGT4n3GFLesukB5PuD+IM/o35JJlzAnldSQcH7WeVmTBc1faLSIrWZaV1pmjYL iPJcFYskFYPrRxScDDNAprNE24fT2GSWWUC61KtQ7/JIFlIgDPWVghUEUlmOUh57Xx/o KxIugAeZKwnyPLgMxvJXTFK4ueQU9iY3302HwLv92h+bW7ZY3vULR2T3bdsKkeSbnvru 63jYAMjqvNxWQ4Oy755DrQ+v7j3/5C4Cfvc2n3qZHPwxiW1AvW6rOnQs3Ql70+Qwyi1n Kn8w== 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=rrePr+VZirfI01USNFoXrDPzgo7TEJC64kGxyd5GlLg=; b=A79CJmLD99UzHdBBUuu2sB78HjrF/o/Fes/MFUizg1VgorhyYoSQSQy4btmxK1Xime rtlQ3+Gv0jUoJV2dCfVeK+VjHe/1B1UC60sO/dCHM8KnPay3loj5UzCMuuczbyqisyJs MwD/GTNQ0cQEazXhpynQIjNI2LFYFvXfEl33qLLEM3T/l1cSk/KkWrEymsFvsdvKnkcc suKCiMoJq/58E1x7kJ9T8Ufbu61lZAuzG73mKRhB+UBN5R2tGiOYBUTw/J9ZuQXO/MKM vqrtHy6afMsraxkNfbzXe1HiMPydZgUT/a7+i4EULxBwDrPum8tsIkIOaeTiLAqYuors KWNg== X-Gm-Message-State: APt69E3zTjzxFk68UH28x+gL7QoSPm/8+d4e50Byonu/adpuoBTdsEyy ctNKFB37TmPc83d4Hgu8YmP1 X-Google-Smtp-Source: AAOMgpdbIxAqSCo2AxDfPQ8HPb7XjSgbCMBOW8QuhLz2DN5hhtA7u2Q6SPep0lfCSp9R6GfJie87RA== X-Received: by 2002:adf:8e93:: with SMTP id q19-v6mr868601wrb.79.1529658524269; Fri, 22 Jun 2018 02:08:44 -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 b16-v6sm11490194wrm.15.2018.06.22.02.08.43 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 22 Jun 2018 02:08:43 -0700 (PDT) Date: Fri, 22 Jun 2018 11:08:59 +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: <20180622090859.ewqrwyyvtjj463or@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> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <833f6445-bcc2-ae2e-1dc7-45f33e0d8e8e@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 09:08:44 -0000 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. > Is it possible? Regards, -- Nélio Laranjeiro 6WIND