Aside from this p2p_ethernet load test, the only failing extended test is the
whole TestVxlanGpe class.
The reason is that scapy 2.3.3 does not know of layer VXLAN, and there is no
scapy patch within vpp to address this.
How do you want to handle this ?
--
Gabriel Ganne
Hi Justin,
The expectation until now has been that options are not parsed until hitting
the tcp related nodes. If tcp_options_parse is enough, then make it public and
use it. That function just expects a tcp_options_t struct for outputting the
results so no need for a tcp_connection_t. Now, i
On Tue, 2017-11-14 at 12:45 +, Shachar Beiser wrote:
>
>
>
>
>
>
>
> From: Marco Varlese [mailto:mvarl...@suse.de]
>
> Sent: Tuesday, November 14, 2017 1:29 PM
>
> To: Shachar Beiser ; vpp-dev@lists.fd.io
>
> Cc: Amir Zeidner ; Shahaf Shuler ;
> Eyal Lavee
>
> Subject: Re: [vpp-d
Likely you ran out of memory. A patch was merged last night that should help
alleviate this by reducing the number of parallel builds.
The new C++ stuff is a hog and is triggering this for several people. If you
don't intend to use it, then perhaps looking for this section in
builds-data/platfo
Hi Dave,
Thanks (again) for your reply.
> Brief commercial: hopefully you added your node to the ip4 unicast feature
> arc,
> configured to grab pkts, pre-ip4/6-lookup.
Indeed, I added my node to the ip4-unicast feature arc.
> In feature-arc land, the following one-liner sets next0 so pkts wil
From: Marco Varlese [mailto:mvarl...@suse.de]
Sent: Tuesday, November 14, 2017 1:29 PM
To: Shachar Beiser ; vpp-dev@lists.fd.io
Cc: Amir Zeidner ; Shahaf Shuler ;
Eyal Lavee
Subject: Re: [vpp-dev] VPP with DPDK external build
It looks like you didn't build the dpdk plugin (dpdk_plugin.so) in V
Dear Justin,
Brief commercial: hopefully you added your node to the ip4 unicast feature arc,
configured to grab pkts, pre-ip4/6-lookup.
In feature-arc land, the following one-liner sets next0 so pkts will visit the
next enabled feature. The last node in the ip4-unicast feature arc is
ip4-look
Hi vpp-dev:
Excuse me. Could you give me a hand? I have a problem when I build
vpp. My environment is vmware workstation + centos7.4 . The capture as
follows. Was this error caused by “make build-release”.
说明: cid:image001.png@01D35D70.582DE740
I used this com
Hi vpp-dev:
Excuse me. Could you give me a hand? I have a problem when I build
vpp. My environment is vmware workstation + centos7.4 . The capture as
follows. Was this error caused by "make build-release".
I used this command "./build-root/vagrant/build.sh".
It does not complete within 20 minutes on other machines.
> I don't think we should do scale tests as part of verification tests.
Agree
-Original Message-
From: Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco)
[mailto:ksek...@cisco.com]
Sent: Tuesday, November 14, 2017 2:47
It looks like you didn't build the dpdk plugin (dpdk_plugin.so) in VPP...
The first command you ran
> root@kickseed:/home/shacharbe/vpp.dlopen# sudo
> ./src/bin/vpp -c ${PWD}/src/vpp/conf/startup.conf
is correct but the DPDK plugin is not loaded (I can't see it listed in the
o
Cool!
Sure, you can use vat in that case as well.
--a
> On 13 Nov 2017, at 22:08, Yuliang Li wrote:
>
> It works! Thanks.
>
> Another question: if I want to use ACL plugin in non-debug build (say,
> build-release), is can I use vat? Or I need to use the python code?
>
>> On Mon, Nov 13, 201
Hi ,
I have successfully build the DPDK by:
make T=x86_64-native-linuxapp-gcc install CPU_CFLAGS="-g -fpic"
then I compiled successfully the vpp with the DPDK external by following
the procedure :
cd vpp/
sed -i '/vpp_uses_dpdk_mlx5_pmd/s/^# //g' buil
It is ...
it takes ~10 seconds to create 1000 subifs on a beefy UCS and the case
tries to create 10, so that would indicate a runtime of
~16minutes...
Quoting Ole Troan (2017-11-14 03:53:28)
> Klement,
>
> > I don't know what to tell you ... I was never a fan of getting the API
> > trace pos
14 matches
Mail list logo
