[vpp-dev] show trace bug in vpp stable 1707

Hi, by following commands in VPP Stable 1707, core dump accrued when packets received. trace add dpdk-input 100 sh trace Does it a bug or something changed in this version ? Thanks. ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/ma

Re: [vpp-dev] show trace bug in vpp stable 1707

Andrew, Are you able to recreate it with a debug build running in the debugger, so we can get a backtrace? Can you share details on how VPP is setup at the time of the crash? Chris From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Andrew Taylor Sent: Thursday

Re: [vpp-dev] trace

Ewan, Yes, it only works on the device input nodes. You're the second person to ask this recently, I guess we need to add a note to some documentation somewhere. :) Cheers, Chris From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of yug...@telincn.com Sent: Thursd

[vpp-dev] suspicion: vpp perf regression in master - 17.10-rc0~42..~48

Hi, We spotted a small packet throughput regression in vpp master branch affecting all perf test cases trended in CSIT by job [1]. All tests reported results data lower by 0.3 .. 0.5 Mpps. job_id vpp_version job_datejob_start_time job_duration #83 17.10-rc0~42-g28160f3 10

Re: [vpp-dev] trace

Folks, If one wants/needs to trace packets which vpp creates from whole cloth, here's how to do it. Typically, it's an input-node function. /* Top of node dispatch function */ u32 n_trace = vlib_get_trace_count (vm, node); /* per-buffer */ VLIB_BUFFER_TRACE_TRAJECTORY_INIT (b0); /*

[vpp-dev] Neighbor unreachability detection in vpp

Hi, I would need help with vpp IPv6 neighbor unreachability detection in vpp. I have a running vpp instance. Vpp has an interface with ip 2001::3, which is connected to linux network interface with ip 2001::5. When I ping 2001::5 from vpp, neighbor solicitation and advertisement runs and I can s

Re: [vpp-dev] VPP: Answer UDP Packets

Hi Neale, thanks for the info. I was already doing that, but I get an unpredictable behavior from vpp. My node listens for UDP packets. For each packet, it creates a new packet and send it back to the source IP address. Below the piece of code that set the buffer's parameters. adj_index_t adj

[vpp-dev] VPP classifier node plugin not invoked.

Hi, Possibly a repeat question on classifier. But could not get much help from other threads on this regards. I am trying to send UDP traffic from 10.10.122.117 to 10.10.121.179 and expect those to hit to my plugin "my4-dl-input" Don't even see the ip4-classifier in the packet tracer. Below is w

Re: [vpp-dev] vppctl bug?

[Resend] This is 100% reproducible, and kind of blocking our automation. Anyone knows the reason? Thanks very much! Regards, Yichen From: "Yichen Wang (yicwang)" Date: Tuesday, July 11, 2017 at 14:51 To: Denis Lotarev via vpp-dev Subject: vppctl bug? Hi, VPP folks, Using a pretty new VPP 1

Re: [vpp-dev] VPP classifier node plugin not invoked.

Dave, your inputs please. Thanks Get Outlook for Android From: Dharmaray Kundargi Sent: Thursday, July 13, 2017 10:17:47 PM To: vpp-dev@lists.fd.io Subject: VPP classifier node plugin not invoked. Hi, Possibly a repeat question on classif

Re: [vpp-dev] VPP classifier node plugin not invoked.

Thanks Shwetha I tried with setting for acl. There is some change in the output of packet tracer as below. I see the node ip4-inacl in the flow. But still ip4-classifier not seen and my node is also not hit. 15:32:15:849439: dpdk-input GigabitEthernet1b/0/0 rx queue 0 buffer 0x1a2a6: curre