Could you share the output of:
~# strace vpp -c /usr/share/vpp/vpp.conf
With DPDK enabled (ie with your targeted config which is failing)?
ben
> -Original Message-
> From: Manoj Iyer
> Sent: jeudi 28 mai 2020 01:11
> To: Damjan Marion ; Manoj Iyer
> Cc: Benoit Ganne (bganne) ; vpp-dev@l
I guess you are using extras/rpm/vpp-suse.spec (SUSE)? It looks like it misses
several evolutions compared to extras/rpm/vpp.spec (CentOS).
I am not familiar with SUSE but you can try to look the CentOS specfile to fix
it.
ben
> -Original Message-
> From: vpp-dev@lists.fd.io On Behalf
Hi Damjan,
I got some feedback regarding switching default compiler from gcc to clang in
VPP, from compiler team.
" Neither LLVM nor GCC tune much for Neoverse N1, I think the difference is
that GCC has better vectorization and a better optimized AArch64 backend. GCC10
has just been released an
Hi Andrew,
In my case it failed several times and appeared to be triggered by
seemingly harmless code changes, but it seemed like the problem was
reproducible for a given version of the code. What seemed to matter was
when I changed things related to local variables inside the
set_ipfix_exporter_c
Hi Elias,
Yeah it all does point to something like uninitialized data - I ran yesterday
the tests on two different machines for a while, apparently without the
issues...
The CI runtime environment is much more dynamic - it’s an ephemeral docker
container that is orchestrated by the nomad and i
Hi Miklos,
> I see the NAT plugin already supports TCP MSS clamping but it is implemented
> only in in2out direction.
>
> We have endpoints with wrong MTUs behind tunnels and not all the traffic is
> NATed. Hence, it would be very nice to have generic support for MSS clamping
> that could be e
Hi Miklos,
May be, it will help https://gerrit.fd.io/r/c/vpp/+/15144
-br
Mohsin
From: on behalf of Ole Troan
Date: Thursday, May 28, 2020 at 11:23 AM
To: Miklos Tirpak
Cc: "vpp-dev@lists.fd.io"
Subject: Re: [vpp-dev] generic TCP MSS clamping
Hi Miklos,
> I see the NAT plugin already support
Good find Mohsin. So it's only missing clamping on RX. I'm sure Miklos can add
that.
Cheers,
Ole
> On 28 May 2020, at 12:23, Mohsin Kazmi (sykazmi) wrote:
>
> Hi Miklos,
>
> May be, it will help https://gerrit.fd.io/r/c/vpp/+/15144
>
> -br
> Mohsin
> From: on behalf of Ole Troan
> Date: Thur
Hello,
I have just added an use case over at
https://wiki.fd.io/view/VPP/IPSec_and_IKEv2#IPSec_between_VPP_peers.2C_tunneling_IPv4_over_IPv6
It is pretty bare bones for now, but I hope to continue to improve it. Feel
free to point out mistakes if there are any.
I also will try to write a longer v
A few weeks back, I became aware of the following issue with the LISP tests:
/vpp/build-root/install-vpp_debug-native/vpp/bin/vpp[63989]:
vnet_lisp_add_del_locator_set:2140: Can't delete a locator that supports a
mapping!
/vpp/build-root/install-vpp_debug-native/vpp/bin/vpp[63989]: received
signal
Hi Andrew,
> Could you push as a separate change the code that reliably gives you
> the error in the LISP unit test
I tried but today, whatever I do, I cannot reproduce the test failure
anymore. All tests pass now even when I try exactly the same code for
which the test failed yesterday.
For exa
Most Excellent!
Congratulations to the VPP & CSIT community for all of the effort to
complete another high quality VPP release.
Special thanks to Andrew for his management of the release and
improvements to the release process!
-daw-
On 5/27/2020 5:27 PM, Andrew Yourtchenko wrote:
Dear al
Thank you for the pointer, this is exactly what I was looking for. I will
rebase the patch and add RX support.
Thanks,
Miklos
From: otr...@employees.org
Sent: Thursday, May 28, 2020 12:43 PM
To: Mohsin Kazmi (sykazmi)
Cc: Miklós Tirpák ; vpp-dev@lists.fd.io
Su
Hi all,
So, the problem is encountered with my C++ client when receiving a reply. The
strange thing is that this happens only with a specific type of api
request-reply.
Follows the segfault stack trace:
>
> Thread 1 "sample_plugin_client" hit Breakpoint 1,
> vapi_type_msg_header1_t_ntoh (h=0x0)
[Edited Message Follows]
Hi all,
So, the problem is encountered with my C++ client when receiving a reply. The
strange thing is that this happens only with a specific type of api
request-reply.
Follows the segfault stack trace:
>
> Thread 1 "sample_plugin_client" hit Breakpoint 1,
> vapi_type_
Hey,
swapping context makes no sense since context is for client - client generates
whatever context it wants and vpp just copies it from request to response, so
that client can match response with request. So there is no reason for client
to swap it when sending the message and then swap it ba
Hi,
When the carrier of an interface comes up, e.g. because someone plugs a cable,
VPP function “ send_sw_interface_event()” sends a message to clients
indicating the event
We are seeing a delay of 4-6 seconds from the time we plug the cable until the
function “ send_sw_interface_event() is
Paul,
This is an excellent catch, thanks!! I will give it a go in test-debug...
--a
> On 28 May 2020, at 16:15, Paul Vinciguerra wrote:
>
>
> A few weeks back, I became aware of the following issue with the LISP tests:
>
> /vpp/build-root/install-vpp_debug-native/vpp/bin/vpp[63989]:
> vnet
Hi Elias,
I will let Ole merge the patch it if he is happy with it.
Thanks a lot!
—a
> On 28 May 2020, at 16:19, Elias Rudberg wrote:
>
> Hi Andrew,
>
>> Could you push as a separate change the code that reliably gives you
>> the error in the LISP unit test
>
> I tried but today, whatever
Ouch. Attempting to run “make test-debug” resulted in a lot of unrelated
sadness... I will do some more testing to ensure it’s not a PEBCAC...
--a
> On 28 May 2020, at 21:25, Andrew Yourtchenko via lists.fd.io
> wrote:
>
> Paul,
>
> This is an excellent catch, thanks!! I will give it a go i
I changed the fix using %U and a new unformat_l3_port function, as
suggested by Paul:
https://gerrit.fd.io/r/c/vpp/+/27280
This works fine, but I wasn't sure where to put the unformat_l3_port
function. Now it's in vnet/udp/udp_format.c -- let me know if you have
a better idea about where it shoul
> On 29 May 2020, at 00:02, Elias Rudberg wrote:
>
> I changed the fix using %U and a new unformat_l3_port function, as
> suggested by Paul:
>
> https://gerrit.fd.io/r/c/vpp/+/27280
My opinion it’s an incorrect and unnecessary generalization/abstraction:
1) port is a L4 concept, not L3. Cf
Ah. OK, now it's changed to the hopefully better name
"unformat_udp_port".
/ Elias
On Fri, 2020-05-29 at 00:32 +0200, Andrew 👽 Yourtchenko wrote:
> > On 29 May 2020, at 00:02, Elias Rudberg
> > wrote:
> >
> > I changed the fix using %U and a new unformat_l3_port function, as
> > suggested by Pa
23 matches
Mail list logo
