Re: [vpp-dev] Question about VPP plugin/node's life cycle

Yes, generally you want to put as less as possible into plugin init code and simply initialise data structures at the moment when feature is configured/enabled. If you have process node, it should be disabled and later enabled by using event message... Please note that there is also a way to

Re: [vpp-dev] vpp 18.07.1 hangs on intel x520-sr2

Just try to run testpmd on that port, your traceback shows that your problem happens inside DPDK code... -- Damjan > On 19 Oct 2018, at 22:28, Tomasz Płaza wrote: > > No I have not. Are there any special steps I should follow? > > On 2018-10-19 22:11 Damjan Marion

Re: [vpp-dev] VPP/Using VPP In A Multi-thread Model

Building generally that kind of pipelines is bad idea, as it will be as slow as slowest part of the pipeline. It typically suffer of core-to-core transfer so our model is to keep packet on the same core as much as possible. In some cases you need to handoff packet to different core (NAT plugin

Re: [vpp-dev] one question IP checksum

Hi Yuwei, I see that you are using VXLAN to carry L3 packets which seems to still have ethernet header. This is not standard usage of VXLAN so I am not aware of a way to achieve what you desired via some kind of configuration of VPP. A more optimal (also not standard) way may be to just send

Re: [vpp-dev] one question IP checksum

Thanks a lot for your detail reply, John. My scenario is vxlan over l3 network, which means after decapsulation, vpp will use ip header to execute the forward function. I use this command to create the tunnel: "vppctl create vxlan tunnel src 10.0.0.1 dst 10.0.0.2 vni 24 encap-vrf-id 0

[vpp-dev] VPP/Using VPP In A Multi-thread Model

Hello Everyone: About the multi-thread mode of VPP, I have a question. After read the following wiki page, I understand that user could allocation 1 or more worker thread to 1 physical interface, and could also bind a worker thread or main thread to a specific CPU core.