[vpp-dev] DPDK plugin - port ID and index

2018-08-17 Thread Andrzej Ostruszka
Hello all I'm new to VPP so please bear with my ignorance in its architecture/internals/development process :). I'd like to ask for some change regarding DPDK plugin - to be specific to differentiate between "device index" (in device table) and "device id" (the DPDK port ID). More information ab

[vpp-dev] VPP crashes on multi core

2018-08-17 Thread Mehran Memarnejad
Hi, In default configuration of vpp on single core, everything seems ok but when I want to get the most out of my hardware resources and modify vpp startup config, it crashes at some stages. Here is some carshes: 1- I set interface's IP and then when I plugged cables in ports, It suddenly carshes a

Re: [vpp-dev] LACP link bonding issue

2018-08-17 Thread Aleksander Djuric
Hi Steven, GDB shows that the vlib_process_get_events function always return ~0, except one time at start and lacp_schedule_periodic_timer is never runs after that. It's looks the same on both sides. I have added some debug info. Please look at the log: ### VPP1:9.58 ###

[vpp-dev] API If Client doesnot have any pending request , it wont read the queue

2018-08-17 Thread chetan bhasin
Hi, We are facing an issue during usage of API framework. We have open a Non-blocking connection from Client app. If Client does not have any pending request then it skip reading the responses in vapi_dispatch . Please suggest vapi_error_e vapi_dispatch (vapi_ctx_t ctx) { vapi_error_e rv = VA

Re: [vpp-dev] API If Client doesnot have any pending request , it wont read the queue

2018-08-17 Thread Klement Sekera via Lists.Fd.Io
What exactly is the issue? According to vapi_dispatch() docstring this is expected: /**  * @brief loop vapi_dispatch_one until responses to all currently outstanding  * requests have been received and their callbacks called  *  * @note the dispatch loop is interrupted if any error is encountered o

Re: [vpp-dev] Bonding error -- uio_interrupt

2018-08-17 Thread Damjan Marion via Lists.Fd.Io
interesting, works fine for me on c3000, but i use vfio. Try with vfio, either with enabling iommu or using noiommu mode (kernel 4.4+) -- Damjan > On 17 Aug 2018, at 03:22, carlito nueno wrote: > > Hi, > > I am trying to bond two Intel 82599 on Intel Atom C3000. But I am > getting uio_i

Re: [vpp-dev] API If Client doesnot have any pending request , it wont read the queue

2018-08-17 Thread chetan bhasin
Hi Klement, Thanks for your reply! The exact problem statement is , we are trying to send some events from VPP to client app , but client is not able to read those events api messages until it has some pending requests. So as a work-around we are sending control ping after few seconds from client

Re: [vpp-dev] DPDK plugin - port ID and index

2018-08-17 Thread Damjan Marion via Lists.Fd.Io
Are you on some old vpp version? We did recently what i think you are asking for, port_id is now decoupled from device_index... -- Damjan > On 17 Aug 2018, at 10:15, Andrzej Ostruszka wrote: > > Hello all > > I'm new to VPP so please bear with my ignorance in its > architecture/internals/d

Re: [vpp-dev] API If Client doesnot have any pending request , it wont read the queue

2018-08-17 Thread Klement Sekera via Lists.Fd.Io
Hi Chetan, I think that in this case it's better to use blocking interface, as you are waiting for the events to come. You can take a look at test/ext/vapi_c_test.c - tests called  test_stats_1, _2 & _3 deal with stats - first two show a blocking, efficient interface, third one is non-blocking, w

Re: [vpp-dev] API If Client doesnot have any pending request , it wont read the queue

2018-08-17 Thread chetan bhasin
Thanks a lot Klement. On Fri, Aug 17, 2018 at 5:36 PM, Klement Sekera wrote: > Hi Chetan, > > I think that in this case it's better to use blocking interface, as you > are waiting for the events to come. > > You can take a look at test/ext/vapi_c_test.c - tests called > test_stats_1, _2 & _3 dea

Re: [vpp-dev] VPP crashes on multi core

2018-08-17 Thread Dave Barach via Lists.Fd.Io
Please refer to https://wiki.fd.io/view/VPP/BugReports for bug reporting, also https://wiki.fd.io/view/VPP/Configuration_Tool If you expect folks to volunteer to help you: write up your system configuration, vpp version and configuration, and so forth to a reasonable standard. From: vpp-dev@li

Re: [vpp-dev] DPDK plugin - port ID and index

2018-08-17 Thread Andrzej Ostruszka
On 17.08.2018 14:07, Damjan Marion wrote: > Are you on some old vpp version? > > We did recently what i think you are asking for, port_id is now > decoupled from device_index... Oh shoot! Yes indeed our client is using older version of VPP - my bad I should have checked current version. Now I'v

[vpp-dev] vector packet processing works in case of multiple interfaces tied to a CPU core (vpp worker).

2018-08-17 Thread Vinay Krishna Ambati
Hi, We have a heavy node that does lots of packet field modifications (like encap tunnels) and is the next node for dpdk-input. This node is followed by another node and outputs the packet to the dpdk-output node. We are observing some packet corruption in case we have more than 1 interface co

Re: [vpp-dev] NAT Fragment Reassembly

2018-08-17 Thread Jon Loeliger
On Thu, Aug 16, 2018 at 12:39 AM, Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES at Cisco) wrote: > Max_frag value is applied when fragments arrived out of order > Ahhh That wasn't clear... But I see... > (non-initial fragments arrive before first fragment which contains L4 > header),

Re: [vpp-dev] LACP link bonding issue

2018-08-17 Thread steven luong via Lists.Fd.Io
Aleksander, I found the CLI bug. You can easily workaround with it. Please set the physical interface state up first in your CLI sequence and it will work. create bond mode lacp load-balance l23 bond add BondEthernet0 GigabitEtherneta/0/0 bond add BondEthernet0 GigabitEtherneta/0/1 set interface

Re: [vpp-dev] VPP crashes on multi core

2018-08-17 Thread Mehran Memarnejad
Here is the system characteristics: == NODE: DUT1 CPU: Model name:Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz CPU(s):16 Thread(s) per core:2 Core(s) per socket:8 Socket(s):1 NUMA node0 CPU(s):0-15