Re: RES: RES: [vpp-dev] NAT memory usage problem for VPP 20.09 compared to 20.05 due to larger translation_buckets value

2020-11-26 Thread Klement Sekera via lists.fd.io
Hi, memory settings are gone from startup.conf. As I already mentioned, those were pointless anyway as the tables now reside in main heap. Translation hash buckets are calculated automatically based on max sessions and max users parameters. Thanks, Klement > On 26 Nov 2020, at 21:50, Damjan M

Re: RES: RES: [vpp-dev] NAT memory usage problem for VPP 20.09 compared to 20.05 due to larger translation_buckets value

2020-11-26 Thread Damjan Marion via lists.fd.io
Will leave that to NAT folks to comment… They have multiple tables and they are two per thread… — Damjan > On 26.11.2020., at 20:27, Marcos - Mgiga wrote: > > Of course. > > Since I intend to implement VPP as a deterministic CGN gateway I have some > parameters regarding to nat config, for

Re: [vpp-dev] bihash doc fix

2020-11-26 Thread hemant via lists.fd.io
Thanks, Dave. Hemant From: v...@barachs.net Sent: Thursday, November 26, 2020 7:51 AM To: hem...@mnkcg.com; vpp-dev@lists.fd.io Subject: RE: [vpp-dev] bihash doc fix Planted a redirect from wiki.fd.io to fd.io docs, removed the duplicate documentation from the wiki, and made the indic

RES: RES: [vpp-dev] NAT memory usage problem for VPP 20.09 compared to 20.05 due to larger translation_buckets value

2020-11-26 Thread Marcos - Mgiga
Of course. Since I intend to implement VPP as a deterministic CGN gateway I have some parameters regarding to nat config, for example: translation hash buckets, translation hash memory , user hash buckets and user hash memory to be configured in startup.conf. In this context I would like to kn

Re: RES: [vpp-dev] NAT memory usage problem for VPP 20.09 compared to 20.05 due to larger translation_buckets value

2020-11-26 Thread Damjan Marion via lists.fd.io
Sorry, I don’t understand your question. Can you elaborate further? -- Damjan > On 26.11.2020., at 20:05, Marcos - Mgiga wrote: > > Hello, > > Taking benefit of the topic, how you suggest to monitor if translation hash > bucket value has an appropriate value? What about translation hash me

RES: [vpp-dev] NAT memory usage problem for VPP 20.09 compared to 20.05 due to larger translation_buckets value

2020-11-26 Thread Marcos - Mgiga
Hello, Taking benefit of the topic, how you suggest to monitor if translation hash bucket value has an appropriate value? What about translation hash memory, user hash buckets and user hash memory ? How do I know if I increase or decrease those values? Best Regards Marcos -Mensagem origi

Re: [vpp-dev] NAT memory usage problem for VPP 20.09 compared to 20.05 due to larger translation_buckets value

2020-11-26 Thread Damjan Marion via lists.fd.io
Dear Elias, Let me try to explain a bit underlying mechanics. Let’s assume your target number of sessions is 10M and we are talking about 16byte key size. That means each hash entry (KV) is 24 bytes (16 bytes key and 8 bytes value). In the setup you were mentioning, with 1<<20 buckets, your wil

Re: [vpp-dev] NAT memory usage problem for VPP 20.09 compared to 20.05 due to larger translation_buckets value

2020-11-26 Thread Klement Sekera via lists.fd.io
Hi Elias, mentioned formula was updated per guidance from Damjan: optimal number of bihash buckets is number of expected entries divided by 2.5 rounded to closest pow2 (might he higher or lower). Regarding memory usage: bihash code has been changed and now uses main heap. Consequently, it igno

[vpp-dev] NAT memory usage problem for VPP 20.09 compared to 20.05 due to larger translation_buckets value

2020-11-26 Thread Elias Rudberg
Hello VPP experts, We are using VPP for NAT44 and are currently looking at how to move from VPP 20.05 to 20.09. There are some differences in the way the NAT plugin is configured. One difficulty for us is the maximum number of sessions allowed, we need to handle large numbers of sessions so that

Re: [vpp-dev] Custom VxLAN port

2020-11-26 Thread Benoit Ganne (bganne) via lists.fd.io
Hi Paul et al, > VPP's vxlan may be great for in memory transfers between containers, but > it is hard on real network infrastructure, because it doesn't provide the > signals to upstream routers for ECMP. > > /* UDP header, randomize src port on something, maybe? */ > udp->src_port =

Re: [vpp-dev] Custom VxLAN port

2020-11-26 Thread hemant via lists.fd.io
See the vxlan rfc. https://tools.ietf.org/html/rfc7348 VXLAN is a layer-2 tech - see section 5, Figure, 1 with the Ethernet header as the outermost header. ECMP is a layer-3 concept. See Figure 3 for when an IP network connects two VXLAN networks. Also see Figure 4. Hemant -Original M

Re: [vpp-dev] Custom VxLAN port

2020-11-26 Thread Paul Vinciguerra
Hi Ole, Artem, For the benefit of others, VPP's vxlan may be great for in memory transfers between containers, but it is hard on real network infrastructure, because it doesn't provide the signals to upstream routers for ECMP. */* UDP header, randomize src port on something, maybe? */ *udp->src_p

Re: [vpp-dev] [csit-dev] event-logger debug CLI cleanup patch failing validation: [vpp gerrit 30124]

2020-11-26 Thread Dave Barach
OK, pushed another patch-set to remove the old command. Thanks... Dave From: Vratko Polak -X (vrpolak - PANTHEON TECH SRO at Cisco) Sent: Thursday, November 26, 2020 8:48 AM To: Dave Barach ; 'Andrew 👽 Yourtchenko' Cc: csit-...@lists.fd.io; vpp-dev@lists.fd.io Subject: RE: [vpp-dev] [csit-d

Re: [vpp-dev] [csit-dev] event-logger debug CLI cleanup patch failing validation: [vpp gerrit 30124]

2020-11-26 Thread Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) via lists.fd.io
In the meantime, [0] got merged everywhere important. You can try to remove the old CLI to see if it passes now. Vratko. From: vpp-dev@lists.fd.io On Behalf Of Dave Barach Sent: Thursday, 2020-November-26 14:36 To: 'Andrew 👽 Yourtchenko' ; Vratko Polak -X (vrpolak - PANTHEON TECH SRO at Cisco)

Re: [vpp-dev] [csit-dev] event-logger debug CLI cleanup patch failing validation: [vpp gerrit 30124]

2020-11-26 Thread Dave Barach
Thanks for the pointer(s), guys. Fixed, new patch-set uploaded... From: Andrew 👽 Yourtchenko Sent: Thursday, November 26, 2020 8:18 AM To: Dave Barach Cc: vrpo...@cisco.com; csit-...@lists.fd.io; vpp-dev@lists.fd.io Subject: Re: [vpp-dev] [csit-dev] event-logger debug CLI cleanup patch fail

Re: [vpp-dev] Custom VxLAN port

2020-11-26 Thread Artem Glazychev
Ole, I don't fully understand, If I want to support configurable UDP port per tunnel, I need to extend "vxlan_tunnel_t" or "vxlan_gpe_tunnel_t" or "vxlan_gbp_tunnel_t" or all of them. So this is what I meant in point 2. Why 2.5? :) Or can I only use the "vxlan_gbp_tunnel_t" for this purpose? Th

Re: [vpp-dev] [csit-dev] event-logger debug CLI cleanup patch failing validation: [vpp gerrit 30124]

2020-11-26 Thread Andrew Yourtchenko
I see the failure in the doc verify job: 22:49:10 Processing siphon for markdown from clicmd.siphon... 22:49:10 INFO:siphon.process.clicmd:Parsing items in file "build-root/docs/siphon_fragments/clicmd.siphon". 22:49:12 ERROR:siphon.process.clicmd:Exception parsing item: { 22:49:12 "block": "

Re: [vpp-dev] bihash doc fix

2020-11-26 Thread Dave Barach
Planted a redirect from wiki.fd.io to fd.io docs, removed the duplicate documentation from the wiki, and made the indicated correction. See https://gerrit.fd.io/r/c/vpp/+/30151. From: vpp-dev@lists.fd.io On Behalf Of hemant via lists.fd.io Sent: Wednesday, November 25, 2020 5:09 PM To: hem...

Re: [vpp-dev] [csit-dev] event-logger debug CLI cleanup patch failing validation: [vpp gerrit 30124]

2020-11-26 Thread Dave Barach
OK, thanks for [0]. Even with the old debug CLI supported on the vpp side, the patch continues to fail validation. I’m going to try again (“recheck”) and see what happens. D. From: vpp-dev@lists.fd.io On Behalf Of Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) via lists.fd.

Re: [vpp-dev] [csit-dev] event-logger debug CLI cleanup patch failing validation: [vpp gerrit 30124]

2020-11-26 Thread Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) via lists.fd.io
Compatibility enhancement on CSIT side: [0]. > easy enough to support both “elog trace” and “event-logger trace” on the vpp > side. When [0] is merged (also to oper branch), the support on VPP side can be dropped. > add a binary API and use it in the csit robot framework +1 to that, especially