Hello,
I am looking to understand the math and reasoning behind the 16K DPDK MBUFs per
socket allocation.
From: vpp/src/plugins/dkdp/device/dpdk.h
#define NB_MBUF (16<<10)
The following online documentation has a comment stating it is 32K per socket.
Above == 16K, and does not seem to
Dear Rubina,
On 8/20/18, Rubina Bianchi wrote:
> Hi dear Andrew
>
> What we were talked before was about "Worker Thread Deadlock".
We had that discussion in march or may. :-)
The one I had in mind was another thread, starting with your mail on
January 30. I forwarded to you unicast :-)
>
> I
Hello VPP experts:
I noticed that recently when I tried to build VPP with external DPDK (DPDK with
some local changes), the build system seems to ignore the
"vpp_uses_external_dpdk = yes". I checked out the changes in src\dpdk\Makefile
and compared the my working vpp folder and the latest
+ infra-steer...@lists.fd.io
On Mon, 2018-08-20 at 16:09 +0200, Marco Varlese wrote:
> The ARM verify job is failing due to "No space left on device" currently...
>
> 15:50:07 CXX pipe_cmds.lo
> 15:50:53 /w/workspace/vpp-arm-verify-master-ubuntu1604/build-
>
Hi dear Andrew
What we were talked before was about "Worker Thread Deadlock".
I tried to test scenario as you explained and started with 1M entry and after
that I doubled it at each run.
When I test with 4M entry size, I logged two things:
1. ps aux | grep vpp
2. First 5 lines of "vppctl show
The ARM verify job is failing due to "No space left on device" currently...
15:50:07 CXX pipe_cmds.lo
15:50:53 /w/workspace/vpp-arm-verify-master-ubuntu1604/build-
data/../extras/vom/vom/pipe_cmds.cpp:145:1: fatal error: error writing to
/tmp/cc3Q4khU.s: No space left on device
15:50:53 }
Hello,
People in this list may be interested in the message below.
Jerome
De : Naveen Joy
Répondre à : "OpenStack Development Mailing List (not for usage questions)"
Date : samedi 18 août 2018 à 03:29
À : "openstack-...@lists.openstack.org"
Objet : [openstack-dev] networking-vpp 18.07 for VPP
Yes, this causes test-debug target to take the old way (not cmake).
This, though, seems a bit counter-intuitive. Shouldn't setting the
value to "no" cause the build process to not use cmake?
On Mon, 2018-08-20 at 12:15 +0200, Damjan Marion wrote:
> >
> > On 20 Aug 2018, at 11:55, Klement Sekera
> On 20 Aug 2018, at 11:55, Klement Sekera wrote:
>
> Hi Damjan,
>
> it seems that the test-debug target is broken with the patch. The build
> process triggered by test-debug target jumps on the cmake train, but
> that train doesn't bring in the APIGEN and other stuff (e.g.
>
Hi Damjan,
it seems that the test-debug target is broken with the patch. The build
process triggered by test-debug target jumps on the cmake train, but
that train doesn't bring in the APIGEN and other stuff (e.g.
libvppapiclient.so).
I don't see vpp-api mentioned in src/CMakeLists.txt. Should it
Hi Steven,
Thanks a lot for your help. It works!
Best whishes,
Aleksander
On Fri, Aug 17, 2018 at 07:08 PM, steven luong wrote:
>
>
>
> Aleksander,
>
>
>
>
>
>
>
> I found the CLI bug. You can easily workaround with it. Please set the
> physical interface state up first in your CLI
11 matches
Mail list logo
