Hi Steven and VPP guys,
I'm studying the lacp implementation. and want to know if it is
possible that Numa is considered in LACP active port selection. As we all know,
if slave with local numa can be preferred to help improve throughput.
One question is that current code seems n
libmemif is compiled as part of per-patch verify jobs, including ubuntu 18.04
so must be something special in your setup. Can you paste your whole console
log, starting with clean git checkout to pastebin?
—
Damjan
> On Jun 3, 2019, at 4:17 PM, Rafał Krych wrote:
>
> Hello,
>
> I think it
Hi Jin,
Thank you for the describtion.
Great if you can push your patch to gerrit and I will review and merge.
Best regards,
Ole
> On 4 Jun 2019, at 08:29, Jin Zhihua wrote:
>
> Dear all:
> I am developing a vpp client built with govpp by using “AsyncConnect”
> function. The first tim
> On 11 Jun 2019, at 19:01, guangwei wrote:
>
> I'am now working on version 19.04, and find the behavior of
> vlib_buffer_free_no_next is different between 18.07 and 19.04, I think it's
> the bug for 19.04:
>
> always_inline void
> vlib_buffer_free_no_next (vlib_main_t * vm,
>/* poin
I'am now working on version 19.04, and find the behavior of
vlib_buffer_free_no_next is different between 18.07 and 19.04, I think it's
the bug for 19.04:
always_inline void
vlib_buffer_free_no_next (vlib_main_t * vm,
/* pointer to first buffer */
u32 * buffers,
/* number of buffers to free *
Dear all:
I am developing a vpp client built with govpp by using “AsyncConnect”
function. The first time I run the client before or after vpp, everything is
ok. After I restart vpp while keeping the client running, the CPU usage of the
client becomes high to around 70%.
I have fou
Hello,
I think it is not the same issue as the one reported in this ticket:
https://jira.fd.io/browse/VPP-1244
I'm doing some kind of research project for my company (evaluating libmemif
performance). Unfortunately since GLIBC 2.27 introduction (Ubuntu 18.04) my
test program fails to build with s
