Re: [vpp-dev] VXLAN and RSS

2022-01-14 Thread Ole Troan
> 0x206a: IP 48.0.0.52.1025 > 16.0.0.52.12: UDP, length 18 >> 11:20:55.856296 IP 10.0.0.0.28635 > 10.0.0.1.6081: Geneve, Flags [none], vni >> 0x206a: IP 16.0.0.51.1025 > 48.0.0.51.12: UDP, length 18 >> >> On Fri, Jan 14, 2022 at 10:40 AM Neale Ranns wrot

Re: [vpp-dev] VXLAN and RSS

2022-01-14 Thread Ole Troan
gth 18 > > On Fri, Jan 14, 2022 at 10:40 AM Neale Ranns wrote: > Hi Pim, > > > > For VXLAN the intention is to use random source ports. The code you sight > builds the ‘static’ portion of the imposed header. The source ports are > overwritten with the hash of the en

Re: [vpp-dev] VXLAN and RSS

2022-01-14 Thread Neale Ranns
at 11:28 To: Neale Ranns Cc: vpp-dev Subject: Re: [vpp-dev] VXLAN and RSS Hoi, Neale, thank you for pointing that out! I verified the intent, and I can confirm that VXLAN uses random source ports [1], and so does GENEVE [2], so this is WAI. I mirrored traffic between the two VPP hosts, while

Re: [vpp-dev] VXLAN and RSS

2022-01-14 Thread Pim van Pelt
he imposed header. The source ports are > overwritten with the hash of the encapped packet in encap.c:246 > > > > /neale > > > > > > *From: *vpp-dev@lists.fd.io on behalf of Pim van > Pelt via lists.fd.io > *Date: *Thursday, 13 January 2022 at 23:37 > *To:

Re: [vpp-dev] VXLAN and RSS

2022-01-14 Thread Neale Ranns
lists.fd.io Date: Thursday, 13 January 2022 at 23:37 To: vpp-dev Subject: [vpp-dev] VXLAN and RSS Hoi folks, I did a deep dive today on VXLAN, GENEVE and compared it to GRE and L2XC - the full read is here: https://ipng.ch/s/articles/2022/01/13/vpp-l2.html One thing that I observed is that both VXLAN

Re: [vpp-dev] VXLAN and RSS

2022-01-13 Thread Florin Coras
>>> It specifically suggests that “the source port SHOULD be calculated using a >>> hash of the encapsulated packet headers using, for example, a traditional >>> 5-tuple.” >>> >>> Yours, >>> Joel >>> >>> From: vpp-dev@li

Re: [vpp-dev] VXLAN and RSS

2022-01-13 Thread Ole Troan
ted using a >> hash of the encapsulated packet headers using, for example, a traditional >> 5-tuple.” >> >> Yours, >> Joel >> >> From: vpp-dev@lists.fd.io On Behalf Of Pim van Pelt >> via lists.fd.io >> Sent: Thursday, January 13, 2022 5

Re: [vpp-dev] VXLAN and RSS

2022-01-13 Thread Florin Coras
m: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> <mailto:vpp-dev@lists.fd.io>> On Behalf Of Pim van Pelt via lists.fd.io > <http://lists.fd.io/> > Sent: Thursday, January 13, 2022 5:37 PM > To: vpp-dev mailto:vpp-dev@lists.fd.io>> > Subject: [vpp-dev] VXLAN and R

Re: [vpp-dev] VXLAN and RSS

2022-01-13 Thread Joel Halpern via lists.fd.io
of the encapsulated packet headers using, for example, a traditional 5-tuple.” Yours, Joel From: vpp-dev@lists.fd.io On Behalf Of Pim van Pelt via lists.fd.io Sent: Thursday, January 13, 2022 5:37 PM To: vpp-dev Subject: [vpp-dev] VXLAN and RSS Hoi folks, I did a deep dive today on VXLAN, GENEVE

[vpp-dev] VXLAN and RSS

2022-01-13 Thread Pim van Pelt
Hoi folks, I did a deep dive today on VXLAN, GENEVE and compared it to GRE and L2XC - the full read is here: https://ipng.ch/s/articles/2022/01/13/vpp-l2.html One thing that I observed is that both VXLAN and GENEVE use static source ports. In the case of VLLs, (an l2 xconnect from a customer