From: Abeeha Aqeel Sent: Friday, February 1, 2019 5:32 PM To: dmar...@me.com Subject: RE: [vpp-dev] VPP register node change upper limit I am using the vpp pppoe plugin and that’s how its working. I do see an option in the vnet/interface.c to create interfaces that do not need TX nodes, but I am not sure how to use that. Also I can not figure out where the nodes created along with the pppoe sessions are being used as they do not show up in the “show runtime” or the trace of packets. From: Damjan Marion via Lists.Fd.Io Sent: Friday, February 1, 2019 5:23 PM To: Abeeha Aqeel Cc: vpp-dev@lists.fd.io Subject: Re: [vpp-dev] VPP register node change upper limit On 1 Feb 2019, at 11:32, Abeeha Aqeel <abeeha.aq...@xflowresearch.com> wrote: Dear All, I am trying to create 64k PPPoE sessions with VPP but VPP crashes after creating 216 sessions each time. From the system logs it seems that it crashes while trying to register a node and that node’s index is greater than the limit (1024). (attached screenshot of the trace) >From the “show vlib graph”, I can see that two new nodes are registered for >each session i.e. pppoe_session0-tx and pppoe_session0-output. Can someone guide me to how to increase the upper limit on the number of nodes? Currently number of nodes is limited by buffer metadata space, and the way how we calculate node errors (vlib_error_t). Currently vlib_error_t is u16, and 10 bits are used for node. That gives you 1 << 10 of node indices, so roughly 300-400 interfaces (2 nodes per interface + other registered nodes < 1024). This is something we can improve, but the real question is, do you really want to go that way. Have you considered using some more lighter way to deal with large number of sessions... -- Damjan
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12120): https://lists.fd.io/g/vpp-dev/message/12120 Mute This Topic: https://lists.fd.io/mt/29617327/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
