Re: [vpp-dev] questions about SCTP feature in VPP

[Marco Varlese]

Hi,

On 2/15/19 7:07 AM, Dong, Yao wrote:
> Dear expert,
> 
>  
> 
> I’m a developer of wireless base station on 5G NR. I have a stupid
> question about SCTP:
> 
> 1.   Is SCTP fully supported by VPP? Which sub function is not
> supported yet?
Multiple sub-connections support is not implemented yet.
> 
> 2.   Is it running in kernel space or user space?
User-space
> 
> 3.   Is it support multiple connections? (1 node can connect to
> multiple peer nodes with separate SCTP connection)
No, as above, it's a missing feature right now.
> 
>  
> 
> Thank you and looking forward to your response.
> 
>  
> 
> BRs,
> 
> Dong Yao (WWID 11605191)
> 
>  
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#12266): https://lists.fd.io/g/vpp-dev/message/12266
> Mute This Topic: https://lists.fd.io/mt/29859930/675056
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [mvarl...@suse.de]
> -=-=-=-=-=-=-=-=-=-=-=-
> 

-- 
Marco Varlese, Architect Developer Technologies, SUSE Labs
SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg



signature.asc
Description: OpenPGP digital signature
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12273): https://lists.fd.io/g/vpp-dev/message/12273
Mute This Topic: https://lists.fd.io/mt/29859930/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] opensuse15 aka opens use leap15 build failures

[Marco Varlese]

Hi Ed,

On 2/14/19 6:53 PM, Ed Kern via Lists.Fd.Io wrote:
> 
> 
> Due to a upstream version reporting change we saw some build failures on 
> osleap15 verify jobs.
Can you please highlight what has changed so that I can look into that
and/or report a bug about it?

> 
> Ive hopefully worked around this (again) so those jobs should be back on 
> track.
> 
> Ed
Thanks,
Marco

> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#12263): https://lists.fd.io/g/vpp-dev/message/12263
> Mute This Topic: https://lists.fd.io/mt/29844347/675056
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [mvarl...@suse.de]
> -=-=-=-=-=-=-=-=-=-=-=-
> 

-- 
Marco Varlese | Architect Developer Technologies
SUSE LINUX GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg



signature.asc
Description: OpenPGP digital signature
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12267): https://lists.fd.io/g/vpp-dev/message/12267
Mute This Topic: https://lists.fd.io/mt/29844347/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] opensuse expert needed

[Marco Varlese]

Damjan,

On 1/31/19 12:41 PM, Damjan Marion wrote:
> 
> 
>> On 31 Jan 2019, at 08:57, Marco Varlese > <mailto:mvarl...@suse.de>> wrote:
>>
>> Damjan,
>>
>> On 1/30/19 3:29 PM, Damjan Marion via Lists.Fd.Io wrote:
>>>
>>> Folks,
>>>
>>> Anybody can help with understanding why opensuse jobs are failing with:
>>>
>>> *13:54:57*
>>> /w/workspace/vpp-verify-master-osleap15/build-root/rpmbuild/BUILD/vpp-19.04/src/plugins/nsim/nsim.c:620:1:
>>> fatal error: error writing to /tmp/ccJaw6Cw.s: Cannot allocate memory
>>> *13:54:57*  };
>>> *13:54:57*  ^
>>> *13:54:57* compilation terminated.
>>>
>>>
>>> *13:54:57* gcc-7: internal compiler error: Killed (program cc1)
>>> *13:54:57* Please submit a full bug report,
>>> *13:54:57* with preprocessed source if appropriate.
>>> *13:54:57* See <http://bugs.opensuse.org/> for instructions.
>> This to me looks like an infrastructure issue.
>> If it was a problem with the distro / setup it would have happened all
>> the time whilst things were pretty stable over the past months...
> 
> Well, that line clearly asks for filling bug with opensuse.org
> <http://opensuse.org>...
Sure... that's pretty standard I'd say.

Anyw... I did ask around to some compiler guys and that
looks like an out-of-memory issue (e.g. no more memory left on the node
where the compilation was running)...

> 
>>
>>>
>>>
>>>
>>> Also, how we can avoid in future that people need to deal with this kind
>>> of issues?
>> I am not sure how to answer this question.
>>
>>>
>>> Personally I don't see lot of value in compiling VPP agains every single
>>> distro on the planet in each verify job,
>>> but i'm fine with that as long as things are stable and not PITA for
>>> people trying to get patch verified
>> Are you suggesting to remove openSUSE builds from Jenkins for VPP?
> 
> That is not what I said. I just don't see lot of value of running each
> verify job against 3 distros,
> I believe one is enough, and I'm not suggesting which one is that.
> 
>> Beside, I see verify jobs are passing now. Has anything been done in the
>> meantime or all started to work auto-magically?
> 
> No, centos job was failing after that. but then everything passed.
> it is lottery, whole infra is fragile and more jobs we run makes it
> harder to have winning lottery ticket.
I think it's rather a matter of sizing the running jobs queue to the
actual capacity we have in the back-end. I remember something similar
happened during summer / end-of summer time where jobs were randomly
failing due to infra issues.
Perhaps, another approach (instead of reducing the number of distros)
could be to have only couple of patches building at a time. I would
imagine that could be driven by Jenkins jobs/queues/etc.
In that way, we could try addressing the capacity issue without reducing
distros support.
> 
> -- 
> Damjan
> 
- Marco



signature.asc
Description: OpenPGP digital signature
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12091): https://lists.fd.io/g/vpp-dev/message/12091
Mute This Topic: https://lists.fd.io/mt/29594604/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] opensuse expert needed

[Marco Varlese]

Damjan,

On 1/30/19 3:29 PM, Damjan Marion via Lists.Fd.Io wrote:
> 
> Folks,
> 
> Anybody can help with understanding why opensuse jobs are failing with:
> 
> *13:54:57* 
> /w/workspace/vpp-verify-master-osleap15/build-root/rpmbuild/BUILD/vpp-19.04/src/plugins/nsim/nsim.c:620:1:
>  fatal error: error writing to /tmp/ccJaw6Cw.s: Cannot allocate memory
> *13:54:57*  };
> *13:54:57*  ^
> *13:54:57* compilation terminated.
> 
> 
> *13:54:57* gcc-7: internal compiler error: Killed (program cc1)
> *13:54:57* Please submit a full bug report,
> *13:54:57* with preprocessed source if appropriate.
> *13:54:57* See <http://bugs.opensuse.org/> for instructions.
This to me looks like an infrastructure issue.
If it was a problem with the distro / setup it would have happened all
the time whilst things were pretty stable over the past months...

> 
> 
> 
> Also, how we can avoid in future that people need to deal with this kind
> of issues?
I am not sure how to answer this question.

> 
> Personally I don't see lot of value in compiling VPP agains every single
> distro on the planet in each verify job,
> but i'm fine with that as long as things are stable and not PITA for
> people trying to get patch verified
Are you suggesting to remove openSUSE builds from Jenkins for VPP?

Beside, I see verify jobs are passing now. Has anything been done in the
meantime or all started to work auto-magically?

> 
> -- 
> Damjan
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#12062): https://lists.fd.io/g/vpp-dev/message/12062
> Mute This Topic: https://lists.fd.io/mt/29594604/675056
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [mvarl...@suse.de]
> -=-=-=-=-=-=-=-=-=-=-=-
> 

-- 
Marco Varlese, Architect Developer Technologies, SUSE Labs
SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg



signature.asc
Description: OpenPGP digital signature
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12087): https://lists.fd.io/g/vpp-dev/message/12087
Mute This Topic: https://lists.fd.io/mt/29594604/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] How do I get the "dpdk-shared" in VPP ?

[Marco Varlese]

On 1/29/19 1:51 PM, Damjan Marion via Lists.Fd.Io wrote:
> 
> As discussed on the last community call, japi is now new fd.io
> <http://fd.io> project and will be in separate repo...
Thanks!

> 
> 
>> On 29 Jan 2019, at 13:10, Marco Varlese > <mailto:mvarl...@suse.de>> wrote:
>>
>> How does the new build-system build the japi (e.g. JAR)?
>> I can't get them to build...
>>
>>
>> On 1/28/19 5:57 PM, Damjan Marion via Lists.Fd.Io wrote:
>>>
>>> With this change, I'm able to compile VPP out of tarball produced by
>>> "make dist".
>>>
>>> https://gerrit.fd.io/r/#/c/17125/
>>>
>>>
>>>> On 28 Jan 2019, at 13:35, Damjan Marion via Lists.Fd.Io
>>>> >>> <mailto:dmarion=me@lists.fd.io> <mailto:dmarion=me@lists.fd.io>>
>>>> wrote:
>>>>
>>>>
>>>>
>>>>> On 28 Jan 2019, at 12:08, Marco Varlese >>>> <mailto:mvarl...@suse.de>
>>>>> <mailto:mvarl...@suse.de>> wrote:
>>>>>
>>>>> Is there still a way to use the old infrastructure to build the code?
>>>>
>>>> No, that doesn't make sense.
>>>>
>>>>>
>>>>> Apparently, cmake works when used inside the GIT repo but fails to
>>>>> build
>>>>> when using the tarball generated via "make dist" (required indeed for
>>>>> downstream consumption).
>>>>
>>>> that should be easy fixable
>>>>
>>>>>
>>>>> On 1/26/19 2:22 PM, Damjan Marion via Lists.Fd.Io wrote:
>>>>>>
>>>>>> Here it is: https://gerrit.fd.io/r/17094
>>>>>>
>>>>>>
>>>>>> $ mkdir build-vpp stage
>>>>>>
>>>>>> $ git clone 
>>>>>>
>>>>>> $ cd dpdk
>>>>>>
>>>>>> $ cat << _EOF_ | patch -p1
>>>>>> diff --git a/config/common_base b/config/common_base
>>>>>> index d12ae98bc..42d6f53dd 100644
>>>>>> --- a/config/common_base
>>>>>> +++ b/config/common_base
>>>>>> @@ -38,7 +38,7 @@ CONFIG_RTE_ARCH_STRICT_ALIGN=n
>>>>>>  #
>>>>>>  # Compile to share library
>>>>>>  #
>>>>>> -CONFIG_RTE_BUILD_SHARED_LIB=n
>>>>>> +CONFIG_RTE_BUILD_SHARED_LIB=y
>>>>>>
>>>>>>  #
>>>>>>  # Use newest code breaking previous ABI
>>>>>> _EOF_
>>>>>>
>>>>>>
>>>>>> $ make -j install T=x86_64-native-linuxapp-gcc DESTDIR=../stage
>>>>>>
>>>>>> $ cd ../build-vpp
>>>>>>
>>>>>> $ cmake -G Ninja -DCMAKE_PREFIX_PATH:PATH=$PWD/../stage
>>>>>> /path/to/vpp/src
>>>>>>
>>>>>> $ ninja
>>>>>>
>>>>>> $ LD_LIBRARY_PATH=../stage/lib ldd lib/vpp_plugins/dpdk_plugin.so
>>>>>> linux-vdso.so.1 (0x7ffe2a3b7000)
>>>>>> librte_cryptodev.so.5.1 => ../stage/lib/librte_cryptodev.so.5.1
>>>>>> (0x7fd5e1fa)
>>>>>> librte_eal.so.9.1 => ../stage/lib/librte_eal.so.9.1
>>>>>> (0x7fd5e1ed1000)
>>>>>> librte_ethdev.so.11.1 => ../stage/lib/librte_ethdev.so.11.1
>>>>>> (0x7fd5e1e3)
>>>>>> librte_mbuf.so.4.1 => ../stage/lib/librte_mbuf.so.4.1
>>>>>> (0x7fd5e1e28000)
>>>>>> librte_mempool.so.5.1 => ../stage/lib/librte_mempool.so.5.1
>>>>>> (0x7fd5e1e1f000)
>>>>>> librte_pmd_bond.so.2.1 => ../stage/lib/librte_pmd_bond.so.2.1
>>>>>> (0x7fd5e1dfe000)
>>>>>> librte_ring.so.2.1 => ../stage/lib/librte_ring.so.2.1
>>>>>> (0x7fd5e1df9000)
>>>>>> librte_sched.so.1.1 => ../stage/lib/librte_sched.so.1.1
>>>>>> (0x7fd5e1ded000)
>>>>>> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fd5e1be9000)
>>>>>> /lib64/ld-linux-x86-64.so.2 (0x7fd5e211d000)
>>>>>> librte_kvargs.so.1.1 => ../stage/lib/librte_kvargs.so.1.1
>>>>>> (0x7fd5e1be4000)
>>>>>> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fd5e1bdc000)
>>>>>> libpthread.so.0 =&g

Re: [vpp-dev] How do I get the "dpdk-shared" in VPP ?

[Marco Varlese]

Hi Damjan,

On 1/29/19 10:39 AM, Damjan Marion wrote:
> 
> Dear Marco,
> 
> May be that my first explanation was not clear enough.
> 
> (1) In VPP repo we use cmake + (ninja or gnumake) for compiling VPP
> which includes searching for dependencies (different libs like dpdk, openssl, 
> uuid).
> To compile VPP everything you need is in src/ directory.
> If cmake is not able to find some dependencies like DPDK, it will warn
> you and disable that compolnent (i.e. DPDK plugin).
> 
> (2) Then we have our build environment crafted out of different Makefiles,
> which is there mainly to support developers and for our internal packaging.
> What those sets of makefiles are doing is:
>  - downloading, compiling (and optionally packaging)  dependencies like dpdk, 
> ipsecmb, nasm
>  - compiling VPP by passing right arguments to (1) so cmake is able to find 
> libraries at the right place
> 
> If you are working on disto packaging, specially if you are linking against
> distro version of libraries like DPDK, there is no sense in using (2).
> Just call cmake with right arguments from your .spec file following
> by "cmake --build" similar to majority of open source projects.
> Simply forget about anything in build-root/ build-data/ or build/
> directories. They are all part of (2).
I managed to get a new .spec in place...
Many paths have changed so it was quite a bit of refactoring.
I'm just struggling right now to have the good, old JAR files built...
are they still available or no longer built?
> 
> Hope this explains,
It definitely helps! Thanks Damjan.

Cheers,
Marco
> 
> 
>> On 29 Jan 2019, at 08:07, Marco Varlese  wrote:
>>
>> Thanks Damjan. I will try that too.
>>
>> A last question: I assume I can keep using the "make -C build-root
>> install-packages" if I pull your last patches. Am I right / wrong?
>>
>>
>> Thanks,
>> Marco
>>
>> On 1/28/19 5:57 PM, Damjan Marion via Lists.Fd.Io wrote:
>>>
>>> With this change, I'm able to compile VPP out of tarball produced by
>>> "make dist".
>>>
>>> https://gerrit.fd.io/r/#/c/17125/
>>>
>>>
>>>> On 28 Jan 2019, at 13:35, Damjan Marion via Lists.Fd.Io
>>>> mailto:dmarion=me@lists.fd.io>> wrote:
>>>>
>>>>
>>>>
>>>>> On 28 Jan 2019, at 12:08, Marco Varlese >>>> <mailto:mvarl...@suse.de>> wrote:
>>>>>
>>>>> Is there still a way to use the old infrastructure to build the code?
>>>>
>>>> No, that doesn't make sense.
>>>>
>>>>>
>>>>> Apparently, cmake works when used inside the GIT repo but fails to build
>>>>> when using the tarball generated via "make dist" (required indeed for
>>>>> downstream consumption).
>>>>
>>>> that should be easy fixable
>>>>
>>>>>
>>>>> On 1/26/19 2:22 PM, Damjan Marion via Lists.Fd.Io wrote:
>>>>>>
>>>>>> Here it is: https://gerrit.fd.io/r/17094
>>>>>>
>>>>>>
>>>>>> $ mkdir build-vpp stage
>>>>>>
>>>>>> $ git clone 
>>>>>>
>>>>>> $ cd dpdk
>>>>>>
>>>>>> $ cat << _EOF_ | patch -p1
>>>>>> diff --git a/config/common_base b/config/common_base
>>>>>> index d12ae98bc..42d6f53dd 100644
>>>>>> --- a/config/common_base
>>>>>> +++ b/config/common_base
>>>>>> @@ -38,7 +38,7 @@ CONFIG_RTE_ARCH_STRICT_ALIGN=n
>>>>>>  #
>>>>>>  # Compile to share library
>>>>>>  #
>>>>>> -CONFIG_RTE_BUILD_SHARED_LIB=n
>>>>>> +CONFIG_RTE_BUILD_SHARED_LIB=y
>>>>>>
>>>>>>  #
>>>>>>  # Use newest code breaking previous ABI
>>>>>> _EOF_
>>>>>>
>>>>>>
>>>>>> $ make -j install T=x86_64-native-linuxapp-gcc DESTDIR=../stage
>>>>>>
>>>>>> $ cd ../build-vpp
>>>>>>
>>>>>> $ cmake -G Ninja -DCMAKE_PREFIX_PATH:PATH=$PWD/../stage /path/to/vpp/src
>>>>>>
>>>>>> $ ninja
>>>>>>
>>>>>> $ LD_LIBRARY_PATH=../stage/lib ldd lib/vpp_plugins/dpdk_plugin.so
>>>>>> linux-vdso.so.1 (0x7ffe2a3b7000)
>>>>>> librte_cryptodev.so.5.1 => ../stage/lib/librte_cryptodev.s

Re: [vpp-dev] How do I get the "dpdk-shared" in VPP ?

[Marco Varlese]

How does the new build-system build the japi (e.g. JAR)?
I can't get them to build...


On 1/28/19 5:57 PM, Damjan Marion via Lists.Fd.Io wrote:
> 
> With this change, I'm able to compile VPP out of tarball produced by
> "make dist".
> 
> https://gerrit.fd.io/r/#/c/17125/
> 
> 
>> On 28 Jan 2019, at 13:35, Damjan Marion via Lists.Fd.Io
>> mailto:dmarion=me@lists.fd.io>> wrote:
>>
>>
>>
>>> On 28 Jan 2019, at 12:08, Marco Varlese >> <mailto:mvarl...@suse.de>> wrote:
>>>
>>> Is there still a way to use the old infrastructure to build the code?
>>
>> No, that doesn't make sense.
>>
>>>
>>> Apparently, cmake works when used inside the GIT repo but fails to build
>>> when using the tarball generated via "make dist" (required indeed for
>>> downstream consumption).
>>
>> that should be easy fixable
>>
>>>
>>> On 1/26/19 2:22 PM, Damjan Marion via Lists.Fd.Io wrote:
>>>>
>>>> Here it is: https://gerrit.fd.io/r/17094
>>>>
>>>>
>>>> $ mkdir build-vpp stage
>>>>
>>>> $ git clone 
>>>>
>>>> $ cd dpdk
>>>>
>>>> $ cat << _EOF_ | patch -p1
>>>> diff --git a/config/common_base b/config/common_base
>>>> index d12ae98bc..42d6f53dd 100644
>>>> --- a/config/common_base
>>>> +++ b/config/common_base
>>>> @@ -38,7 +38,7 @@ CONFIG_RTE_ARCH_STRICT_ALIGN=n
>>>>  #
>>>>  # Compile to share library
>>>>  #
>>>> -CONFIG_RTE_BUILD_SHARED_LIB=n
>>>> +CONFIG_RTE_BUILD_SHARED_LIB=y
>>>>
>>>>  #
>>>>  # Use newest code breaking previous ABI
>>>> _EOF_
>>>>
>>>>
>>>> $ make -j install T=x86_64-native-linuxapp-gcc DESTDIR=../stage
>>>>
>>>> $ cd ../build-vpp
>>>>
>>>> $ cmake -G Ninja -DCMAKE_PREFIX_PATH:PATH=$PWD/../stage /path/to/vpp/src
>>>>
>>>> $ ninja
>>>>
>>>> $ LD_LIBRARY_PATH=../stage/lib ldd lib/vpp_plugins/dpdk_plugin.so
>>>> linux-vdso.so.1 (0x7ffe2a3b7000)
>>>> librte_cryptodev.so.5.1 => ../stage/lib/librte_cryptodev.so.5.1
>>>> (0x7fd5e1fa)
>>>> librte_eal.so.9.1 => ../stage/lib/librte_eal.so.9.1 (0x7fd5e1ed1000)
>>>> librte_ethdev.so.11.1 => ../stage/lib/librte_ethdev.so.11.1
>>>> (0x7fd5e1e3)
>>>> librte_mbuf.so.4.1 => ../stage/lib/librte_mbuf.so.4.1
>>>> (0x7fd5e1e28000)
>>>> librte_mempool.so.5.1 => ../stage/lib/librte_mempool.so.5.1
>>>> (0x7fd5e1e1f000)
>>>> librte_pmd_bond.so.2.1 => ../stage/lib/librte_pmd_bond.so.2.1
>>>> (0x7fd5e1dfe000)
>>>> librte_ring.so.2.1 => ../stage/lib/librte_ring.so.2.1
>>>> (0x7fd5e1df9000)
>>>> librte_sched.so.1.1 => ../stage/lib/librte_sched.so.1.1
>>>> (0x7fd5e1ded000)
>>>> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fd5e1be9000)
>>>> /lib64/ld-linux-x86-64.so.2 (0x7fd5e211d000)
>>>> librte_kvargs.so.1.1 => ../stage/lib/librte_kvargs.so.1.1
>>>> (0x7fd5e1be4000)
>>>> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fd5e1bdc000)
>>>> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
>>>> (0x7fd5e1bbb000)
>>>> librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fd5e1bb1000)
>>>> libnuma.so.1 => /usr/lib/x86_64-linux-gnu/libnuma.so.1
>>>> (0x7fd5e19a6000)
>>>> librte_cmdline.so.2.1 => ../stage/lib/librte_cmdline.so.2.1
>>>> (0x7fd5e199a000)
>>>> librte_pci.so.1.1 => ../stage/lib/librte_pci.so.1.1 (0x7fd5e1993000)
>>>> librte_bus_vdev.so.2.1 => ../stage/lib/librte_bus_vdev.so.2.1
>>>> (0x7fd5e198c000)
>>>> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fd5e17ff000)
>>>>
>>>> -- 
>>>> Damjan
>>>>
>>>>
>>>>
>>>>
>>>>> On 25 Jan 2019, at 18:03, Kinsella, Ray >>>> <mailto:ray.kinse...@intel.com>
>>>>> <mailto:ray.kinse...@intel.com>> wrote:
>>>>>
>>>>> I tried doing this recently and it barfed.
>>>>> How did you get it working?
>>>>>
>>>>> Ray K
>>>>>
>>>>>> -Original Me

Re: [vpp-dev] How do I get the "dpdk-shared" in VPP ?

[Marco Varlese]

Thanks Damjan. I will try that too.

A last question: I assume I can keep using the "make -C build-root
install-packages" if I pull your last patches. Am I right / wrong?


Thanks,
Marco

On 1/28/19 5:57 PM, Damjan Marion via Lists.Fd.Io wrote:
> 
> With this change, I'm able to compile VPP out of tarball produced by
> "make dist".
> 
> https://gerrit.fd.io/r/#/c/17125/
> 
> 
>> On 28 Jan 2019, at 13:35, Damjan Marion via Lists.Fd.Io
>> mailto:dmarion=me@lists.fd.io>> wrote:
>>
>>
>>
>>> On 28 Jan 2019, at 12:08, Marco Varlese >> <mailto:mvarl...@suse.de>> wrote:
>>>
>>> Is there still a way to use the old infrastructure to build the code?
>>
>> No, that doesn't make sense.
>>
>>>
>>> Apparently, cmake works when used inside the GIT repo but fails to build
>>> when using the tarball generated via "make dist" (required indeed for
>>> downstream consumption).
>>
>> that should be easy fixable
>>
>>>
>>> On 1/26/19 2:22 PM, Damjan Marion via Lists.Fd.Io wrote:
>>>>
>>>> Here it is: https://gerrit.fd.io/r/17094
>>>>
>>>>
>>>> $ mkdir build-vpp stage
>>>>
>>>> $ git clone 
>>>>
>>>> $ cd dpdk
>>>>
>>>> $ cat << _EOF_ | patch -p1
>>>> diff --git a/config/common_base b/config/common_base
>>>> index d12ae98bc..42d6f53dd 100644
>>>> --- a/config/common_base
>>>> +++ b/config/common_base
>>>> @@ -38,7 +38,7 @@ CONFIG_RTE_ARCH_STRICT_ALIGN=n
>>>>  #
>>>>  # Compile to share library
>>>>  #
>>>> -CONFIG_RTE_BUILD_SHARED_LIB=n
>>>> +CONFIG_RTE_BUILD_SHARED_LIB=y
>>>>
>>>>  #
>>>>  # Use newest code breaking previous ABI
>>>> _EOF_
>>>>
>>>>
>>>> $ make -j install T=x86_64-native-linuxapp-gcc DESTDIR=../stage
>>>>
>>>> $ cd ../build-vpp
>>>>
>>>> $ cmake -G Ninja -DCMAKE_PREFIX_PATH:PATH=$PWD/../stage /path/to/vpp/src
>>>>
>>>> $ ninja
>>>>
>>>> $ LD_LIBRARY_PATH=../stage/lib ldd lib/vpp_plugins/dpdk_plugin.so
>>>> linux-vdso.so.1 (0x7ffe2a3b7000)
>>>> librte_cryptodev.so.5.1 => ../stage/lib/librte_cryptodev.so.5.1
>>>> (0x7fd5e1fa)
>>>> librte_eal.so.9.1 => ../stage/lib/librte_eal.so.9.1 (0x7fd5e1ed1000)
>>>> librte_ethdev.so.11.1 => ../stage/lib/librte_ethdev.so.11.1
>>>> (0x7fd5e1e3)
>>>> librte_mbuf.so.4.1 => ../stage/lib/librte_mbuf.so.4.1
>>>> (0x7fd5e1e28000)
>>>> librte_mempool.so.5.1 => ../stage/lib/librte_mempool.so.5.1
>>>> (0x7fd5e1e1f000)
>>>> librte_pmd_bond.so.2.1 => ../stage/lib/librte_pmd_bond.so.2.1
>>>> (0x7fd5e1dfe000)
>>>> librte_ring.so.2.1 => ../stage/lib/librte_ring.so.2.1
>>>> (0x7fd5e1df9000)
>>>> librte_sched.so.1.1 => ../stage/lib/librte_sched.so.1.1
>>>> (0x7fd5e1ded000)
>>>> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fd5e1be9000)
>>>> /lib64/ld-linux-x86-64.so.2 (0x7fd5e211d000)
>>>> librte_kvargs.so.1.1 => ../stage/lib/librte_kvargs.so.1.1
>>>> (0x7fd5e1be4000)
>>>> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fd5e1bdc000)
>>>> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
>>>> (0x7fd5e1bbb000)
>>>> librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fd5e1bb1000)
>>>> libnuma.so.1 => /usr/lib/x86_64-linux-gnu/libnuma.so.1
>>>> (0x7fd5e19a6000)
>>>> librte_cmdline.so.2.1 => ../stage/lib/librte_cmdline.so.2.1
>>>> (0x7fd5e199a000)
>>>> librte_pci.so.1.1 => ../stage/lib/librte_pci.so.1.1 (0x7fd5e1993000)
>>>> librte_bus_vdev.so.2.1 => ../stage/lib/librte_bus_vdev.so.2.1
>>>> (0x7fd5e198c000)
>>>> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fd5e17ff000)
>>>>
>>>> -- 
>>>> Damjan
>>>>
>>>>
>>>>
>>>>
>>>>> On 25 Jan 2019, at 18:03, Kinsella, Ray >>>> <mailto:ray.kinse...@intel.com>
>>>>> <mailto:ray.kinse...@intel.com>> wrote:
>>>>>
>>>>> I tried doing this recently and it barfed.
>>>>> How did you 

Re: [vpp-dev] How do I get the "dpdk-shared" in VPP ?

[Marco Varlese]

Is there still a way to use the old infrastructure to build the code?

Apparently, cmake works when used inside the GIT repo but fails to build
when using the tarball generated via "make dist" (required indeed for
downstream consumption).

On 1/26/19 2:22 PM, Damjan Marion via Lists.Fd.Io wrote:
> 
> Here it is: https://gerrit.fd.io/r/17094
> 
> 
> $ mkdir build-vpp stage
> 
> $ git clone 
> 
> $ cd dpdk
> 
> $ cat << _EOF_ | patch -p1
> diff --git a/config/common_base b/config/common_base
> index d12ae98bc..42d6f53dd 100644
> --- a/config/common_base
> +++ b/config/common_base
> @@ -38,7 +38,7 @@ CONFIG_RTE_ARCH_STRICT_ALIGN=n
>  #
>  # Compile to share library
>  #
> -CONFIG_RTE_BUILD_SHARED_LIB=n
> +CONFIG_RTE_BUILD_SHARED_LIB=y
> 
>  #
>  # Use newest code breaking previous ABI
> _EOF_
> 
> 
> $ make -j install T=x86_64-native-linuxapp-gcc DESTDIR=../stage
> 
> $ cd ../build-vpp
> 
> $ cmake -G Ninja -DCMAKE_PREFIX_PATH:PATH=$PWD/../stage /path/to/vpp/src
> 
> $ ninja
> 
> $ LD_LIBRARY_PATH=../stage/lib ldd lib/vpp_plugins/dpdk_plugin.so
> linux-vdso.so.1 (0x7ffe2a3b7000)
> librte_cryptodev.so.5.1 => ../stage/lib/librte_cryptodev.so.5.1
> (0x7fd5e1fa)
> librte_eal.so.9.1 => ../stage/lib/librte_eal.so.9.1 (0x7fd5e1ed1000)
> librte_ethdev.so.11.1 => ../stage/lib/librte_ethdev.so.11.1
> (0x7fd5e1e3)
> librte_mbuf.so.4.1 => ../stage/lib/librte_mbuf.so.4.1 (0x7fd5e1e28000)
> librte_mempool.so.5.1 => ../stage/lib/librte_mempool.so.5.1
> (0x7fd5e1e1f000)
> librte_pmd_bond.so.2.1 => ../stage/lib/librte_pmd_bond.so.2.1
> (0x7fd5e1dfe000)
> librte_ring.so.2.1 => ../stage/lib/librte_ring.so.2.1 (0x7fd5e1df9000)
> librte_sched.so.1.1 => ../stage/lib/librte_sched.so.1.1 (0x7fd5e1ded000)
> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fd5e1be9000)
> /lib64/ld-linux-x86-64.so.2 (0x7fd5e211d000)
> librte_kvargs.so.1.1 => ../stage/lib/librte_kvargs.so.1.1
> (0x7fd5e1be4000)
> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fd5e1bdc000)
> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
> (0x7fd5e1bbb000)
> librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fd5e1bb1000)
> libnuma.so.1 => /usr/lib/x86_64-linux-gnu/libnuma.so.1 (0x7fd5e19a6000)
> librte_cmdline.so.2.1 => ../stage/lib/librte_cmdline.so.2.1
> (0x7fd5e199a000)
> librte_pci.so.1.1 => ../stage/lib/librte_pci.so.1.1 (0x7fd5e1993000)
> librte_bus_vdev.so.2.1 => ../stage/lib/librte_bus_vdev.so.2.1
> (0x7fd5e198c000)
> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fd5e17ff000)
> 
> -- 
> Damjan
> 
> 
> 
> 
>> On 25 Jan 2019, at 18:03, Kinsella, Ray > <mailto:ray.kinse...@intel.com>> wrote:
>>
>> I tried doing this recently and it barfed.
>> How did you get it working?
>>
>> Ray K
>>
>>> -Original Message-
>>> From: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io>
>>> [mailto:vpp-dev@lists.fd.io] On Behalf Of Marco
>>> Varlese
>>> Sent: Friday 25 January 2019 12:38
>>> To: Damjan Marion mailto:dmar...@me.com>>
>>> Cc: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io>
>>> Subject: Re: [vpp-dev] How do I get the "dpdk-shared" in VPP ?
>>>
>>> Never mind... I did find the issue. All good ;)
>>>
>>> Thank you Damjan!!!
>>>
>>> On 1/25/19 1:26 PM, Marco Varlese wrote:
>>>>
>>>>
>>>> On 1/25/19 11:14 AM, Damjan Marion wrote:
>>>>>
>>>>>
>>>>>> On 25 Jan 2019, at 10:49, Marco Varlese >>>>> <mailto:mvarl...@suse.de>
>>>>>> <mailto:mvarl...@suse.de>> wrote:
>>>>>>
>>>>>> Hi Damjan,
>>>>>>
>>>>>> On 1/24/19 10:46 PM, Damjan Marion via Lists.Fd.Io wrote:
>>>>>>>
>>>>>>> In theory like any other cmake project:
>>>>>>>
>>>>>>> $ mkdir build
>>>>>>> $ cd build
>>>>>>> $ cmake /path/to/vpp/src  $ make $ make install
>>>>>> Hmmm, not sure if I explained myself in the right way.
>>>>>>
>>>>>> The problem today is that I cannot find a way to tell VPP _not_ to
>>>>>> download the dpdk tarball, uncompress it, build it and then link
>>>>>> against it...
>>>>>
>>>>> That is exactly what I described above
>>>>>
>>>>>&

Re: [vpp-dev] How do I get the "dpdk-shared" in VPP ?

[Marco Varlese]

Never mind... I did find the issue. All good ;)

Thank you Damjan!!!

On 1/25/19 1:26 PM, Marco Varlese wrote:
> 
> 
> On 1/25/19 11:14 AM, Damjan Marion wrote:
>>
>>
>>> On 25 Jan 2019, at 10:49, Marco Varlese >> <mailto:mvarl...@suse.de>> wrote:
>>>
>>> Hi Damjan,
>>>
>>> On 1/24/19 10:46 PM, Damjan Marion via Lists.Fd.Io wrote:
>>>>
>>>> In theory like any other cmake project:
>>>>
>>>> $ mkdir build
>>>> $ cd build
>>>> $ cmake /path/to/vpp/src 
>>>> $ make
>>>> $ make install
>>> Hmmm, not sure if I explained myself in the right way.
>>>
>>> The problem today is that I cannot find a way to tell VPP _not_ to
>>> download the dpdk tarball, uncompress it, build it and then link against
>>> it...
>>
>> That is exactly what I described above
>>
>>>
>>> How does the above help in that regard?
>>
>> It helps as cmake doesn't download dpdk or other libs. It is downloaded
>> by bunch of makefiles outside of src/.
>> If you don't need such service from those Makefiles, don''t use them..
> OK, so I did try your suggestion but in that case the DPDK plugin
> doesn't get built at all and the build procedure doesn't even get to the
> point of looking for a DPDK library (whether statically or dynamically
> linked).
>>
>>>
>>>>
>>>> In practice probably few lines should be modified in
>>>> src/plugins/dodkCMakeLists.txt to enable linking with shared libs, as
>>>> today we do static...
>>> So the shared-lib support was removed when moving to cmake I suppose.
>>> Was that intentional or just a miss?
>>
>> it was intentional miss :)
>>
>> -- 
>> Damjan
>>
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#12008): https://lists.fd.io/g/vpp-dev/message/12008
> Mute This Topic: https://lists.fd.io/mt/29529767/675056
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [mvarl...@suse.de]
> -=-=-=-=-=-=-=-=-=-=-=-
> 

-- 
Marco Varlese, Architect Developer Technologies, SUSE Labs
SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg



signature.asc
Description: OpenPGP digital signature
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12009): https://lists.fd.io/g/vpp-dev/message/12009
Mute This Topic: https://lists.fd.io/mt/29529767/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] How do I get the "dpdk-shared" in VPP ?

[Marco Varlese]

On 1/25/19 11:14 AM, Damjan Marion wrote:
> 
> 
>> On 25 Jan 2019, at 10:49, Marco Varlese > <mailto:mvarl...@suse.de>> wrote:
>>
>> Hi Damjan,
>>
>> On 1/24/19 10:46 PM, Damjan Marion via Lists.Fd.Io wrote:
>>>
>>> In theory like any other cmake project:
>>>
>>> $ mkdir build
>>> $ cd build
>>> $ cmake /path/to/vpp/src 
>>> $ make
>>> $ make install
>> Hmmm, not sure if I explained myself in the right way.
>>
>> The problem today is that I cannot find a way to tell VPP _not_ to
>> download the dpdk tarball, uncompress it, build it and then link against
>> it...
> 
> That is exactly what I described above
> 
>>
>> How does the above help in that regard?
> 
> It helps as cmake doesn't download dpdk or other libs. It is downloaded
> by bunch of makefiles outside of src/.
> If you don't need such service from those Makefiles, don''t use them..
OK, so I did try your suggestion but in that case the DPDK plugin
doesn't get built at all and the build procedure doesn't even get to the
point of looking for a DPDK library (whether statically or dynamically
linked).
> 
>>
>>>
>>> In practice probably few lines should be modified in
>>> src/plugins/dodkCMakeLists.txt to enable linking with shared libs, as
>>> today we do static...
>> So the shared-lib support was removed when moving to cmake I suppose.
>> Was that intentional or just a miss?
> 
> it was intentional miss :)
> 
> -- 
> Damjan
> 

-- 
Marco Varlese, Architect Developer Technologies, SUSE Labs
SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg



signature.asc
Description: OpenPGP digital signature
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12008): https://lists.fd.io/g/vpp-dev/message/12008
Mute This Topic: https://lists.fd.io/mt/29529767/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] How do I get the "dpdk-shared" in VPP ?

[Marco Varlese]

Hi Damjan,

On 1/24/19 10:46 PM, Damjan Marion via Lists.Fd.Io wrote:
> 
> In theory like any other cmake project:
> 
> $ mkdir build
> $ cd build
> $ cmake /path/to/vpp/src 
> $ make
> $ make install
Hmmm, not sure if I explained myself in the right way.

The problem today is that I cannot find a way to tell VPP _not_ to
download the dpdk tarball, uncompress it, build it and then link against
it...

How does the above help in that regard?

> 
> In practice probably few lines should be modified in 
> src/plugins/dodkCMakeLists.txt to enable linking with shared libs, as today 
> we do static...
So the shared-lib support was removed when moving to cmake I suppose.
Was that intentional or just a miss?

> 
> — 
> Damjan
Cheers,
Marco

> 
>> On Jan 24, 2019, at 9:15 PM, Marco Varlese  wrote:
>>
>> Hi Damjan and all,
>>
>> How do I get VPP master and / or 19.01-rcX to build against a DPDK
>> already on my system?
>>
>> I am basically talking about the previously available feature driven via
>> vpp.mk as per below snippet:
>>vpp_uses_external_dpdk = yes
>>vpp_dpdk_inc_dir = /usr/include/dpdk
>>vpp_dpdk_lib_dir = /usr/lib
>>vpp_dpdk_shared_lib = yes
>>
>> I can't find how right now...
>>
>>
>> Thanks in advance,
>>
>> Marco
>>
>> -- 
>> Marco Varlese, Architect Developer Technologies, SUSE Labs
>> SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
>> HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
>>
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>>
>> View/Reply Online (#11995): https://lists.fd.io/g/vpp-dev/message/11995
>> Mute This Topic: https://lists.fd.io/mt/29529767/675642
>> Group Owner: vpp-dev+ow...@lists.fd.io
>> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [dmar...@me.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#11997): https://lists.fd.io/g/vpp-dev/message/11997
> Mute This Topic: https://lists.fd.io/mt/29529767/675056
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [mvarl...@suse.de]
> -=-=-=-=-=-=-=-=-=-=-=-
> 

-- 
Marco Varlese, Architect Developer Technologies, SUSE Labs
SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg



signature.asc
Description: OpenPGP digital signature
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12003): https://lists.fd.io/g/vpp-dev/message/12003
Mute This Topic: https://lists.fd.io/mt/29529767/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] How do I get the "dpdk-shared" in VPP ?

[Marco Varlese]

Hi Damjan and all,

How do I get VPP master and / or 19.01-rcX to build against a DPDK
already on my system?

I am basically talking about the previously available feature driven via
vpp.mk as per below snippet:
   vpp_uses_external_dpdk = yes
   vpp_dpdk_inc_dir = /usr/include/dpdk
   vpp_dpdk_lib_dir = /usr/lib
   vpp_dpdk_shared_lib = yes

I can't find how right now...


Thanks in advance,

Marco

-- 
Marco Varlese, Architect Developer Technologies, SUSE Labs
SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg




signature.asc
Description: OpenPGP digital signature
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11995): https://lists.fd.io/g/vpp-dev/message/11995
Mute This Topic: https://lists.fd.io/mt/29529767/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] wireshark vpp dispatch trace dissector merged

[Marco Varlese]

That's great !!!

On Thu, 2019-01-17 at 13:11 +, Dave Barach via Lists.Fd.Io wrote:
> 
> 
> I’m pleased to announce that our dispatch trace wireshark dissector has been
> merged. At some point in the indefinite future, everyone’s favorite distro
> will include a copy of wireshark which knows
>  how to dissect vpp dispatch trace pcap files.
>  
> I’ll update the docs accordingly.
>  
> Dave
>  
> 
> 
> From: bugzilla-dae...@wireshark.org 
> 
> 
> Sent: Thursday, January 17, 2019 6:32 AM
> 
> To: wiresh...@barachs.net
> 
> Subject: [Bug 15411] [dissector] Add dissector for vector packet processing
> dispatch traces
> 
> 
>  
> 
> Comment
>  # 2 on 
> bug 15411 from Gerrit Code Review
> 
> Change 31466 merged by Anders Broman:
> VPP: add vpp graph dispatch trace dissector
>  
> https://code.wireshark.org/review/31466
> 
> 
> 
> 
> You are receiving this mail because:
> 
> 
> 
> You reported the bug.
> You are the assignee for the bug.
> 
> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-Links: You receive all messages sent to this group.
> View/Reply Online (#11939): https://lists.fd.io/g/vpp-dev/message/11939
> Mute This Topic: https://lists.fd.io/mt/29172119/675056
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [mvarl...@suse.de]-=-=-=-=-
> =-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11948): https://lists.fd.io/g/vpp-dev/message/11948
Mute This Topic: https://lists.fd.io/mt/29172119/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Build/rebuild problems (adding dpdk support)

[Marco Varlese]

Hi Brian,
On Mon, 2018-12-17 at 20:19 -0800, Brian Dickson wrote:
> Hi, VPP folks,
> I am trying to add in support for a new card/driver.
> 
> The info on the DPDK website says the drivers I have should work fine.
> 
> Thus, the only issue is adding in the correct manufacturer/device IDs into the
> init.c file:
> 
> 
> 
> 
> 
> 
> src/plugins/dpdk/device/init.c
> 
> I edit the file (one-line change), put it back into the .tar.xz file, put it
> where it should be being picked up (in build-root or so I believe), and it
> gets blown away.
> 
> 
> It always seems to want to pull everything from git regardless of the presence
> of the right tar.xz file in build-root, pointed to by the vpp-latest symbolic
> link.
> 
> 
> I am using "make pkg-rpm" as the command to rebuild things from the main vpp
> source root (parent of build-root).
> 
> 
> What am I doing wrong?
> 
> 
> Where should I be rebuilding this? 
If it's something that small I would suggest to follow the same approach used
today: add a patch to the VPP repo to patch DPDK tarball after it has been
downloaded.See under "/build/external/patches/" there are various sub-folders
for the different DPDK versions.The file build/external/packages.mk already
takes care of navigating the various directories to apply the patch files so
it's a matter of having the new patch in the directory as mentioned above.Now, I
am not sure whether your patch is already on its ways to DPDK upstream but it
would be really a good idea to do that.
> What command should I use? 
> Or what make target?
> In what directory?
I suppose all the three questions above are answered in the 1st point.
> Thanks in advance.
> 
> 
> Brian
Best,Marco
> P.S. I already spent a lot of time chasing a red herring. Does someone want to
> explain to me the purpose of the "sed -e s/-/_/" in extras/rpm/Makefile, full
> line:
> > 
> > 
> > 
> > 
> > RELEASE=$(shell echo $(BASENAME) | cut -f3- -d- | sed -e s/-/_/g)
> 
> It seems really out of place, and leads to lots of difficulty in tracking down
> the place where something that looks like "foo-bar-blech" becomes "foo-
> bar_blech", for no obvious reason. 
> 
> -=-=-=-=-=-=-=-=-=-=-=-Links: You receive all messages sent to this group.
> View/Reply Online (#11641): https://lists.fd.io/g/vpp-dev/message/11641
> Mute This Topic: https://lists.fd.io/mt/28789545/675056
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [mvarl...@suse.de]-=-=-=-=-
> =-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11649): https://lists.fd.io/g/vpp-dev/message/11649
Mute This Topic: https://lists.fd.io/mt/28789545/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Issue with vpp on Cloud Ubuntu Xenial VM (openstack, KVM)

[Marco Varlese]

On Sat, 2018-12-01 at 22:51 +0530, Amit Surana wrote:
> Hi Marcos,
> Many thanks for your help, I have got it working now.
My pleasure; that's great to hear!!!
> Regards
> Amit Surana
> On Sat, 1 Dec 2018, 11:09 Amit Surana  > Thanks Marco. yes that seems to be the issue as vpp crash file too indicates
> > same.Please find /cat/proc for Guest CPU, it does not have support for SSE4.
> > processor   : 1
> > vendor_id   : AuthenticAMD
> > cpu family  : 6
> > model   : 6
> > model name  : QEMU Virtual CPU version 2.5+
> > stepping: 3
> > cpu MHz : 2299.923
> > cache size  : 512 KB
> > physical id : 1
> > siblings: 1
> > core id : 0
> > cpu cores   : 1
> > apicid  : 1
> > initial apicid  : 1
> > fpu : yes
> > fpu_exception   : yes
> > cpuid level : 13
> > wp  : yes
> > flags   : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
> > pat pse36 clflush mmx fxsr sse sse2 syscall nx lm nopl cpuid pni cx16
> > hypervisor lahf_lm svm 3dnowprefetch vmmcall
> > bugs: fxsave_leak sysret_ss_attrs spectre_v1 spectre_v2
> > spec_store_bypass
> > bogomips: 0.22
> > TLB size: 1024 4K pages
> > clflush size: 64
> > cache_alignment : 64
> > address sizes   : 40 bits physical, 48 bits virtual
> > VPP crash output-Program terminated with signal SIGILL, Illegal instruction.
> > #0  0x7f157f37215c in _mm_set_epi8 (__q00=,
> > __q01=, __q02=, __q03=,
> > __q04=, __q05=, __q06=,
> > __q07=, __q08=, __q09=,
> > __q10=, __q11=, __q12=,
> > __q13=, __q14=, __q15=)
> > at /usr/lib/gcc/x86_64-linux-gnu/7/include/emmintrin.h:620
> > My Host does have SSE4 support, its not reflecting in Guest due to Nova
> > setting.I'm using devstack, so need to check best way to change it. 
> > RegardsAmit Surana
> > 
> > 
> > On Fri, Nov 30, 2018 at 6:54 PM Marco Varlese  wrote:
> > > I think you're CPU doesn't support SSE4/AVX instructions...
> > > Can you try to paste here the content of the "flags" parameters in the
> > > output of "cat /proc/cpuinfo"
> > > 
> > > - Marco
> > > On Fri, 2018-11-30 at 16:00 +0530, Amit Surana wrote:
> > > > Hi Team,
> > > > Please can you help me with following issue.
> > > > I'm trying to run VPP on Ubuntu Xenial VM (2 vCPU, 4 GB) in
> > > > Openstack/KVM.
> > > >  After installation vppctl fails with
> > > > following:$vppctlERROR:clib_socket_init: connect (fd 3,
> > > > '/run/vpp/cli.sock'): No such file or directory
> > > > 
> > > > Thread for Similar issue-I checked following
> > > > https://lists.fd.io/g/vpp-dev/topic/running_vpp_failed/16298572?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,20,16298572
> > > > 
> > > > But Resolution is not applicable for my settings.
> > > > 
> > > > 
> > > > 
> > > > Journalctl has following :
> > > > 
> > > > 
> > > > 
> > > > Nov 29 11:52:14 ubuntuxenial vpp[26827]:
> > > > vlib_plugin_early_init:359: plugin path /usr/lib/vpp_plugins
> > > > 
> > > > Nov 29 11:52:14 ubuntuxenial kernel: traps: vpp[26827] trap
> > > > invalid opcode ip:7f62ce450b9e sp:7ffe696c3c20 error:0 in
> > > > libvppinfra.so.0.0.0[7f62ce3f+7c000]
> > > > 
> > > > Nov 29 11:52:18 ubuntuxenial systemd[1]: vpp.service: Main
> > > > process exited, code=dumped, status=4/ILL
> > > > 
> > > > Nov 29 11:52:18 ubuntuxenial systemd[1]: vpp.service: Unit
> > > > entered failed state.
> > > > 
> > > > Nov 29 11:52:18 ubuntuxenial systemd[1]: vpp.service: Failed
> > > > with result 'core-dump'.
> > > > Please note I've used instruction as per 
> > > > 
> > > > 
> > > > https://github.com/cncf/cnfs/tree/master/comparison/box-by-box-kvm-docker
> > > > -
> > > > 
> > > > 
> > > > export UBUNTU="xenial"
> > > >   export RELEASE=".stable.1804"
> > > >   rm /etc/apt/sources.list.d/99fd.io.list
> > > >   echo "deb [trusted=yes] 
> > > > https://nexus.fd.io/content/repositories/fd.io.ubuntu.$UBUNTU.main/ ./"
> > > > | tee -a /etc/apt/sources.list.d/99fd.io.list
> > > >   sudo apt-get update
&

Re: [vpp-dev] Issue with vpp on Cloud Ubuntu Xenial VM (openstack, KVM)

[Marco Varlese]

I think you're CPU doesn't support SSE4/AVX instructions...
Can you try to paste here the content of the "flags" parameters in the output of
"cat /proc/cpuinfo"
- Marco
On Fri, 2018-11-30 at 16:00 +0530, Amit Surana wrote:
> Hi Team,
> Please can you help me with following issue.
> I'm trying to run VPP on Ubuntu Xenial VM (2 vCPU, 4 GB) in Openstack/KVM.
>  After installation vppctl fails with following:$vppctlERROR:clib_socket_init:
> connect (fd 3, '/run/vpp/cli.sock'): No such file or directory
> 
> Thread for Similar issue-I checked following
> https://lists.fd.io/g/vpp-dev/topic/running_vpp_failed/16298572?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,20,16298572
> 
> But Resolution is not applicable for my settings.
> 
> 
> 
> Journalctl has following :
> 
> 
> 
> Nov 29 11:52:14 ubuntuxenial vpp[26827]:
> vlib_plugin_early_init:359: plugin path /usr/lib/vpp_plugins
> 
> Nov 29 11:52:14 ubuntuxenial kernel: traps: vpp[26827] trap
> invalid opcode ip:7f62ce450b9e sp:7ffe696c3c20 error:0 in
> libvppinfra.so.0.0.0[7f62ce3f+7c000]
> 
> Nov 29 11:52:18 ubuntuxenial systemd[1]: vpp.service: Main
> process exited, code=dumped, status=4/ILL
> 
> Nov 29 11:52:18 ubuntuxenial systemd[1]: vpp.service: Unit
> entered failed state.
> 
> Nov 29 11:52:18 ubuntuxenial systemd[1]: vpp.service: Failed
> with result 'core-dump'.
> Please note I've used instruction as per 
> 
> 
> https://github.com/cncf/cnfs/tree/master/comparison/box-by-box-kvm-docker -
> 
> 
> export UBUNTU="xenial"
>   export RELEASE=".stable.1804"
>   rm /etc/apt/sources.list.d/99fd.io.list
>   echo "deb [trusted=yes] 
> https://nexus.fd.io/content/repositories/fd.io.ubuntu.$UBUNTU.main/ ./" | tee
> -a /etc/apt/sources.list.d/99fd.io.list
>   sudo apt-get update
>   apt-get install vpp vpp-lib vpp-plugins vpp-dbg vpp-dev vpp-api-java vpp-
> api-python vpp-api-lua
> 
> 
> 
> I've tried to run it on Ubuntu Bionic cloud image but facing same issue.
> 
> 
> Regards
> Amit Surana
> 
> 
> 
> 
> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-Links: You receive all messages sent to this group.
> View/Reply Online (#11468): https://lists.fd.io/g/vpp-dev/message/11468
> Mute This Topic: https://lists.fd.io/mt/28508443/675056
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [mvarl...@suse.de]-=-=-=-=-
> =-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11469): https://lists.fd.io/g/vpp-dev/message/11469
Mute This Topic: https://lists.fd.io/mt/28508443/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: 答复: 答复: [vpp-dev] about sctp

[Marco Varlese]

On Fri, 2018-11-23 at 00:57 +, Liu Daolin (刘道林) wrote:
> Hi Macro,
>  
> OK, I will try it when I have time.
Well, as you wish.

> 
> I'm reading the sctp source code and found some issues. The most critical one
> is the checksum. The sctp checksum should not include the ip header, just only
> sctp data, and also it should use crc32c, not the current code shown. 
I am not sure what you refer to with "code shown". 
However the crc calculated is indeed the one you mention and it's using SSE4
instructions which are exactly using the polynomial depicted by RFC 4960.

> Another important issue is the max cookie length is 20 from the macro
> definition. Actually it should not be a fixed value (usually more than 200).
So I cannot find a definition for the actual length of the cookie.
It would help if you could point to the actual filename / definition when
reporting issues.

>  
>  
> Best regards
> 刘道林 (Daolin Liu)
> T大连市共进科技有限公司
> DALIAN GONGJIN TECHNOLOGY CO.,LTD
> 中国大连市高新园区软件园路1A-4-24层
> Floor 24th, 1A-4 Software Park Road, Hi-tech Zone, Dalian, Liaoning, China
> 直线(TEL)：(86-411)39996705   分机(EXT)：76824
> 手机(Mobile)：(86)13704090959
>  
> 发件人: Marco Varlese [mailto:mvarl...@suse.de] 
> 发送时间: 2018年11月22日 20:52
> 收件人: Liu Daolin (刘道林); vpp-dev@lists.fd.io
> 主题: Re: 答复: [vpp-dev] about sctp
>  
> Dear Liu,
>  
> The reason why I asked you to take a look at the "test_sctp.py" is to see how
> things are setup and execute the exact steps in the CLI. You'll see things
> work.
>  
> You cannot remove the MTU code because that's used to initialize the PMTU and
> calculate initially the MSS to be sent to the other peer.
>  
>  
> Cheers,
> Marco
>  
> On Wed, 2018-11-21 at 01:50 +, Liu Daolin (刘道林) wrote:
> > Hi Marco,
> >  
> > Thanks for your reply.
> >  
> > Actually I'm trying to read the sctp code recently to want to know how it
> > works. My requirement is very simply. I need to run sctp server based on vpp
> > on one VM, and run sctp client without vpp (I have this now) on the other
> > VM. As my below email, there will be aborted (core dumped), and I found the
> > place yesterday, but I don’t know the root reason. You can see below
> > picture:
> >  
> > 
> >  
> > The sw_if_index is -1, so crashed when get mtu. Maybe I miss something? When
> > I run actually is CLI command from echo_server.c. As you mentioned, if I run
> > test_sctp.py, it will work fine? My requirement is only C language as it
> > will merged some other code, so I don’t like to run it with python.
> >  
> > Yesterday, I also try to remove this mtu code, and the crash was disappeared
> > although the sw_if_index is still -1, and then I start sctp client on the
> > other VM to send INIT, but the server with vpp seemed be dead (no crash but
> > cannot enter any command, seemed dead loop).
> >  
> > Anyway, I think it's better to try CLI "test echo server" in your side and
> > find and fix all issues visually.
> >  
> >  
> >  
> >  
> >  
> > Best regards
> > 刘道林 (Daolin Liu)
> > T大连市共进科技有限公司
> > DALIAN GONGJIN TECHNOLOGY CO.,LTD
> > 中国大连市高新园区软件园路1A-4-24层
> > Floor 24th, 1A-4 Software Park Road, Hi-tech Zone, Dalian, Liaoning, China
> > 直线(TEL)：(86-411)39996705   分机(EXT)：76824
> > 手机(Mobile)：(86)13704090959
> >  
> > -邮件原件-
> > 发件人: Marco Varlese [mailto:mvarl...@suse.de] 
> > 发送时间: 2018年11月21日 1:06
> > 收件人: Liu Daolin (刘道林); vpp-dev@lists.fd.io
> > 主题: Re: [vpp-dev] about sctp
> >  
> > Hi,
> >  
> > On Tue, 2018-11-20 at 02:50 +, Liu Daolin (刘道林) wrote:
> > > Hi,
> > > 
> > > I encountered below Aborted (core dumped) issue:
> > > 
> > >
> > > 
> > > When I run "test echo server uri", it's ok for tcp, but crashed
> > immediately
> > > for sctp.
> > > 
> > > Please try this in your side and give me advice. I use 18.10. Thanks!
> > Can you please try to run "make test TEST=test_sctp"?
> > > 
> > > 
> > > Best regards
> > > 刘道林 (Daolin Liu)
> > > T大连市共进科技有限公司
> > > DALIAN GONGJIN TECHNOLOGY CO.,LTD
> > > 中国大连市高新园区软件园路1A-4-24层
> > > Floor 24th, 1A-4 Software Park Road, Hi-tech Zone, Dalian, Liaoning, China
> > > 直线(TEL)：(86-411)39996705   分机(EXT)：76824
> > > 手机(Mobile)：(86)13704090959
> > > 
> > > 发件人: Liu Daolin (刘道林)
> > > 发送时间: 2018年11月19日 19:23
> > > 收件人: 'vpp-dev@lists.fd.io'
> > > 主题: about sctp
> > > 
> > > Hi,

Re: 答复: [vpp-dev] about sctp

[Marco Varlese]

Dear Liu,
The reason why I asked you to take a look at the "test_sctp.py" is to see how
things are setup and execute the exact steps in the CLI. You'll see things work.
You cannot remove the MTU code because that's used to initialize the PMTU and
calculate initially the MSS to be sent to the other peer.

Cheers,Marco
On Wed, 2018-11-21 at 01:50 +, Liu Daolin (刘道林) wrote:
> Hi Marco,
>  
> Thanks for your reply.
>  
> Actually I'm trying to read the sctp code recently to want to know how it
> works. My requirement is very simply. I need to run sctp server based on vpp
> on one VM, and run sctp client without vpp (I have this now) on the other VM.
> As my
>  below email, there will be aborted (core dumped), and I found the place
> yesterday, but I don’t know the root reason. You can see below picture:
>  
> 
>  
> The sw_if_index is -1, so crashed when get mtu. Maybe I miss something? When I
> run actually is CLI command from echo_server.c. As you mentioned, if I run
> test_sctp.py, it will work fine? My requirement is only C language as it will
> merged
>  some other code, so I don’t like to run it with python.
>  
> Yesterday, I also try to remove this mtu code, and the crash was disappeared
> although the sw_if_index is still -1, and then I start sctp client on the
> other VM to send INIT, but the server with vpp seemed be dead (no crash but
> cannot
>  enter any command, seemed dead loop).
>  
> Anyway, I think it's better to try CLI "test echo server" in your side and
> find and fix all issues visually.
>  
>  
>  
>  
>  
> Best regards
> 刘道林 (Daolin Liu)
> T大连市共进科技有限公司
> DALIAN GONGJIN TECHNOLOGY CO.,LTD
> 中国大连市高新园区软件园路1A-4-24层
> Floor 24th, 1A-4 Software Park Road, Hi-tech Zone, Dalian, Liaoning, China
> 直线(TEL)：(86-411)39996705  
> 分机(EXT)：76824
> 手机(Mobile)：(86)13704090959
>  
> -邮件原件-
> 
> 发件人: Marco Varlese [mailto:mvarl...@suse.de]
> 
> 
> 发送时间: 2018年11月21日 1:06
> 
> 收件人: Liu Daolin (刘道林); vpp-dev@lists.fd.io
> 
> 主题: Re: [vpp-dev] about sctp
>  
> Hi,
>  
> On Tue, 2018-11-20 at 02:50 +, Liu Daolin (刘道林) wrote:
> > Hi,
> >  
> > I encountered below Aborted (core dumped) issue:
> >  
> > 
> >  
> > When I run "test echo server uri", it's ok for tcp, but crashed immediately
> > for sctp.
> >  
> > Please try this in your side and give me advice. I use 18.10. Thanks!
> Can you please try to run "make test TEST=test_sctp"?
> >  
> >  
> > Best regards
> > 刘道林 (Daolin Liu)
> > T大连市共进科技有限公司
> > DALIAN GONGJIN TECHNOLOGY CO.,LTD
> > 中国大连市高新园区软件园路1A-4-24层
> > Floor 24th, 1A-4 Software Park Road, Hi-tech Zone, Dalian, Liaoning, China
> > 直线(TEL)：(86-411)39996705  
> 分机(EXT)：76824
> > 手机(Mobile)：(86)13704090959
> >  
> > 发件人: Liu Daolin (刘道林)
> 
> > 发送时间: 2018年11月19日 19:23
> > 收件人: 'vpp-dev@lists.fd.io'
> > 主题: about sctp
> >  
> > Hi,
> >  
> > I'd like to know some information about sctp.
> >  
> > Is this fully functional? Or just partly? 
> There are missing pieces to the SCTP implementations. 
>  
> > Actually, I want to try simply with CLI to verify sctp basic functions now.
> > But it seems that there is no CLI, and the binary APIs are also imperfect.
> What do you actually mean by imperfect? Any input (e.g. patch submission)
> would
> be greatly appreciated!
> >  
> > Do you have any plan in the next release? Including the sample test.
> I am planning to create some JIRA ticket(s) so that people can see what's
> missing and contribute if they like. Would you be interested?
>  
> >  
> > Best regards
> > 刘道林 (Daolin Liu)
> > T大连市共进科技有限公司
> > DALIAN GONGJIN TECHNOLOGY CO.,LTD
> > 中国大连市高新园区软件园路1A-4-24层
> > Floor 24th, 1A-4 Software Park Road, Hi-tech Zone, Dalian, Liaoning, China
> > 直线(TEL)：(86-411)39996705  
> 分机(EXT)：76824
> > 手机(Mobile)：(86)13704090959
> >  
> >
> 本电子邮件（包括任何的附件）为本公司保密文件。本文件仅仅可为以上指定的收件人或公司使用，如果阁下非电子邮件所指定之收件人，那么阁下对该邮件部分或全部的泄漏、
> >
> 阅览、复印、变更、散布或对邮件内容的使用都是被严格禁止的。如果阁下接收了该错误传送的电子邮件，敬请阁下通过回复该邮件的方式立即通知寄件人，同时删除你所接收到
> > 的文本。 This e-mail may contain confidential and/or privileged information. If
> > you are not the intended recipient (or have received this e-mail in error)
> > please notify the sender immediately and destroy this e-mail. Any
> unauthorized
> > copying, disclosure or distribution of the material in this e-mail is
> strictly
> > forbidden.
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> > 
> > View/Reply Online (#113

Re: [vpp-dev] about sctp

[Marco Varlese]

Hi,

On Tue, 2018-11-20 at 02:50 +, Liu Daolin (刘道林) wrote:
> Hi,
>  
> I encountered below Aborted (core dumped) issue:
>  
> 
>  
> When I run "test echo server uri", it's ok for tcp, but crashed immediately
> for sctp.
>  
> Please try this in your side and give me advice. I use 18.10. Thanks!
Can you please try to run "make test TEST=test_sctp"?
>  
>  
> Best regards
> 刘道林 (Daolin Liu)
> T大连市共进科技有限公司
> DALIAN GONGJIN TECHNOLOGY CO.,LTD
> 中国大连市高新园区软件园路1A-4-24层
> Floor 24th, 1A-4 Software Park Road, Hi-tech Zone, Dalian, Liaoning, China
> 直线(TEL)：(86-411)39996705   分机(EXT)：76824
> 手机(Mobile)：(86)13704090959
>  
> 发件人: Liu Daolin (刘道林) 
> 发送时间: 2018年11月19日 19:23
> 收件人: 'vpp-dev@lists.fd.io'
> 主题: about sctp
>  
> Hi,
>  
> I'd like to know some information about sctp.
>  
> Is this fully functional? Or just partly? 
There are missing pieces to the SCTP implementations. 

> Actually, I want to try simply with CLI to verify sctp basic functions now.
> But it seems that there is no CLI, and the binary APIs are also imperfect.
What do you actually mean by imperfect? Any input (e.g. patch submission) would
be greatly appreciated!
>  
> Do you have any plan in the next release? Including the sample test.
I am planning to create some JIRA ticket(s) so that people can see what's
missing and contribute if they like. Would you be interested?

>  
> Best regards
> 刘道林 (Daolin Liu)
> T大连市共进科技有限公司
> DALIAN GONGJIN TECHNOLOGY CO.,LTD
> 中国大连市高新园区软件园路1A-4-24层
> Floor 24th, 1A-4 Software Park Road, Hi-tech Zone, Dalian, Liaoning, China
> 直线(TEL)：(86-411)39996705   分机(EXT)：76824
> 手机(Mobile)：(86)13704090959
>  
> 本电子邮件（包括任何的附件）为本公司保密文件。本文件仅仅可为以上指定的收件人或公司使用，如果阁下非电子邮件所指定之收件人，那么阁下对该邮件部分或全部的泄漏、
> 阅览、复印、变更、散布或对邮件内容的使用都是被严格禁止的。如果阁下接收了该错误传送的电子邮件，敬请阁下通过回复该邮件的方式立即通知寄件人，同时删除你所接收到
> 的文本。 This e-mail may contain confidential and/or privileged information. If
> you are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any unauthorized
> copying, disclosure or distribution of the material in this e-mail is strictly
> forbidden.
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#11334): https://lists.fd.io/g/vpp-dev/message/11334
> Mute This Topic: https://lists.fd.io/mt/28240674/675056
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [mvarl...@suse.de]
> -=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11340): https://lists.fd.io/g/vpp-dev/message/11340
Mute This Topic: https://lists.fd.io/mt/28240674/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Andrew Yourtchenko is now a vpp project committer!

[Marco Varlese]

Congratulations Andrew!!!

On Thu, 2018-11-15 at 16:43 +, Dave Barach via Lists.Fd.Io wrote:
> The TSC formally approved Andrew’s vpp committer nomination a short while ago.
>  
> Congratulations, and thanks in advance for your participation as a committer.
>  
> Dave
>  
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#11261): 
> https://lists.fd.io/g/vpp-dev/message/11261
> 
> Mute This Topic: 
> https://lists.fd.io/mt/28147575/675056
> 
> Group Owner: 
> vpp-dev+ow...@lists.fd.io
> 
> Unsubscribe: 
> https://lists.fd.io/g/vpp-dev/unsub
>   [
> mvarl...@suse.de
> ]
> -=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11281): https://lists.fd.io/g/vpp-dev/message/11281
Mute This Topic: https://lists.fd.io/mt/28147575/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] #vpp sctp echo test crash

[Marco Varlese]

Florin,
Your patch addresses the TCP issue.Now back to SCTP... ;(

Cheers,Marco
On Thu, 2018-11-08 at 14:02 -0800, Florin Coras wrote:
> Hm, I suspect in case of TCP it may be an overlap between unit tests and the
> throughput test. I’ve separated them here. Can you try it out with 500M
> locally? It works fine on my box, but maybe it has to do with the hardware it
> runs on. 
> 
> Thanks, 
> Florin
> 
> [1] https://gerrit.fd.io/r/#/c/15833/
> > On Nov 8, 2018, at 1:29 PM, Marco Varlese  wrote:
> > 
> > It finishes with errors (stating 3 tests failed). Same behavior as seen with
> > SCTP so I'm now guessing that's rather an issue with the test code (either
> > client or server) or with the session layer (doubt that since VCL works)??
> > 
> > Thoughts?
> > Marco Varlese
> > 
> > On Nov 8, 2018 22:06, Florin Coras  wrote:
> > > Hi Marco, 
> > > So echo test with 500MB does finish and reports throughput after 15s but
> > > with warnings of the type “clients stuck”?
> > > 
> > > Note that we also have tests that run iperf3 for about 5s and those
> > > exchange GB of data probably. 
> > > 
> > > Florin
> > > 
> > > > On Nov 8, 2018, at 12:55 PM, Marco Varlese  wrote:
> > > 
> > > Well, folks there's something strange here...
> > > I was trying to understand what's going on with SCTP and (because I
> > > couldn't see the light) I decided to give TCP a try.
> > > I hence modified test_tcp.py to have 500 mbytes to send and the test
> > > fails. Similarly to what happens for SCTP. I did try to increase the test-
> > > timeout but without much success...
> > > Interestingly, for both TCP and SCTP, with a test-timeout of 30 seconds
> > > the test completes (with errors) after round 12-15 secs...
> > > On Thu, 2018-11-08 at 08:21 -0800, Florin Coras wrote:
> > > > Hi guys, 
> > > > I unfortunately missed this. Yes, the fifo size provided is the number
> > > > of kB and yes you should be able to do 4MB (fifo-size 4096) or even
> > > > higher. 
> > > > 
> > > > The “stuck clients” warning is just a notification, the test can still
> > > > finish. To make sure you give the test enough time, add “test-timeout
> > > > ” to the list of parameters. 
> > > > 
> > > > Florin
> > > > 
> > > > > On Nov 8, 2018, at 5:46 AM, Yao, Chengqiang 
> > > > > wrote:
> > > > > 
> > > > > Hi Macro, Seems the max workable fifo-size in test_sctp.py is 16. With
> > > > > fifo-size in test_sctp.py set to 16, the throughput is only 4Gbps (VPP
> > > > > is under release mode), I think the real number should be more than
> > > > > this if we can increase both fifo-size and mbytes in test_sctp.py. 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11184): https://lists.fd.io/g/vpp-dev/message/11184
Mute This Topic: https://lists.fd.io/mt/28023358/21656
Mute #vpp: https://lists.fd.io/mk?hashtag=vpp=1480452
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] #vpp sctp echo test crash

[Marco Varlese]

It finishes with errors (stating 3 tests failed). Same behavior as seen with 
SCTP so I'm now guessing that's rather an issue with the test code (either 
client or server) or with the session layer (doubt that since VCL works)??
Thoughts?


Marco VarleseOn Nov 8, 2018 22:06, Florin Coras  wrote:
>
> Hi Marco, 
>
> So echo test with 500MB does finish and reports throughput after 15s but with 
> warnings of the type “clients stuck”?
>
> Note that we also have tests that run iperf3 for about 5s and those exchange 
> GB of data probably. 
>
> Florin
>
>> On Nov 8, 2018, at 12:55 PM, Marco Varlese  wrote:
>>
> Well, folks there's something strange here...
>
> I was trying to understand what's going on with SCTP and (because I couldn't 
> see the light) I decided to give TCP a try.
>
> I hence modified test_tcp.py to have 500 mbytes to send and the test fails. 
> Similarly to what happens for SCTP. I did try to increase the test-timeout 
> but without much success...
>
> Interestingly, for both TCP and SCTP, with a test-timeout of 30 seconds the 
> test completes (with errors) after round 12-15 secs...
>
> On Thu, 2018-11-08 at 08:21 -0800, Florin Coras wrote:
>>
>> Hi guys, 
>>
>> I unfortunately missed this. Yes, the fifo size provided is the number of kB 
>> and yes you should be able to do 4MB (fifo-size 4096) or even higher. 
>>
>> The “stuck clients” warning is just a notification, the test can still 
>> finish. To make sure you give the test enough time, add “test-timeout 
>> ” to the list of parameters. 
>>
>> Florin
>>
>>> On Nov 8, 2018, at 5:46 AM, Yao, Chengqiang  
>>> wrote:
>>>
>>> Hi Macro,
>>>  
>>> Seems the max workable fifo-size in test_sctp.py is 16. With fifo-size in 
>>> test_sctp.py set to 16, the throughput is only 4Gbps (VPP is under release 
>>> mode), I think the real number should be more than this if we can increase 
>>> both fifo-size and mbytes in test_sctp.py.
>>>  -=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11177): https://lists.fd.io/g/vpp-dev/message/11177
Mute This Topic: https://lists.fd.io/mt/28023358/21656
Mute #vpp: https://lists.fd.io/mk?hashtag=vpp=1480452
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] #vpp sctp echo test crash

[Marco Varlese]

Well, folks there's something strange here...
I was trying to understand what's going on with SCTP and (because I couldn't see
the light) I decided to give TCP a try.
I hence modified test_tcp.py to have 500 mbytes to send and the test fails.
Similarly to what happens for SCTP. I did try to increase the test-timeout but
without much success...
Interestingly, for both TCP and SCTP, with a test-timeout of 30 seconds the test
completes (with errors) after round 12-15 secs...
On Thu, 2018-11-08 at 08:21 -0800, Florin Coras wrote:
> Hi guys, 
> I unfortunately missed this. Yes, the fifo size provided is the number of kB
> and yes you should be able to do 4MB (fifo-size 4096) or even higher. 
> 
> The “stuck clients” warning is just a notification, the test can still finish.
> To make sure you give the test enough time, add “test-timeout  seconds>” to the list of parameters. 
> 
> Florin
> 
> > On Nov 8, 2018, at 5:46 AM, Yao, Chengqiang 
> > wrote:
> > 
> > Hi Macro, Seems the max workable fifo-size in test_sctp.py is 16. With fifo-
> > size in test_sctp.py set to 16, the throughput is only 4Gbps (VPP is under
> > release mode), I think the real number should be more than this if we can
> > increase both fifo-size and mbytes in test_sctp.py.   If
> > increase fifo-size to 20, or increase mbytes in test_sctp.py to more than
> > 2000, an issue will happen. Maybe “make test” is only for functional
> > test. Best Regards,Chengqiang Yao  From: 
> > vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Marco Varlese
> > Sent: Thursday, November 8, 2018 8:20 PM
> > To: Yao, Chengqiang 
> > Cc: vpp-dev@lists.fd.io
> > Subject: Re: [vpp-dev] #vpp sctp echo test crash On Thu, 2018-11-08 at 11:59
> > +, Yao, Chengqiang wrote:
> > > Hi Macro,
> > >  
> > > I’m running on master branch and latest version.
> > >  
> > > “make test TEST-test_sctp.py” also works for me. I want to benchmark the
> > > performance of sctp, but fifo-size is only 4 in test_sctp.py, so the
> > > throughput is only ~2Gbps. If I increase the fifo-size in test_sctp.py,
> > > then the test fails.
> > Please see:
> > src/vnet/session-apps/echo_client.c
> > src/vnet/session-apps/echo_server.c
> >  
> > In there you would see that fifo-size is shifted left by 10 (that means 4
> > becomes 4096). Maybe you want to try with 8 or 16?
> > Hopefully, Florin can shed some light about the usage of 4096 for the fifo-
> > size... which would eventually mean a fifo of 4M entries?
> >  
> > >  
> > > That’s why I want to use CLI commands to test SCTP. I’m not intended to
> > > run multiple clients, the reason I set nclients=2 is because test_sctp.py
> > > does the same thing, I just want to keep the same.
> > I am not sure why you see nclients=2 in test_sctp.py... there's no mention
> > of it on latest MASTER... 
> > >   You mean you use the same commands in my last mail, and there is no
> > > issue? If yes, then I need to check my setup.   Best Regards,Chengqiang
> > > Yao   From: Marco Varlese [mailto:mvarl...@suse.de] 
> > > Sent: Thursday, November 8, 2018 6:52 PM
> > > To: Yao, Chengqiang 
> > > Cc: vpp-dev@lists.fd.io
> > > Subject: Re: [vpp-dev] #vpp sctp echo test crash Dear Yao, First of all,
> > > are you on MASTER branch or some other release? Second, can you run "make
> > > test TEST=test_sctp.py" and see if that works for you? It all looks good
> > > on my side and on Jenkins. If you are interested in running multiple
> > > clients, you can do that by editing test_sctp.py and add "nclients X"
> > > (where X can be 2 or more). Again, I have just tested it right now and I
> > > cannot see that issue.  Cheers,Marco On Thu, 2018-11-08 at 09:20 +,
> > > Yao, Chengqiang wrote:
> > > > Hi Macro, I follow test_sctp.py to use following commands in server and
> > > > client, but client can not connect server with an error printed
> > > > “echo_client_node_fn:238: stuck clients” as you can see below.Do I miss
> > > > any command ?  Server:vpp# set int ip address FortyGigabitEthernet18/0/1
> > > > 192.168.60.73/24vpp# set int state FortyGigabitEthernet18/0/1 upvpp# set
> > > > ip arp FortyGigabitEthernet18/0/1 192.168.60.74 3c:fd:fe:c2:12:68vpp#
> > > > session enablevpp# app ns add id 0 secret 0 sw_if_index 2vpp# test echo
> > > > server appns 0 fifo-size 4 uri sctp://192.168.60.73/1234  Client:vpp#
> > > > set int ip address FortyGigabitEthernet18/0/0 192.168.60.74/24vpp# set
> > > > int s

Re: [vpp-dev] New Committer Nomination: Andrew Yourtchenko

[Marco Varlese]

+1

On Thu, 2018-11-08 at 12:13 +, Dave Barach via Lists.Fd.Io wrote:
> In view of significant code contributions to the vpp project - see below - I'm
> pleased to nominate Andrew Yourtchenko as a vpp project committer. I have high
> confidence that he'll be a major asset to the project in a committer role.  
> 
> Andrew has contributed 181 merged patches, including significant new feature
> work in the ACL plugin. Example: https://gerrit.fd.io/r/#/c/13162
>  
> Committers, please vote (+1, 0, -1) on vpp-dev@ We'll need a recorded vote
> so that the TSC will approve Andrew's nomination.
> 
> Thanks... Dave
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#11158): https://lists.fd.io/g/vpp-dev/message/11158
> Mute This Topic: https://lists.fd.io/mt/28035544/675056
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [mvarl...@suse.de]
> -=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11162): https://lists.fd.io/g/vpp-dev/message/11162
Mute This Topic: https://lists.fd.io/mt/28035544/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] #vpp sctp echo test crash

[Marco Varlese]

On Thu, 2018-11-08 at 11:59 +, Yao, Chengqiang wrote:
> Hi Macro,
> 
>  
> 
> I’m running on master branch and latest version.
> 
>  
> 
> “make test TEST-test_sctp.py” also works for me. I want to benchmark the
> performance of sctp, but fifo-size is only 4 in test_sctp.py,
>  so the throughput is only ~2Gbps. If I increase the fifo-size in
> test_sctp.py, then the test fails.
Please see:
src/vnet/session-apps/echo_client.c
src/vnet/session-apps/echo_server.c

In there you would see that fifo-size is shifted left by 10 (that means 4
becomes 4096). Maybe you want to try with 8 or 16?
Hopefully, Florin can shed some light about the usage of 4096 for the fifo-
size... which would eventually mean a fifo of 4M entries?

> That’s why I want to use CLI commands to test SCTP. I’m not intended to run
> multiple clients, the reason I set nclients=2 is because
>  test_sctp.py does the same thing, I just want to keep the same.
I am not sure why you see nclients=2 in test_sctp.py... there's no mention of it
on latest MASTER...
>  
> You mean you use the same commands in my last mail, and there is no issue? If
> yes, then I need to check my setup.
>  
>  
>  
> Best Regards,
> Chengqiang Yao
>  
>  
>  
> 
> 
> From: Marco Varlese [mailto:mvarl...@suse.de]
> 
> 
> Sent: Thursday, November 8, 2018 6:52 PM
> 
> To: Yao, Chengqiang 
> 
> Cc: vpp-dev@lists.fd.io
> 
> Subject: Re: [vpp-dev] #vpp sctp echo test crash
> 
> 
>  
> 
> Dear Yao,
> 
> 
>  
> 
> 
> First of all, are you on MASTER branch or some other release?
> 
> 
>  
> 
> 
> Second, can you run "make test TEST=test_sctp.py" and see if that works for
> you? It all looks good on my side and on Jenkins.
> 
> 
>  
> 
> 
> If you are interested in running multiple clients, you can do that by editing
> test_sctp.py and add "nclients X" (where X can be 2 or more).
> 
> 
>  
> 
> 
> Again, I have just tested it right now and I cannot see that issue.
> 
> 
> 
>  
> 
> 
>  
> 
> 
> Cheers,
> 
> 
> Marco
> 
> 
>  
> 
> 
> On Thu, 2018-11-08 at 09:20 +, Yao, Chengqiang wrote:
> 
> > Hi Macro,
> >  
> > I follow test_sctp.py to use following commands in server and client, but
> > client can not connect server with an error printed
> > “echo_client_node_fn:238:
> >  stuck clients” as you can see below.
> > Do I miss any command ?
> >  
> >  
> > Server:
> > vpp# set int ip address FortyGigabitEthernet18/0/1 192.168.60.73/24
> > vpp# set int state FortyGigabitEthernet18/0/1 up
> > vpp# set ip arp FortyGigabitEthernet18/0/1 192.168.60.74 3c:fd:fe:c2:12:68
> > vpp# session enable
> > vpp# app ns add id 0 secret 0 sw_if_index 2
> > vpp# test echo server appns 0 fifo-size 4 uri sctp://192.168.60.73/1234
> >  
> >  
> > Client:
> > vpp# set int ip address FortyGigabitEthernet18/0/0 192.168.60.74/24
> > vpp# set int state FortyGigabitEthernet18/0/0 up
> > vpp# set ip arp FortyGigabitEthernet18/0/0 192.168.60.73 3c:fd:fe:c2:17:09
> > vpp# session enable
> > vpp# app ns add id 1 secret 0 sw_if_index 1
> > vpp# test echo client nclients 2 mbytes 10 appns 1 fifo-size 4 test-bytes
> > syn-timeout 3 uri sctp://192.168.60.73/1234
> >  
> >  
> >  
> > 2 three-way handshakes in 0.00 seconds 4648.53/s
> > Test started at 37.835987
> > 0: echo_client_node_fn:238: stuck clients
> > Timeout with 2 sessions still active...
> > test failed
> > test echo clients: failed: timeout with 2 sessions
> >  
> >  
> > Best Regards,
> > Chengqiang Yao
> >  
> >  
> >  
> >  
> > 
> > 
> > From: Marco Varlese [mailto:mvarl...@suse.de]
> > 
> > 
> > Sent: Thursday, November 8, 2018 4:07 PM
> > 
> > To: Yao, Chengqiang 
> > 
> > Cc: vpp-dev@lists.fd.io
> > 
> > Subject: Re: [vpp-dev] #vpp sctp echo test crash
> > 
> > 
> >  
> > 
> > Hi Yao,
> > 
> > 
> >  
> > 
> > 
> > As per test_sctp.py the command is:
> > 
> > 
> >  
> > 
> > 
> > test echo server appns 0 fifo-size 4 [URI]
> > 
> > 
> >  
> > 
> > 
> > Where URI is made up as: sctp://IP/PORT
> > 
> > 
> >  
> > 
> > 
> > Please, take a look at "test/test_sctp.py" to see also the client side of
> > it.
> > 
> > 
> >  
> > 
> > 
> >  
> > 
> > 
> > HTH,
> > 
> > 
> > Marco
> > 
&

Re: [vpp-dev] #vpp sctp echo test crash

[Marco Varlese]

Dear Yao,
First of all, are you on MASTER branch or some other release?
Second, can you run "make test TEST=test_sctp.py" and see if that works for you?
It all looks good on my side and on Jenkins.
If you are interested in running multiple clients, you can do that by editing
test_sctp.py and add "nclients X" (where X can be 2 or more).
Again, I have just tested it right now and I cannot see that issue. 

Cheers,Marco
On Thu, 2018-11-08 at 09:20 +, Yao, Chengqiang wrote:
> Hi Macro,
>  
> I follow test_sctp.py to use following commands in server and client, but
> client can not connect server with an error printed “echo_client_node_fn:238:
>  stuck clients” as you can see below.
> Do I miss any command ?
>  
>  
> Server:
> vpp# set int ip address FortyGigabitEthernet18/0/1 192.168.60.73/24
> vpp# set int state FortyGigabitEthernet18/0/1 up
> vpp# set ip arp FortyGigabitEthernet18/0/1 192.168.60.74 3c:fd:fe:c2:12:68
> vpp# session enable
> vpp# app ns add id 0 secret 0 sw_if_index 2
> vpp# test echo server appns 0 fifo-size 4 uri sctp://192.168.60.73/1234
>  
>  
> Client:
> vpp# set int ip address FortyGigabitEthernet18/0/0 192.168.60.74/24
> vpp# set int state FortyGigabitEthernet18/0/0 up
> vpp# set ip arp FortyGigabitEthernet18/0/0 192.168.60.73 3c:fd:fe:c2:17:09
> vpp# session enable
> vpp# app ns add id 1 secret 0 sw_if_index 1
> vpp# test echo client nclients 2 mbytes 10 appns 1 fifo-size 4 test-bytes syn-
> timeout 3 uri sctp://192.168.60.73/1234
>  
>  
>  
> 2 three-way handshakes in 0.00 seconds 4648.53/s
> Test started at 37.835987
> 0: echo_client_node_fn:238: stuck clients
> Timeout with 2 sessions still active...
> test failed
> test echo clients: failed: timeout with 2 sessions
>  
>  
> Best Regards,
> Chengqiang Yao
>  
>  
>  
>  
> 
> 
> From: Marco Varlese [mailto:mvarl...@suse.de]
> 
> 
> Sent: Thursday, November 8, 2018 4:07 PM
> 
> To: Yao, Chengqiang 
> 
> Cc: vpp-dev@lists.fd.io
> 
> Subject: Re: [vpp-dev] #vpp sctp echo test crash
> 
> 
>  
> 
> Hi Yao,
> 
> 
>  
> 
> 
> As per test_sctp.py the command is:
> 
> 
>  
> 
> 
> test echo server appns 0 fifo-size 4 [URI]
> 
> 
>  
> 
> 
> Where URI is made up as: sctp://IP/PORT
> 
> 
>  
> 
> 
> Please, take a look at "test/test_sctp.py" to see also the client side of it.
> 
> 
>  
> 
> 
>  
> 
> 
> HTH,
> 
> 
> Marco
> 
> 
>  
> 
> 
> On Wed, 2018-11-07 at 15:01 +, Yao, Chengqiang wrote:
> 
> > Hi Macro,
> >  
> > I use following CLI command to setup SCTP server, but VPP crashed. While
> > this command works for TCP/UDP.
> >  
> > Can you tell me  the correct cli commands to run echo test for SCTP?
> >  
> >  
> > vpp# set int ip address FortyGigabitEthernet18/0/1 192.168.60.73/24
> > vpp# set int state FortyGigabitEthernet18/0/1 up
> > vpp# set ip arp FortyGigabitEthernet18/0/1 192.168.60.74 3c:fd:fe:c2:12:68
> > vpp# test echo server fifo-size 4096 uri sctp://192.168.60.73/1234 no-echo
> >  
> >  
> > After debugging, I found it’s caused by invalid sw_if_index in
> > sctp_connection_bind function of sctp.c.
> > 
> >  
> >  
> >  
> > Best Regards,
> > Chengqiang Yao
> >  
> >  
> >  
> > 
> > 
> > From:
> > vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io]
> > On Behalf Of Yao, Chengqiang
> > 
> > Sent: Thursday, October 25, 2018 9:15 PM
> > 
> > To: Marco Varlese ;
> > vpp-dev@lists.fd.io
> > 
> > Subject: Re: [vpp-dev] #vpp
> > 
> > 
> >  
> > Hi Macro,
> >  
> > Thanks for your information, I will have a try.
> >  
> >  
> > Best Regards,
> > Chengqiang Yao
> >  
> >  
> >  
> > 
> > 
> > From: Marco Varlese [mailto:mvarl...@suse.de]
> > 
> > 
> > Sent: Thursday, October 25, 2018 9:09 PM
> > 
> > To: Yao, Chengqiang ;
> > vpp-dev@lists.fd.io
> > 
> > Subject: Re: [vpp-dev] #vpp
> > 
> > 
> >  
> > 
> > Hi,
> > 
> > 
> >  
> > 
> > 
> > On Thu, 2018-10-25 at 04:59 +, Yao, Chengqiang wrote:
> > 
> > > Hi Macro,
> > >  
> > > Is there any sample code to show how to use SCTP (such as association,
> > > packet transmission/reception, etc.)? And is there any performance
> > >  report for SCTP?
> > 
> > You can have a look at the test for SCTP:
> > 
> > 
> > 1) test/test_sctp.py
> >

Re: [vpp-dev] #vpp sctp echo test crash

[Marco Varlese]

Hi Yao,
As per test_sctp.py the command is:
test echo server appns 0 fifo-size 4 [URI]
Where URI is made up as: sctp://IP/PORT
Please, take a look at "test/test_sctp.py" to see also the client side of it.

HTH,Marco
On Wed, 2018-11-07 at 15:01 +, Yao, Chengqiang wrote:
> Hi Macro,
>  
> I use following CLI command to setup SCTP server, but VPP crashed. While this
> command works for TCP/UDP.
>  
> Can you tell me  the correct cli commands to run echo test for SCTP?
>  
>  
> vpp# set int ip address FortyGigabitEthernet18/0/1 192.168.60.73/24
> vpp# set int state FortyGigabitEthernet18/0/1 up
> vpp# set ip arp FortyGigabitEthernet18/0/1 192.168.60.74 3c:fd:fe:c2:12:68
> vpp# test echo server fifo-size 4096 uri sctp://192.168.60.73/1234 no-echo
>  
>  
> After debugging, I found it’s caused by invalid sw_if_index in
> sctp_connection_bind function of sctp.c.
> 
>  
>  
>  
> Best Regards,
> Chengqiang Yao
>  
>  
>  
> 
> 
> From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io]
> On Behalf Of Yao, Chengqiang
> 
> Sent: Thursday, October 25, 2018 9:15 PM
> 
> To: Marco Varlese ; vpp-dev@lists.fd.io
> 
> Subject: Re: [vpp-dev] #vpp
> 
> 
>  
> Hi Macro,
>  
> Thanks for your information, I will have a try.
>  
>  
> Best Regards,
> Chengqiang Yao
>  
>  
>  
> 
> 
> From: Marco Varlese [mailto:mvarl...@suse.de]
> 
> 
> Sent: Thursday, October 25, 2018 9:09 PM
> 
> To: Yao, Chengqiang ;
> vpp-dev@lists.fd.io
> 
> Subject: Re: [vpp-dev] #vpp
> 
> 
>  
> 
> Hi,
> 
> 
>  
> 
> 
> On Thu, 2018-10-25 at 04:59 +, Yao, Chengqiang wrote:
> 
> > Hi Macro,
> >  
> > Is there any sample code to show how to use SCTP (such as association,
> > packet transmission/reception, etc.)? And is there any performance
> >  report for SCTP?
> 
> You can have a look at the test for SCTP:
> 
> 
> 1) test/test_sctp.py
> 
> 
> 2) src/vnet/session-apps/echo_client.c & echo_server.c
> 
> 
>  
> 
> 
> The echo_client and echo_server are used by TCP / UDP and SCTP to exercise the
> networking stack implemented.
> 
> 
>  
> 
> 
> With regards to the state-machine (I assumed that's what you're asking by
> "association", "packet transmssion/reception", etc.), the whole of it is gone
> through when running the tests.
> 
> 
> If you are interested in seeing/learning how that's implemented I am afraid
> you need to look into the code tho.
> 
> 
>  
> 
> 
> With regards to performance: no, there're no reports. However, something can
> be retrieved by running the test_sctp.py since at the end it prints out how
> much data has been transferred and how long that took.
> 
> 
>  
> 
> >  
> >  
> > Best Regards,
> > Chengqiang Yao
> 
> Cheers,
> 
> 
> Marco
> 
> 
>  
> 
> >  
> >  
> >  
> >  
> > 
> > 
> > From:
> > vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io]
> > On Behalf Of Marco Varlese
> > 
> > Sent: Wednesday, October 10, 2018 5:47 PM
> > 
> > To: srivastava.rac...@gmail.com;
> > vpp-dev@lists.fd.io
> > 
> > Subject: Re: [vpp-dev] #vpp
> > 
> > 
> >  
> > 
> > Hi Srivastava,
> > 
> > 
> >  
> > 
> > 
> > On Wed, 2018-10-10 at 01:23 -0700, 
> > srivastava.rac...@gmail.com wrote:
> > 
> > > Hi 
> > > 
> > > 
> > >  
> > > 
> > > 
> > > Does the VPP support SCTP. If yes what is the configuration for SCTP. Does
> > > it support the same features as the linux kernel SCTP ?
> > > 
> > 
> > VPP has an implementation for SCTP. You can look into /src/vnet/sctp folder
> > to see what we currently support in terms of RFC.
> > 
> > 
> > Any feedback (and contribution) is very much welcome!
> > 
> > 
> >  
> > 
> > >  
> > > 
> > > 
> > > Thanks
> > > 
> > > 
> > > Rachit Srivastava
> > > 
> > 
> > Thanks,
> > 
> > 
> > Marco
> > 
> > 
> >  
> > 
> > > -=-=-=-=-=-=-=-=-=-=-=-
> > > Links: You receive all messages sent to this group.
> > >  
> > > View/Reply Online (#10787): https://lists.fd.io/g/vpp-dev/message/10787
> > > Mute This Topic: https://lists.fd.io/mt/27155313/675056
> > > Mute #vpp: https://lists.fd.io/mk?hashtag=vpp=1480704
> > > Group Owner: vpp-dev+ow...@lists.fd.io
> > > Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [mvarl...@suse.de]
> > > -=-=-=-=-=-=-=-=-=-=-=-
> > >  
> 
> 
> 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11152): https://lists.fd.io/g/vpp-dev/message/11152
Mute This Topic: https://lists.fd.io/mt/28023358/21656
Mute #vpp: https://lists.fd.io/mk?hashtag=vpp=1480452
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] 18.10 release artifacts

[Marco Varlese]

I am going to check with Vanessa...

On Tue, 2018-10-30 at 21:32 +, Michal Cmarada via Lists.Fd.Io
wrote:
jvpp-ioampot
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11049): https://lists.fd.io/g/vpp-dev/message/11049
Mute This Topic: https://lists.fd.io/mt/27799255/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] All VPP builds are currently failing

[Marco Varlese]

All VPP builds are currently failing.

Reported error in gerrit is "UNSTABLE"

In the logs I can see this:

11:44:47 [vpp-checkstyle-verify-master] $ /bin/bash -l
/tmp/jenkins5258297763900395189.sh
11:44:47 mesg: ttyname failed: Inappropriate ioctl for device


Cheers,
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10997): https://lists.fd.io/g/vpp-dev/message/10997
Mute This Topic: https://lists.fd.io/mt/27737775/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] #vpp

[Marco Varlese]

Hi,
On Thu, 2018-10-25 at 04:59 +, Yao, Chengqiang wrote:
> Hi Macro,
> 
>  
> 
> Is there any sample code to show how to use SCTP (such as association, packet
> transmission/reception, etc.)? And is there any performance
>  report for SCTP?
You can have a look at the test for SCTP:1) test/test_sctp.py2)
src/vnet/session-apps/echo_client.c & echo_server.c
The echo_client and echo_server are used by TCP / UDP and SCTP to exercise the
networking stack implemented.
With regards to the state-machine (I assumed that's what you're asking by
"association", "packet transmssion/reception", etc.), the whole of it is gone
through when running the tests.If you are interested in seeing/learning how
that's implemented I am afraid you need to look into the code tho.
With regards to performance: no, there're no reports. However, something can be
retrieved by running the test_sctp.py since at the end it prints out how much
data has been transferred and how long that took. 
> 
> 
>  
> 
> Best Regards,
> 
> Chengqiang Yao
Cheers,Marco
>  
>  
>  
> 
> 
> From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io]
> On Behalf Of Marco Varlese
> 
> Sent: Wednesday, October 10, 2018 5:47 PM
> 
> To: srivastava.rac...@gmail.com; vpp-dev@lists.fd.io
> 
> Subject: Re: [vpp-dev] #vpp
> 
> 
>  
> 
> Hi Srivastava,
> 
> 
>  
> 
> 
> On Wed, 2018-10-10 at 01:23 -0700, 
> srivastava.rac...@gmail.com wrote:
> 
> > Hi 
> > 
> > 
> >  
> > 
> > 
> > Does the VPP support SCTP. If yes what is the configuration for SCTP. Does
> > it support the same features as the linux kernel SCTP ?
> > 
> 
> VPP has an implementation for SCTP. You can look into /src/vnet/sctp folder to
> see what we currently support in terms of RFC.
> 
> 
> Any feedback (and contribution) is very much welcome!
> 
> 
>  
> 
> >  
> > 
> > 
> > Thanks
> > 
> > 
> > Rachit Srivastava
> > 
> 
> Thanks,
> 
> 
> Marco
> 
> 
>  
> 
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> >  
> > View/Reply Online (#10787): https://lists.fd.io/g/vpp-dev/message/10787
> > Mute This Topic: https://lists.fd.io/mt/27155313/675056
> > Mute #vpp: https://lists.fd.io/mk?hashtag=vpp=1480704
> > Group Owner: vpp-dev+ow...@lists.fd.io
> > Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [mvarl...@suse.de]
> > -=-=-=-=-=-=-=-=-=-=-=-
> >  
> 
> 
> 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10987): https://lists.fd.io/g/vpp-dev/message/10987
Mute This Topic: https://lists.fd.io/mt/27155313/21656
Mute #vpp: https://lists.fd.io/mk?hashtag=vpp=1480452
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] running VPP non-root broken

[Marco Varlese]

Hi Damjan,
On Wed, 2018-10-24 at 16:14 +0200, Damjan Marion via Lists.Fd.Io wrote:
> We merged patch which should fix things with 1G hugepages but I was not able
> to test it on arm, so please try...

Is this something which should go also on stable/1810 for a potential future dot
release?
If so could you please cherry pick it to that branch?


> -- 
> Damjan

Cheers,
Marco

> 
> 
> > On 24 Oct 2018, at 05:28, Sirshak Das  wrote:
> > 2M works but 1G still fails.
> >  
> > I toned down the dpdk resource allocation to default:
> > dpdk
> > {
> >   dev 0004:01:00.1
> >   dev 0004:01:00.2
> >   no-multi-seg
> >   log-level debug
> >   dev default
> >   {
> > num-rx-queues 1
> > # num-tx-queues 4
> > num-rx-desc 2048
> > num-tx-desc 2048
> >   }
> >   # num-mbufs 128000
> >   # socket-mem 2048,2048
> >   no-tx-checksum-offload
> >  
> > But here is the problem (for 16G of Hugepage memory):
> > With:
> > 2MB (nr_hugepages: 8192)
> > GRUB_CMDLINE_LINUX="default_hugepagesz=2M hugepagesz=1G hugepages=16
> > hugepagesz=2M hugepages=8192 iommu.passthrough=1 isolcpus=16-45
> > nohz_full=16-45 rcu_nocbs=16-45"
> > vs 1GB (nr_hugepages: 16)
> > GRUB_CMDLINE_LINUX="default_hugepagesz=1G hugepagesz=1G hugepages=16
> > hugepagesz=2M hugepages=8192 iommu.passthrough=1 isolcpus=16-45
> > nohz_full=16-45 rcu_nocbs=16-45"
> >  
> > I am getting a performance improvement of 49% when I use 1G hugepages
> > compared to 2MB.
> > I am not an expert on hugepages to pinpoint the exact reason but it will
> > surely help if you can fix the 1G hugepage issue.
> >  
> > Thank you
> > Sirshak Das 
> > From: Damjan Marion  
> > Sent: Tuesday, October 23, 2018 3:43 PM
> > To: Sirshak Das 
> > Cc: vpp-dev ; Honnappa Nagarahalli <
> > honnappa.nagaraha...@arm.com>; Lijian Zhang (Arm Technology China) <
> > lijian.zh...@arm.com>; khemendra kumar ; Juraj
> > Linkeš 
> > Subject: Re: [vpp-dev] running VPP non-root broken
> >  
> >  
> > OMG, you are good in wasting memory. 1G pages, 2G per socket given to dpdk
> > to hang empty :)
> > 128K buffers
> >  
> > For a start can you switch default page size to 2M. newer x86 kernels ignore
> > it but maybe it behaves
> > differently on aarch64...
> >  
> > In the meantime I will fix few coverity issues...
> >  
> > -- 
> > Damjan
> > 
> > 
> > > On 23 Oct 2018, at 20:45, Sirshak Das  wrote:
> > >  
> > > Hi Damjan,
> > >  
> > > I am getting the following error as well I don’t know if its related to
> > > this issue:
> > > vlib_plugin_early_init:361: plugin path
> > > /home/sirdas/code/commita/vpp/build-root/install-vpp-
> > > native/vpp/lib/vpp_plugins
> > > load_one_plugin:117: Plugin disabled (default): abf_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): acl_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): avf_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): cdp_plugin.so
> > > load_one_plugin:189: Loaded plugin: dpdk_plugin.so (Data Plane Development
> > > Kit (DPDK))
> > > load_one_plugin:117: Plugin disabled (default): flowprobe_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): gbp_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): gtpu_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): igmp_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): ila_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): ioam_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): ixge_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): l2e_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): lacp_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): lb_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): mactime_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): map_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): memif_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): nat_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): nsh_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): nsim_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): perfmon_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): pppoe_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): srv6ad_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): srv6am_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): srv6as_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): stn_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): svs_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): tlsmbedtls_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): tlsopenssl_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): unittest_plugin.so
> > > load_one_plugin:117: Plugin disabled (default): vmxnet3_plugin.so
> > > clib_elf_parse_file: open `linux-vdso.so.1': No such file or directory
> > > load_one_vat_plugin:67: 

Re: [vpp-dev] [csit-dev] VPP 18.10 is out!!!

[Marco Varlese]

Hi Jan,

Yes, I already told Vanessa... I don't know why that RPM/DEB was not included in
the first place!


Cheers,
Marco

On Wed, 2018-10-24 at 08:59 +, Jan Gelety via Lists.Fd.Io wrote:
> Hello Macro,
> 
> Great and thanks for the info!
> 
> Unfortunately, vpp-ext-deps packages are missing there [0] - is it possible to
> fix it, please?
> 
> Thanks,
> Jan
> 
> [0] https://packagecloud.io/app/fdio/release/search?q=vpp-ext-deps
> 
> -Original Message-
> From: csit-...@lists.fd.io  On Behalf Of Marco Varlese
> Sent: Wednesday, October 24, 2018 9:47 AM
> To: vpp-dev@lists.fd.io; csit-...@lists.fd.io
> Cc: t...@lists.fd.io
> Subject: [csit-dev] VPP 18.10 is out!!!
> 
> Dear all,
> 
> I am very happy to announce that release 18.10 is available.
> 
> Release artificats can be found on both Nexus and Packagecloud.
> 
> Thanks to all contributors for yet another great release!
> 
> 
> Cheers,
> --
> Marco V
> 
> SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB
> 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#3141): https://lists.fd.io/g/csit-dev/message/3141
> Mute This Topic: https://lists.fd.io/mt/27615759/675056
> Group Owner: csit-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/csit-dev/unsubb  [mvarl...@suse.de]
> -=-=-=-=-=-=-=-=-=-=-=-
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10947): https://lists.fd.io/g/vpp-dev/message/10947
Mute This Topic: https://lists.fd.io/mt/27616092/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] VPP 18.10 is out!!!

[Marco Varlese]

Dear all,

I am very happy to announce that release 18.10 is available.

Release artificats can be found on both Nexus and Packagecloud.

Thanks to all contributors for yet another great release!


Cheers,
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10938): https://lists.fd.io/g/vpp-dev/message/10938
Mute This Topic: https://lists.fd.io/mt/27615761/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] DO NOT MERGE ANY PATCHES onto stable/1810

[Marco Varlese]

TO ALL COMMITTERS:

I am in the process of cutting the 18.10 release. 

Please, do NOT merge any patches onto stable/1810 until the release has been
announced on vpp-dev@lists.fd.io


Thanks,
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10910): https://lists.fd.io/g/vpp-dev/message/10910
Mute This Topic: https://lists.fd.io/mt/27565937/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Problem downloading always VPP 19.01 instead of VPP 18.07

[Marco Varlese]

If you want to build the sources yourself then - once you have cloned the VPP
repo - you will have to checkout the correct branch for the version you're
interested in. If you simply clone the repo then the "default" branch is master
which is correctly pointing to 19.01-rc0...
If you want to checkout and eventually build v18.07.1 then do:# git checkout
v18.07.1
That will checkout the 18.07 branch at the tag 18.07.1
Once you've done that... well, it's a matter of building and running VPP.

- Marco
On Thu, 2018-10-18 at 12:05 +, Francesco Spinelli wrote:
> 
> Hello VPP experts,
> 
> 
> 
> 
> 
> I'm trying to download VPP version 18.07  but when I build it and run it, I
> notice that both VPP and the packages belong always to the 19.01 version
> 
> 
> 
> 
> 
> It happens if I download them from here, using the command: 
> 
> curl -s https://packagecloud.io/install/repositories/fdio/1807/script.deb.sh |
> sudo bash
> 
> 
> 
> 
> and when I pull VPP from gerrit:
> 
> 
> 
> 
> 
> git clone https://gerrit.fd.io/r/vpp
> 
> 
> and then buidling it.
> 
> 
> 
> 
> 
> Am I missing anything in my buildling process? How can I retrieve  18.07
> packages and avoid to use the  most recent ones?
> 
> 
> 
> 
> 
> Thanks a lot for your help,
> 
> Best Regards,
> 
> 
> 
> 
> 
> Francesco 
> 
> 
> 
> 
> 
> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-Links: You receive all messages sent to this group.
> View/Reply Online (#10868): https://lists.fd.io/g/vpp-dev/message/10868Mute
> This Topic: https://lists.fd.io/mt/27401834/675056Group Owner: vpp-
> dev+ow...@lists.fd.ioUnsubscribe: https://lists.fd.io/g/vpp-dev/unsubb  [mvarl
> e...@suse.de]-=-=-=-=-=-=-=-=-=-=-=-
-- 
Marco V


SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10869): https://lists.fd.io/g/vpp-dev/message/10869
Mute This Topic: https://lists.fd.io/mt/27401834/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] bug in api for tapv2

[Marco Varlese]

Thank you!
On Wed, 2018-10-17 at 12:18 +, Michal Cmarada via Lists.Fd.Io wrote:
> Hi Marco,
>  
> Done: 
> https://gerrit.fd.io/r/#/c/15342/
>  
> Michal
>  
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Michal Cmarada
> Engineer - Software
> mcmar...@cisco.com
> Tel:
> 
>  
>  
> 
> 
> 
> 
>  
> 
> 
> 
> 
> 
> 
> 
>  
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Cisco Systems, Inc.
>  
>  
>  
> Slovakia
> cisco.com
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Think before you print.
> 
> 
> 
> 
> This email may contain confidential and privileged material for the sole use
> of the intended recipient. Any review, use, distribution
>  or disclosure by others is strictly prohibited. If you are not the intended
> recipient (or authorized to receive for the recipient), please contact the
> sender by reply email and delete all copies of this message.
> Please
> 
> click here for Company Registration Information.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  
> 
>  
> 
> 
> From: Marco Varlese  
> 
> Sent: Wednesday, October 17, 2018 2:16 PM
> 
> To: Michal Cmarada -X (mcmarada - PANTHEON TECHNOLOGIES at Cisco) <
> mcmar...@cisco.com>; vpp-dev@lists.fd.io
> 
> Subject: Re: [vpp-dev] bug in api for tapv2
> 
> 
>  
> 
> Hi Michal,
> 
> 
>  
> 
> 
> On Wed, 2018-10-17 at 11:49 +, Michal Cmarada via Lists.Fd.Io wrote:
> 
> > Hi VPP devs,
> >  
> > I found a bug in API for tapv2. I prepared a fix but I need someone to check
> > it.
> > 
> > 
> > gerrit patch: https://gerrit.fd.io/r/#/c/15341/
> 
> Yes, your fix makes sense to me.
> 
> 
> I am waiting for the Verified+1 to merge it.
> 
> 
>  
> 
> > 
> > also it will probably need a cherry-pick to stable 18.10
> 
> Yes, it will have to be cherry-picked to stable 18.10. Can you push a patch
> there too?
> 
> 
>  
> 
> >  
> >  
> > Thanks
> >  
> > Michal
> 
> Cheers,
> 
> 
> Marco
> 
> 
>  
> 
> >  
> >  
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Michal Cmarada
> > Engineer - Software
> > mcmar...@cisco.com
> > Tel:
> > 
> >  
> >  
> > 
> > 
> > 
> > 
> >  
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >  
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Cisco Systems, Inc.
> >  
> >  
> >  
> > Slovakia
> > cisco.com
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Think before you print.
> > 
> > 
> > 
> > 
> > This email may contain confidential and privileged material for the sole use
> > of the intended recipient. Any review, use, distribution
> >  or disclosure by others is strictly prohibited. If you are not the intended
> > recipient (or authorized to receive for the recipient), please contact the
> > sender by reply email and delete all copies of this message.
> > Please
> > 
> > click here for Company Registration Information.
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >  
> >  
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> >  
> > View/Reply Online (#10854): https://lists.fd.io/g/vpp-dev/message/10854
> > Mute This Topic: https://lists.fd.io/mt/27379050/675056
> > Group Owner: vpp-dev+ow...@lists.fd.io
> > Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [mvarl...@suse.de]
> > -=-=-=-=-=-=-=-=-=-=-=-
> >  
> 
> -- 
> 
> Marco V
> 
> 
>  
> 
> SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
> 
> HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
> 
> 
> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-Links: You receive all messages sent to this group.
> View/Reply Online (#10856): https://lists.fd.io/g/vpp-dev/message/10856Mute
> This Topic: https://lists.fd.io/mt/27379050/675056Group Owner: vpp-
> dev+ow...@lists.fd.ioUnsubscribe: https://lists.fd.io/g/vpp-dev/unsubb  [mvarl
> e...@suse.de]-=-=-=-=-=-=-=-=-=-=-=-
-- 
Marco V


SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10857): https://lists.fd.io/g/vpp-dev/message/10857
Mute This Topic: https://lists.fd.io/mt/27379050/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] bug in api for tapv2

[Marco Varlese]

Hi Michal,

On Wed, 2018-10-17 at 11:49 +, Michal Cmarada via Lists.Fd.Io wrote:
> 
> 
> Hi VPP devs,
> 
>  
> 
> I found a bug in API for tapv2. I prepared a fix but I need someone to check
> it.
> 
> 
> gerrit patch: https://gerrit.fd.io/r/#/c/15341/
> 
Yes, your fix makes sense to me.
I am waiting for the Verified+1 to merge it.



also it will probably need a cherry-pick to stable 18.10
Yes, it will have to be cherry-picked to stable 18.10. Can you push a patch
there too?

 
Thanks
 
Michal
Cheers,
Marco

 
Michal Cmarada
Engineer - Software
mcmar...@cisco.com
Tel:
 
 
 
 
Cisco Systems, Inc.
 
 
 
Slovakia
cisco.com
Think before you print.
This email may contain confidential and privileged material for the sole use of 
the intended recipient. Any review, use, distribution
 or disclosure by others is strictly prohibited. If you are not the intended 
recipient (or authorized to receive for the recipient), please contact the 
sender by reply email and delete all copies of this message.
Please

click here for Company Registration Information.
 
 



> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#10854): https://lists.fd.io/g/vpp-dev/message/10854
> Mute This Topic: https://lists.fd.io/mt/27379050/675056
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [mvarl...@suse.de]
> -=-=-=-=-=-=-=-=-=-=-=-
> 
-- 
Marco V


SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10855): https://lists.fd.io/g/vpp-dev/message/10855
Mute This Topic: https://lists.fd.io/mt/27379050/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] VPP 18.10 RC2 milestone complete!!!

[Marco Varlese]

Dear all,

I have created the v18.10-rc2 tag on stable/1810. 
VPP 18.10 Release Milestone RC2 is complete!

As a reminder, the VPP 18.10 Final Release is in one week:
Wednesday October 24, 2018.

It is important that only bugs which address critical issues (as determined by
the VPP committers), ideally limited to addressing bugs found by CSIT testing,
are pushed to stable now.

Per the standard process, all bug fixes to stable branches should follow the
best practices:
* All bug fixes must be double-committed to the release throttle as well as to
the master branch
* Commit first to the release throttle, then "git cherry-pick" into master

All bug fixes need to have a Jira ticket. Please put Jira IDs into the commit
messages. Please use the same Jira ID for both the stable branch and master.


Thanks and regards,
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10852): https://lists.fd.io/g/vpp-dev/message/10852
Mute This Topic: https://lists.fd.io/mt/27378265/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Outstanding coverity scan warnings

[Marco Varlese]

Dear all,

Please, take a moment to either fix or dismiss (in coverity) the warnings
highlighted by the tool.

There are currently 7 outstanding difects; the affected areas are:
* plugins/memif/device.c
* vnet/vxlan-gpe/encap.c
* plugins/nsh/nsh.c
* vppinfra/linux/mem.c

When fixing any of the above issues, please, cherry-pick your patch to
stable/1810 as well!


Thanks,
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10832): https://lists.fd.io/g/vpp-dev/message/10832
Mute This Topic: https://lists.fd.io/mt/27368350/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] VPP 18.10 RC2 milestone is on Wed 17th Oct

[Marco Varlese]

Dear all,

Gentle reminder that VPP 18.10 -rc2 milestone is on Wed 17th Oct.


Thanks and regards,
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10815): https://lists.fd.io/g/vpp-dev/message/10815
Mute This Topic: https://lists.fd.io/mt/27327231/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] VPP 18.10 RC1 milestone is complete! [UPDATE]

[Marco Varlese]

Folks,

On Wed, 2018-10-10 at 15:39 +0200, Marco Varlese wrote:
> Dear all,
> 
> The VPP 18.10 RC1 milestone is complete. 
> 
> The VPP 18.10 release branch (stable/1810) has been created, along with the
> associated nexus and packagecloud repo's.
> 
> VPP master branch is now open for all patches slated for VPP 19.01 (and
> beyond).
> VPP stable/1810 is open for bug-fix patches only. 
> 
> Per the standard process, all bug fixes to the stable branch should follow the
> best practices:
> 1) All bug fixes must be double-committed to the release throttle as well as
> to
> the master branch:
>   a) Commit first to the release throttle, then "git cherry-pick" into master
>   b) Manual merges may be required, depending on the degree of divergence
> between throttle and master
> 2) All bug fixes need to have a Jira ticket:
>   a) Please put Jira IDs into the commit messages.
>   b) Please use the same Jira ID for both the stable branch and master.
> 
> There is one small issue left to be fixed, which is currently affecting the
> Nexus repositories hence the uploading of DEBs/RPMs. This should be fixed
> soon.
> On the other hand, packagecloud.io repo is working perfectly 
> https://packagecloud.io/fdio/1810
All issues connected to packages generation and upload on both Nexus and
Packagecloud have been resolved.
If you had any patch failing verification on stable/1810, please, just rebase it
and wait for the verification process to finish.
> 
> 
> Thanks and regards,
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#10794): https://lists.fd.io/g/vpp-dev/message/10794
> Mute This Topic: https://lists.fd.io/mt/27156944/675056
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsubb  [mvarl...@suse.de]
> -=-=-=-=-=-=-=-=-=-=-=-
Cheers,
Marco


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10805): https://lists.fd.io/g/vpp-dev/message/10805
Mute This Topic: https://lists.fd.io/mt/27267857/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Verification always fail with stable/1801

[Marco Varlese]

Yes, there's troubles with 2 things:1) package naming2) packagecloud bionic
"repo"
Both things are getting addressed.
HTH,Marco
On Thu, 2018-10-11 at 15:00 +, John Lo (loj) via Lists.Fd.Io wrote:
> It seems verifications are always failing for patches on stable/1801 branch. 
> Does anyone know why?
> The following patch with a simple one line change is an example which fails
> all 3 verification attempts:
> https://gerrit.fd.io/r/#/c/15222/
>  
> Regards,
> John
> 
> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-Links: You receive all messages sent to this group.
> View/Reply Online (#10799): https://lists.fd.io/g/vpp-dev/message/10799Mute
> This Topic: https://lists.fd.io/mt/27242615/675056Group Owner: vpp-
> dev+ow...@lists.fd.ioUnsubscribe: https://lists.fd.io/g/vpp-dev/unsubb  [mvarl
> e...@suse.de]-=-=-=-=-=-=-=-=-=-=-=-
-- 
Marco V


SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10800): https://lists.fd.io/g/vpp-dev/message/10800
Mute This Topic: https://lists.fd.io/mt/27242615/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] VPP 18.10 RC1 milestone is complete!

[Marco Varlese]

Dear all,

The VPP 18.10 RC1 milestone is complete. 

The VPP 18.10 release branch (stable/1810) has been created, along with the
associated nexus and packagecloud repo's.

VPP master branch is now open for all patches slated for VPP 19.01 (and beyond).
VPP stable/1810 is open for bug-fix patches only. 

Per the standard process, all bug fixes to the stable branch should follow the
best practices:
1) All bug fixes must be double-committed to the release throttle as well as to
the master branch:
  a) Commit first to the release throttle, then "git cherry-pick" into master
  b) Manual merges may be required, depending on the degree of divergence
between throttle and master
2) All bug fixes need to have a Jira ticket:
  a) Please put Jira IDs into the commit messages.
  b) Please use the same Jira ID for both the stable branch and master.

There is one small issue left to be fixed, which is currently affecting the
Nexus repositories hence the uploading of DEBs/RPMs. This should be fixed soon.
On the other hand, packagecloud.io repo is working perfectly 
https://packagecloud.io/fdio/1810


Thanks and regards,
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10794): https://lists.fd.io/g/vpp-dev/message/10794
Mute This Topic: https://lists.fd.io/mt/27156944/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] #vpp

[Marco Varlese]

Hi Srivastava,
On Wed, 2018-10-10 at 01:23 -0700, srivastava.rac...@gmail.com wrote:
> Hi 
> 
>  
> 
> Does the VPP support SCTP. If yes what is the configuration for SCTP. Does it
> support the same features as the linux kernel SCTP ?
VPP has an implementation for SCTP. You can look into /src/vnet/sctp folder to
see what we currently support in terms of RFC.Any feedback (and contribution) is
very much welcome!
>  
> 
> Thanks
> 
> Rachit Srivastava
Thanks,Marco
> -=-=-=-=-=-=-=-=-=-=-=-Links: You receive all messages sent to this group.
> View/Reply Online (#10787): https://lists.fd.io/g/vpp-dev/message/10787Mute
> This Topic: https://lists.fd.io/mt/27155313/675056Mute #vpp: 
> https://lists.fd.io/mk?hashtag=vpp=1480704Group Owner: vpp-
> dev+ow...@lists.fd.ioUnsubscribe: https://lists.fd.io/g/vpp-dev/unsubb  [mvarl
> e...@suse.de]-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10788): https://lists.fd.io/g/vpp-dev/message/10788
Mute This Topic: https://lists.fd.io/mt/27155313/21656
Mute #vpp: https://lists.fd.io/mk?hashtag=vpp=1480452
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] VPP Release 18.10: RC1 is today!!!

[Marco Varlese]

Dear all,

A gentle reminder that RC1 branch is happening today [1]!!!

[1] https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_18.10


Thanks and regards,
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10784): https://lists.fd.io/g/vpp-dev/message/10784
Mute This Topic: https://lists.fd.io/mt/27155040/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] VPP Release 18.10: RC1 is tomorrow!!!

[Marco Varlese]

Dear all,

Gentle reminder about -RC1 deadline happening tomorrow [1].

[1] https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_18.10


Regards,
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10772): https://lists.fd.io/g/vpp-dev/message/10772
Mute This Topic: https://lists.fd.io/mt/27119694/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Outstanding coverity scan warnings for 18.10

[Marco Varlese]

Dear all,

I would like to ask all of you to, please, take some time to review the
outstanding coverity scan warnings and triage them.

Areas of interest are:
* MEMIF
* NSH plugin
* VXLAN
* VXLAN-GPE
* API
* PROMETHEUS


Thanks and regards,
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10766): https://lists.fd.io/g/vpp-dev/message/10766
Mute This Topic: https://lists.fd.io/mt/26872018/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] VPP Release 18.10: RC1 in a week!!!

[Marco Varlese]

Dear all,

A reminder that the RC1 branch is in one week [1]!!! 
We’re still accepting low-risk patches on master ahead of the branch.

[1] https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_18.10


Thanks and regards,
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10735): https://lists.fd.io/g/vpp-dev/message/10735
Mute This Topic: https://lists.fd.io/mt/26715883/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] VPP Release 18.10: F0 has arrived

[Marco Varlese]

Dear all,

F0 [1] has finally arrived. That marks the API freeze deadline.

Only low-risk changes will be accepted on main branch until it will reopen for
business (a separate email will announce that).

[1] https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_18.10


Thanks and regards,
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10734): https://lists.fd.io/g/vpp-dev/message/10734
Mute This Topic: https://lists.fd.io/mt/26715799/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] VPP Release 18.10 (F0): few days left

[Marco Varlese]

Dear all,

This is just a gentle reminder that we have just few days left for F0 [1].

Please, make sure you have your patches with API changes merged before the
deadline (Oct 3rd).

[1] https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_18.10


Thanks and regards,
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10703): https://lists.fd.io/g/vpp-dev/message/10703
Mute This Topic: https://lists.fd.io/mt/26375436/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] VPP Release 18.10: API freeze (F0) is next week

[Marco Varlese]

Dear all,

F0 deadline is next week (2018-10-03)!!!

As of today, there is a substantial list of API changes which are pending merge
in gerrit. Some of them have merge-conflict which needs author's attention.

Please, remember that no API changes will be allowed after F0 deadline (2018-10-
03) so let's get your API patches in soon. Refer to [1] for
deliverables/milestones.

@committers: please, provide feedback/help in a timely manner so to have API
changes accepted before the deadline.

[1]: https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_18.10


Thanks and regards,
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10619): https://lists.fd.io/g/vpp-dev/message/10619
Mute This Topic: https://lists.fd.io/mt/26198047/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] VPP Release 18.10 (F0): 2 weeks notice reminder

[Marco Varlese]

Dear all,

I would like to remind you that API freeze (F0) for release 18.10 is exactly
in 2 weeks from now. If you are not aware yet of the release schedule, please,
take a moment to familiarize yourself with it by visiting [1]. 
 
Please, whilst I do my best to review the submitted code, be proactive and
highlight to me any API changes - in your patches - which break backward
compatibility with previous API version (released with 18.07).

I look forward to your input and collaboration for yet another great VPP
release!
 
[1] https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_18.10


Thanks and regards,
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10562): https://lists.fd.io/g/vpp-dev/message/10562
Mute This Topic: https://lists.fd.io/mt/25753275/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Difference between python api and vppctl result - stats

[Marco Varlese]

On Mon, 2018-09-17 at 20:33 +0200, Ole Troan wrote:
> Marco,
> 
> > > > Which version of vpp python api does include this stats api?
> > > > I tried it at vpp stable/1807, but there was no VPPStats module in it!
> > > 
> > > Going in 18.10. I recommend latest master for now. 
> > 
> > Great! Any chances to see it added to the wiki page for 18.10? 
> > https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_18.10
> 
> Now there is a probability near 1 that you will see it on the wiki page! ;-)
Thanks :)
> 
> Best regards,
> Ole
> 
> > > > 
> > > > On Mon, Sep 17, 2018 at 11:45 AM Ole Troan  wrote:
> > > > > Brayan,
> > > > > 
> > > > > > I would like to share my problem with you in order to find solution.
> > > > > > As you can see in vppctl output file, "vppctl show hardware" command
> > > > > > result contains "rx broadcast packets" and "tx broadcast packets".
> > > > > > However, when I used vpp python api to extract these stats, the
> > > > > > value of VNET_INTERFACE_COUNTER_RX_BROADCAST and
> > > > > > VNET_INTERFACE_COUNTER_TX_BROADCAST are stuck on zero incorrectly.
> > > > > > attached you can see my python script and its output and vppctl
> > > > > > command output. This behavior exists in multicast stats.
> > > > > > 
> > > > > > Best Regards,
> > > > > > 
> > > > > > 
> > > > > > vppctl output: https://pastebin.com/zXrArE4b
> > > > > > Python Script: https://pastebin.com/gDJbH1if
> > > > > > Python Script output: https://pastebin.com/q4dJ8VMs
> > > > > 
> > > > > Firstly these are not exactly the same counters. The first ones come
> > > > > directly from DPDK I believe, and the VNET_INTERFACE_COUNTER ones are
> > > > > from the stats_collect_rx_node, sitting as an input feature behind
> > > > > device-input.
> > > > > I don’t know if they are different because the broadcasts are filtered
> > > > > out before reaching VPP or if there is a better explanation, Damjan?
> > > > > 
> > > > > With regards to Python and stats collection, or any stats collection
> > > > > in general. I would encourage you to try out the new stats segment.
> > > > > 
> > > > > In Python you basically do:
> > > > > 
> > > > > from vpp_papi.vpp_stats import VPPStats
> > > > > stat = VPPStats( > > > > dir = stat.ls(['^/if’]) # For all interface counters use “show
> > > > > statistics segment” or vpp_get_stats ls to see all available counters
> > > > > counters = stat.dump(dir)
> > > > > 
> > > > > Then counters[‘/if/tx'][thread index][sw_if_index] will give you the
> > > > > TX counter for a particular worker thread / software interface.
> > > > > 
> > > > > Cheers,
> > > > > Ole
> > > > > 
> > > > > 
> > > > > 
> > > > 
> > > > -=-=-=-=-=-=-=-=-=-=-=-
> > > > Links: You receive all messages sent to this group.
> > > > 
> > > > View/Reply Online (#10515): https://lists.fd.io/g/vpp-dev/message/10515
> > > > Mute This Topic: https://lists.fd.io/mt/25704565/675193
> > > > Group Owner: vpp-dev+ow...@lists.fd.io
> > > > Unsubscribe: https://lists.fd.io/g/vpp-dev/unsubb  [otr...@employees.org
> > > > ]
> > > > -=-=-=-=-=-=-=-=-=-=-=-
> > > 
> > > -=-=-=-=-=-=-=-=-=-=-=-
> > > Links: You receive all messages sent to this group.
> > > 
> > > View/Reply Online (#10516): https://lists.fd.io/g/vpp-dev/message/10516
> > > Mute This Topic: https://lists.fd.io/mt/25704565/675056
> > > Group Owner: vpp-dev+ow...@lists.fd.io
> > > Unsubscribe: https://lists.fd.io/g/vpp-dev/unsubb  [mvarl...@suse.de]
> > > -=-=-=-=-=-=-=-=-=-=-=-
> > > 
> > 
> > -- 
> > Marco V
> > 
> > SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
> > HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#10527): https://lists.fd.io/g/vpp-dev/message/10527
> Mute This Topic: https://lists.fd.io/mt/25704565/675056
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsubb  [mvarl...@suse.de]
> -=-=-=-=-=-=-=-=-=-=-=-
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10530): https://lists.fd.io/g/vpp-dev/message/10530
Mute This Topic: https://lists.fd.io/mt/25704565/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Difference between python api and vppctl result - stats

[Marco Varlese]

On Mon, 2018-09-17 at 13:00 +0200, Ole Troan wrote:
Brayan,

Which version of vpp python api does include this stats api?
I tried it at vpp stable/1807, but there was no VPPStats module in it!

Going in 18.10. I recommend latest master for now. 
Great! Any chances to see it added to the wiki page for 18.10? 
https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_18.10

> 
> Cheers 
> Ole
Thanks,
Marco




On Mon, Sep 17, 2018 at 11:45 AM Ole Troan  wrote:
Brayan,


> I would like to share my problem with you in order to find solution.

> As you can see in vppctl output file, "vppctl show hardware" command result 
> contains "rx broadcast packets" and "tx broadcast packets". However, when I 
> used vpp python api to extract these stats, the value of 
> VNET_INTERFACE_COUNTER_RX_BROADCAST and VNET_INTERFACE_COUNTER_TX_BROADCAST 
> are stuck on zero incorrectly. attached you can see my python script and its 
> output and vppctl command output. This behavior exists in multicast stats.

> 

> Best Regards,

> 

> 

> vppctl output: https://pastebin.com/zXrArE4b

> Python Script: https://pastebin.com/gDJbH1if

> Python Script output: https://pastebin.com/q4dJ8VMs


Firstly these are not exactly the same counters. The first ones come directly 
from DPDK I believe, and the VNET_INTERFACE_COUNTER ones are from the 
stats_collect_rx_node, sitting as an input feature behind device-input.

I don’t know if they are different because the broadcasts are filtered out 
before reaching VPP or if there is a better explanation, Damjan?


With regards to Python and stats collection, or any stats collection in 
general. I would encourage you to try out the new stats segment.


In Python you basically do:


from vpp_papi.vpp_stats import VPPStats

stat = VPPStats(https://lists.fd.io/g/vpp-dev/message/10515
Mute This Topic: https://lists.fd.io/mt/25704565/675193
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [otr...@employees.org]
-=-=-=-=-=-=-=-=-=-=-=-
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#10516): https://lists.fd.io/g/vpp-dev/message/10516
> Mute This Topic: https://lists.fd.io/mt/25704565/675056
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [mvarl...@suse.de]
> -=-=-=-=-=-=-=-=-=-=-=-
> 
-- 
Marco V


SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10524): https://lists.fd.io/g/vpp-dev/message/10524
Mute This Topic: https://lists.fd.io/mt/25704565/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] build queue backed up a bit foo

[Marco Varlese]

Obviously I meant "does NOT add any meaningful insight..."
On Mon, 2018-09-10 at 16:48 +0200, Marco Varlese wrote:
> On Mon, 2018-09-10 at 14:29 +, Ed Kern (ejk) wrote:
> > At least three different possible actions to take at this point:  (outside
> > of fixing the issue)
> > 
> > 
> > 
> > 
> > 1. remove make test attempt from arm build (return it to the way it was
> > before a week ago).
> > 
> > 2. lower timeout further my first thought would be in the 75 minute range
> > (from 120)
> I don't like this option mainly because it would still imply that developers
> will have to wait for 75 minutes to see a patch verified... The worst is that
> the job is a non-voting one hence having it running does add any meaningful
> insight into the build result. I'm in favour for the issue being resolved in
> the sandbox and eventually moved to production when stable.
> > 3. remove job altogether.
> I believe this should be the option to purse unless it could be fixed
> quickly.As it is it only causes delays to the overall build / review / merging
> process... 
> > 
> > 
> > Im happy to push a patch that accomplishes the above or other options I
> > haven’t thought of
> > for this mail.
> > 
> > 
> > 
> > Just let me know..
> > 
> > 
> > 
> > Ed
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > > On Sep 10, 2018, at 4:31 AM, Marco Varlese  wrote:
> > > 
> > > Last
> > >  example (today) can be found here
> > > 
> > > 
> > > 
> > > 10:47:06
> > >  Not running extended tests (some tests will be skipped)
> > > 
> > > 10:47:06
> > >  Perform 4 attempts to pass the suite...
> > > 
> > > 10:47:10
> > >  *** Error in `python': double free or corruption (out):
> > > 
> > > 0x75d483f0
> > >  ***
> > > 
> > > 12:27:54
> > >  Build timed out (after 120 minutes). Marking the build as failed.
> > > 
> > > 
> > > 
> > > Patch: https://gerrit.fd.io/r/#/c/14744/
> > > 
> > > 
> > > 
> > > Other
> > >  jobs have finished more than one and half-hour ago and the patch cannot
> > > be
> > > 
> > > marked
> > >  Verified+1 because Jenkins is still waiting for the ARM job to complete
> > > 
> > > (timeout
> > >  = 120 minutes). IMHO it makes the overall patch submission and review
> > > 
> > > very
> > >  painful for authors and commiters. 
> > > 
> > > 
> > > 
> > > I
> > >  would recommend (it has been done in the past for other jobs) to disable
> > > this
> > > 
> > > job
> > >  in production, move it again to sandbox, get it fixed and eventually
> > > moved
> > > 
> > > again
> > >  to production...
> > > 
> > > 
> > > 
> > > -
> > >  Marco
> > > 
> > > 
> > > 
> > > On
> > >  Fri, 2018-09-07 at 12:04 -0700, Florin Coras wrote:
> > > 
> > > > ARM jobs have not been working for some days now. That’s why their
> > > > result is
> > > > 
> > > > skipped. Timeout is 2h but probably we should drop that even further … 
> > > > 
> > > > 
> > > > 
> > > > Florin
> > > > 
> > > > 
> > > > 
> > > > > On Sep 7, 2018, at 11:59 AM, Ole Troan  wrote:
> > > > > 
> > > > > Trying out a change in:
> > > > > 
> > > > > https://gerrit.fd.io/r/#/c/14732/
> > > > > 
> > > > > 
> > > > > 
> > > > > All others succeed but ARM this doesn’t look too good.
> > > > > 
> > > > > Stuck apparently.
> > > > > 
> > > > > 
> > > > > 
> > > > > 
https://jenkins.fd.io/job/vpp-arm-verify-master-ubuntu1604/2157/console
> > > > > 
> > > > > 20:16:04 
> > > > > 
> > > > > ==
> > > > > ==
> > > > > 
> > > > > ==
> > > > > 
> > > > > 
> > > > > 
> > > > > 20:16:04 
> > > > > 
> > > > > ARP Test Case 
> > > &g

Re: [vpp-dev] build queue backed up a bit foo

[Marco Varlese]

On Mon, 2018-09-10 at 14:29 +, Ed Kern (ejk) wrote:
> At least three different possible actions to take at this point:  (outside of
> fixing the issue)
> 
> 
> 
> 
> 1. remove make test attempt from arm build (return it to the way it was before
> a week ago).
> 
> 2. lower timeout further my first thought would be in the 75 minute range
> (from 120)
I don't like this option mainly because it would still imply that developers
will have to wait for 75 minutes to see a patch verified... The worst is that
the job is a non-voting one hence having it running does add any meaningful
insight into the build result. I'm in favour for the issue being resolved in the
sandbox and eventually moved to production when stable.
> 3. remove job altogether.
I believe this should be the option to purse unless it could be fixed quickly.As
it is it only causes delays to the overall build / review / merging process... 
> 
> 
> Im happy to push a patch that accomplishes the above or other options I
> haven’t thought of
> for this mail.
> 
> 
> 
> Just let me know..
> 
> 
> 
> Ed
> 
> 
> 
> 
> 
> 
> 
> 
> > On Sep 10, 2018, at 4:31 AM, Marco Varlese  wrote:
> > 
> > Last
> >  example (today) can be found here
> > 
> > 
> > 
> > 10:47:06
> >  Not running extended tests (some tests will be skipped)
> > 
> > 10:47:06
> >  Perform 4 attempts to pass the suite...
> > 
> > 10:47:10
> >  *** Error in `python': double free or corruption (out):
> > 
> > 0x75d483f0
> >  ***
> > 
> > 12:27:54
> >  Build timed out (after 120 minutes). Marking the build as failed.
> > 
> > 
> > 
> > Patch: https://gerrit.fd.io/r/#/c/14744/
> > 
> > 
> > 
> > Other
> >  jobs have finished more than one and half-hour ago and the patch cannot be
> > 
> > marked
> >  Verified+1 because Jenkins is still waiting for the ARM job to complete
> > 
> > (timeout
> >  = 120 minutes). IMHO it makes the overall patch submission and review
> > 
> > very
> >  painful for authors and commiters. 
> > 
> > 
> > 
> > I
> >  would recommend (it has been done in the past for other jobs) to disable
> > this
> > 
> > job
> >  in production, move it again to sandbox, get it fixed and eventually moved
> > 
> > again
> >  to production...
> > 
> > 
> > 
> > -
> >  Marco
> > 
> > 
> > 
> > On
> >  Fri, 2018-09-07 at 12:04 -0700, Florin Coras wrote:
> > 
> > > ARM jobs have not been working for some days now. That’s why their result
> > > is
> > > 
> > > skipped. Timeout is 2h but probably we should drop that even further … 
> > > 
> > > 
> > > 
> > > Florin
> > > 
> > > 
> > > 
> > > > On Sep 7, 2018, at 11:59 AM, Ole Troan  wrote:
> > > > 
> > > > Trying out a change in:
> > > > 
> > > > https://gerrit.fd.io/r/#/c/14732/
> > > > 
> > > > 
> > > > 
> > > > All others succeed but ARM this doesn’t look too good.
> > > > 
> > > > Stuck apparently.
> > > > 
> > > > 
> > > > 
> > > > https://jenkins.fd.io/job/vpp-arm-verify-master-ubuntu1604/2157/console
> > > > 
> > > > 20:16:04 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > ==
> > > > 
> > > > 
> > > > 
> > > > 20:16:04 
> > > > 
> > > > ARP Test Case 
> > > > 
> > > > 
> > > > 
> > > > 20:16:04 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > ==
> > > > 
> > > > 
> > > > 
> > > > 20:16:07 
> > > > 
> > > > *** Error in `python': free(): invalid pointer: 0x553263a8 ***
> > > > 
> > > > 
> > > > 
> > > > 20:16:09 
> > > > 
> > > > ARP
> > > >  OK
> > > > 
> > > > 
> > > > 
> > > > 20:16:09 
> > > > 
> > > > ARP Duplicates
> > > >   

Re: [vpp-dev] build queue backed up a bit foo

[Marco Varlese]

Last example (today) can be found here

10:47:06 Not running extended tests (some tests will be skipped)
10:47:06 Perform 4 attempts to pass the suite...
10:47:10 *** Error in `python': double free or corruption (out):
0x75d483f0 ***
12:27:54 Build timed out (after 120 minutes). Marking the build as failed.

Patch: https://gerrit.fd.io/r/#/c/14744/

Other jobs have finished more than one and half-hour ago and the patch cannot be
marked Verified+1 because Jenkins is still waiting for the ARM job to complete
(timeout = 120 minutes). IMHO it makes the overall patch submission and review
very painful for authors and commiters. 

I would recommend (it has been done in the past for other jobs) to disable this
job in production, move it again to sandbox, get it fixed and eventually moved
again to production...

- Marco

On Fri, 2018-09-07 at 12:04 -0700, Florin Coras wrote:
> ARM jobs have not been working for some days now. That’s why their result is
> skipped. Timeout is 2h but probably we should drop that even further … 
> 
> Florin
> 
> > On Sep 7, 2018, at 11:59 AM, Ole Troan  wrote:
> > Trying out a change in:
> > https://gerrit.fd.io/r/#/c/14732/
> > 
> > All others succeed but ARM this doesn’t look too good.
> > Stuck apparently.
> > 
> > https://jenkins.fd.io/job/vpp-arm-verify-master-ubuntu1604/2157/console
> > 20:16:04 
> > 
> > ==
> > 
> > 20:16:04 
> > ARP Test Case 
> > 
> > 20:16:04 
> > 
> > ==
> > 
> > 20:16:07 
> > *** Error in `python': free(): invalid pointer: 0x553263a8 ***
> > 
> > 20:16:09 
> > ARP  OK
> > 
> > 20:16:09 
> > ARP Duplicates   OK
> > 
> > 20:16:09 
> > test_arp_incomplete (test_neighbor.ARPTestCase)  OK
> > 
> > 20:16:09 
> > ARP Static   OK
> > 
> > 20:16:15 
> > ARP reply with VRRP virtual src hw addr  OK
> > 
> > 20:16:15 
> > GARP OK
> > 
> > 20:16:15 
> > MPLS OK
> > 
> > 
> > Cheers,
> > Ole
> > 
> > 
> > > On 7 Sep 2018, at 18:50, Ole Troan  wrote:
> > > 
> > > Ed,
> > > 
> > > Let me take a closer look at these.
> > > It appears if VPP is slow to start it might not have created the socket
> > > yet. Let me try to put in a retry loop and see if that fixes verify. 
> > > 
> > > Cheers 
> > > Ole
> > > 
> > > On 7 Sep 2018, at 18:06, Ed Kern via Lists.Fd.Io <
> > > ejk=cisco@lists.fd.io> wrote:
> > > 
> > > > make test failures due to the below causing pretty consistent failures. 
> > > > Note:  For whatever reason the failures are not 100%. 
> > > > The failures and with the retries on nonconcurrent merge jobs may lead
> > > > to long build queues.   
> > > > 
> > > > These are not infra issues but ill be keeping an eye on it.
> > > > 
> > > > 
> > > > Ed
> > > > 
> > > > 
> > > > 
> > > > 13:08:25 
> > > > Using /var/cache/vpp/python/virtualenv/lib/python2.7/site-packages
> > > > 
> > > > 13:08:25 
> > > > Finished processing dependencies for vpp-papi==1.6.1
> > > > 
> > > > 13:08:27 
> > > > Traceback (most recent call last):
> > > > 
> > > > 13:08:27 
> > > >  File "sanity_run_vpp.py", line 21, in 
> > > > 
> > > > 13:08:27 
> > > >tc.setUpClass()
> > > > 
> > > > 13:08:27 
> > > >  File "/w/workspace/vpp-merge-master-ubuntu1604/test/framework.py", line
> > > > 394, in setUpClass
> > > > 
> > > > 13:08:27 
> > > >cls.statistics = VPPStats(socketname=cls.tempdir+'/stats.sock')
> > > > 
> > > > 13:08:27 
> > > >  File "build/bdist.linux-x86_64/egg/vpp_papi/vpp_stats.py", line 117, in
> > > > __init__
> > > > 
> > > > 13:08:27 
> > > > IOError
> > > > 
> > > > 13:08:27 
> > > > ***
> > > > 
> > > > 13:08:27 
> > > > * Sanity check failed, cannot run vpp
> > > > 
> > > > 13:08:27
> > > > ***
> > > > 
> > > > -=-=-=-=-=-=-=-=-=-=-=-
> > > > Links: You receive all messages sent to this group.
> > > > 
> > > > View/Reply Online (#10432): https://lists.fd.io/g/vpp-dev/message/10432
> > > > Mute This Topic: https://lists.fd.io/mt/25308161/675193
> > > > Group Owner: vpp-dev+ow...@lists.fd.io
> > > > Unsubscribe: https://lists.fd.io/g/vpp-dev/unsubb  [otr...@employees.org
> > > > ]
> > > > -=-=-=-=-=-=-=-=-=-=-=-
> > > -=-=-=-=-=-=-=-=-=-=-=-
> > > Links: You receive all messages sent to this group.
> > > 
> > > View/Reply Online (#10435): https://lists.fd.io/g/vpp-dev/message/10435
> > > Mute This Topic: https://lists.fd.io/mt/25308161/675193
> > > Group Owner: vpp-dev+ow...@lists.fd.io
> > > 

Re: [vpp-dev] cmake is on

[Marco Varlese]

Please, take a look at my patch just pushed...https://gerrit.fd.io/r/#/c/14716/
On Fri, 2018-09-07 at 10:44 +0200, Damjan Marion wrote:
> Folks,
> I'm going to revert this change, as it breaks compilation on non-cavium
> systems.
> That patch wrongly changes default cacheline size for all AArch64 platforms to
> 128 bytes...
> 
> -- 
> Damjan
> 
> 
> 
> > On 6 Sep 2018, at 15:52, Nitin Saxena  wrote:
> > 
> > 
> >   
> > 
> >   
> >   Thanks Marco, Damjan. Adding cpu id fixes the compilationPushed the patch:
> > https://gerrit.fd.io/r/#/c/14701/Thanks,
> > 
> > Nitin
> > 
> > 
> > 
> > 
> > On Thursday 06 September 2018 07:06 PM,
> >   Damjan Marion wrote:
> > 
> > 
> > 
> > >   External Email
> > >   
> > > 
> > > 
> > > 
> > > Dear Nitin,
> > > 
> > > 
> > > 
> > > Yes, it is missing.  I took care only for platforms I have
> > >   access to...
> > > 
> > >   
> > > 
> > >   — 
> > > Damjan
> > >   
> > >   
> > > 
> > > On 6 Sep 2018, at 14:04, Nitin Saxena  > > >
> > > wrote:
> > > 
> > > 
> > > 
> > >   
> > >   
> > > > Hi Damjan,cmake is making Cavium's OCTEONTx build failure.
> > > > Following is the failure
> > > > log
> > > > 
> > > >   In function ‘dpdk_init’:
> > > > 
> > > > /home/nsaxena/vpp/src/plugins/dpdk/device/init.c:1802:3:
> > > > error: static assertion failed: "DPDK RTE CACHE LINE
> > > > SIZE does not match with
> > > > 1< > > > 
> > > >STATIC_ASSERT (RTE_CACHE_LINE_SIZE == 1 <<
> > > > CLIB_LOG2_CACHE_LINE_BYTES,=
> > > > ==I am failing to see translation of
> > > > Autoconf changes
> > > > from commit id: 473f46135c3fd77dad5614215cc279b1164e9a74
> > > > to CMake.Thanks,Nitin
> > > > 
> > > >   
> > > >   On Sunday 02 September 2018
> > > > 06:18 PM, Damjan Marion via Lists.Fd.Io wrote:
> > > > 
> > > >   
> > > >   
> > > > > External Email
> > > > > 
> > > > >   
> > > > > 
> > > > >   
> > > > >   Dear all,
> > > > >   
> > > > > 
> > > > >   
> > > > >   We just switched from autotools to cmake
> > > > > and retired all autotools related files in src/.
> > > > >   
> > > > > 
> > > > >   
> > > > >   All verify jobs are ok, and we also
> > > > > tried it on 3 different x86 and 2 different ARM
> > > > > Aarch64 machines.
> > > > >   
> > > > > 
> > > > >   
> > > > >   Due to blast radius, i will not be
> > > > > surprised that some small issues pop out, but i
> > > > > don't expect anything hard to fix.
> > > > >   
> > > > > 
> > > > >   
> > > > >   Let us know if you hit something...
> > > > >   
> > > > > 
> > > > >   
> > > > >   PS As a part of this change, CentOS 7
> > > > > build are now using devtoolset-7, so they are
> > > > > compiled with gcc-7, which also means images have
> > > > > support for Skylake Servers (AVX512).
> > > > >   
> > > > > 
> > > > > 
> > > > >   
> > > > > -- 
> > > > > 
> > > > > Damjan
> > > > > 
> > > > > 
> > > > > 
> > > > >   
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > -=-=-=-=-=-=-=-=-=-=-=-Links: You receive all messages
> > > > > sent to this group.
> > > > > View/Reply Online (#10337): 
> > > > > https://lists.fd.io/g/vpp-dev/message/10337Mute This Topic: 
> > > > > https://lists.fd.io/mt/25155374/675748Group Owner: vpp-
> > > > > dev+ow...@lists.fd.ioUnsubscribe: https://lists.fd.io/g/vpp-dev/unsubb
> > > > >   [nsax...@caviumnetworks.com]-=-=-=-=-=-=-=-=-=-=-=-
> > > > > 
> > > > >   
> > > > 
> > > >   
> > > > 
> > > > 
> > > >   
> > > 
> > >   
> > > > -=-=-=-=-=-=-=-=-=-=-=-
> > > > 
> > > >   Links: You receive all messages sent to this group.
> > > > 
> > > >   
> > > > 
> > > >   View/Reply Online (#10407): 
> > > >   

Re: [vpp-dev] cmake is on

[Marco Varlese]

Hi Nitin,
On Thu, 2018-09-06 at 18:34 +0530, Nitin Saxena wrote:
> Hi Damjan,
> 
> cmake is making Cavium's OCTEONTx build failure. Following is the
>   failure log
> 
> 
> 
> 
> 
> In function ‘dpdk_init’:
> 
>   /home/nsaxena/vpp/src/plugins/dpdk/device/init.c:1802:3: error:
>   static assertion failed: "DPDK RTE CACHE LINE SIZE does not match
>   with 1< 
>  STATIC_ASSERT (RTE_CACHE_LINE_SIZE == 1 <<
>   CLIB_LOG2_CACHE_LINE_BYTES,

I believe there's a missing CPU_TYPE detection in here "src/cmake/cpu.cmake"I
don't have an OCTEONTX machine to check so if you can provide them (or submit a
patch with those) I think that could fix it...
> ===
> 
> I am failing to see translation of Autoconf changes from commit
>   id: 473f46135c3fd77dad5614215cc279b1164e9a74 to CMake.
> 
> Thanks,
> 
> Nitin
> 
> 
> 
> On Sunday 02 September 2018 06:18 PM,
>   Damjan Marion via Lists.Fd.Io wrote:
> 
> 
> 
> 
> >   
> >   External Email
> >   
> > 
> > 
> > 
> > Dear all,
> > 
> > 
> > 
> > We just switched from autotools to cmake and
> >   retired all autotools related files in src/.
> > 
> > 
> > 
> > All verify jobs are ok, and we also tried it on 3
> >   different x86 and 2 different ARM Aarch64 machines.
> > 
> > 
> > 
> > Due to blast radius, i will not be surprised that
> >   some small issues pop out, but i don't expect anything hard to
> >   fix.
> > 
> > 
> > 
> > Let us know if you hit something...
> > 
> > 
> > 
> > PS As a part of this change, CentOS 7 build are
> >   now using devtoolset-7, so they are compiled with gcc-7, which
> >   also means images have support for Skylake Servers (AVX512).
> > 
> > 
> >   
> > 
> >   -- 
> > 
> >   Damjan
> >   
> >   
> > 
> > 
> >   
> >   
> > 
> >   
> >   
> > 
> >   -=-=-=-=-=-=-=-=-=-=-=-Links: You receive all messages sent to this
> > group.
> > View/Reply Online (#10337): https://lists.fd.io/g/vpp-dev/message/10337Mute
> > This Topic: https://lists.fd.io/mt/25155374/675748Group Owner: vpp-
> > dev+ow...@lists.fd.ioUnsubscribe: https://lists.fd.io/g/vpp-dev/unsubb  [nsa
> > x...@caviumnetworks.com]-=-=-=-=-=-=-=-=-=-=-=-
> > 
> > 
> 
> 
> 
>   
> 
> -=-=-=-=-=-=-=-=-=-=-=-Links: You receive all messages sent to this group.
> View/Reply Online (#10407): https://lists.fd.io/g/vpp-dev/message/10407Mute
> This Topic: https://lists.fd.io/mt/25155374/675056Group Owner: vpp-
> dev+ow...@lists.fd.ioUnsubscribe: https://lists.fd.io/g/vpp-dev/unsubb  [mvarl
> e...@suse.de]-=-=-=-=-=-=-=-=-=-=-=-
-- 
Marco V


SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10408): https://lists.fd.io/g/vpp-dev/message/10408
Mute This Topic: https://lists.fd.io/mt/25155374/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Using VPP in Openstack VMs

[Marco Varlese]

Pedro,

On Thu, 2018-09-06 at 10:15 +0200, Pedro A. Aranda wrote:
> Dear all,
> I’m trying to setup a VM in OpenStack to run VPP based apps. I intend to use
> ubuntu-xenial or ubuntu-bionic.
> What ‘extra’ features do I need to activate? How do I tell OpenStack to
> activate them?
Take a look at this https://github.com/openstack/networking-
vpp/blob/master/README.rst


Thanks a lot, /PA
—
PEDRO ANDRES ARANDA GUTIERREZ
para...@it.uc3m.es

Fragen sind nicht da um beantwortet zu werden…
Fragen sind da, um gestellt zu werden.
Georg Kreisler

> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#10399): https://lists.fd.io/g/vpp-dev/message/10399
> Mute This Topic: https://lists.fd.io/mt/25235841/675056
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [mvarl...@suse.de]
> -=-=-=-=-=-=-=-=-=-=-=-
> 
-- 
Marco V


SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10400): https://lists.fd.io/g/vpp-dev/message/10400
Mute This Topic: https://lists.fd.io/mt/25235841/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Issue in adding 10 G NIC to VPP

[Marco Varlese]

Priyanka,

Please, make sure you have "intel_iommu=on" and "iommu=pt" in your boot grub
configuration.

Also, if you're using (as I presume but you didn't confirmed) a NUMA machine,
remove any configuration about hugepages from the boot grub configuration and
follow the instructions I gave you earlier.

Then, reboot your machine and do not use uio_pci_generic but rather vfio-pci
(edit the startup.conf: change the uio_driver used and modprobe vfio-pci instead
of uio_pci_generic).

Also, please, if things still do not work share:
1) VPP version
2) Content of "startup.conf"
3) Output of "cat /proc/cmdline"

On Thu, 2018-09-06 at 13:12 +0530, ppnaik wrote:
> Hi Marco,
> 
> The NIC is binded to DPDK driver: devbing.py output:
> 
> Network devices using DPDK-compatible driver
> 
> :01:00.1 'I350 Gigabit Network Connection 1521' drv=uio_pci_generic 
> unused=vfio-pci
> :81:00.0 'Ethernet Controller 10-Gigabit X540-AT2 1528' 
> drv=uio_pci_generic unused=vfio-pci
> :81:00.1 'Ethernet Controller 10-Gigabit X540-AT2 1528' 
> drv=uio_pci_generic unused=vfio-pci
> 
> Network devices using kernel driver
> ===
> :01:00.0 'I350 Gigabit Network Connection 1521' if=enp1s0f0 drv=igb 
> unused=vfio-pci,uio_pci_generic *Active*
> 
> Other Network devices
> =
> 
> 
> Crypto devices using DPDK-compatible driver
> ===
> 
> 
> Crypto devices using kernel driver
> ==
> 
> 
> Other Crypto devices
> 
> 
> 
> Eventdev devices using DPDK-compatible driver
> =
> 
> 
> Eventdev devices using kernel driver
> 
> 
> 
> Other Eventdev devices
> ==========
> 
> 
> Mempool devices using DPDK-compatible driver
> 
> 
> 
> Thanks,
> Priyanka
> 
> 
> On 2018-09-06 12:56, Marco Varlese wrote:
> > On Thu, 2018-09-06 at 11:23 +0530, Avinash Dhar Dubey wrote:
> > > Arijit,
> > > Share the output of "cat /proc/meminfo | grep -i huge" and "free 
> > > -h".
> > > You are using 1GB hugepages and you have not configured them.
> > > Better use 2MB hugepages if you are running vpp just for learning.
> > > 
> > > Also share the contents of "/etc/default/grub". Looks like you have 
> > > set 1GB as
> > > default hugepage size.
> > 
> > Actually the output log is the complete opposite!!!That log is simply 
> > stating
> > that you have _NOT_ reserved 1GB hugepages but rather the 2MB ones. 
> > See below
> > for the actual "problem"...
> > > Regards,
> > > Avinash
> > > 
> > > On Thu, Sep 6, 2018 at 4:41 PM, Arijit Pramanik 
> > >  wrote:
> > > > I have added the plugin path  as /usr/lib/vpp/vpp_plugins and 
> > > 
> > > enabled only
> > > > dpdk_plugin.so
> > > > 
> > > > But I'm getting the error currently as
> > > > 
> > > > Sep 06 16:30:54 turing-04 vpp[2339]: EAL: No free hugepages 
> > > 
> > > reported in
> > > > hugepages-1048576kB
> > > > Sep 06 16:30:54 turing-04 vpp[2339]: EAL: VFIO support initialized
> > > > Sep 06 16:30:54 turing-04 vnet[2339]: EAL: VFIO support 
> > > 
> > > initialized
> > > > Sep 06 16:30:54 turing-04 vpp[2339]: EAL: Requested device 
> > > 
> > > :81:00.1
> > > > cannot be used
> > > > Sep 06 16:30:54 turing-04 vnet[2339]: EAL: Requested device 
> > > 
> > > :81:00.1
> > > > cannot be used
> > > > Sep 06 16:30:55 turing-04 vnet[2339]: dpdk_pool_create:550:
> > > > ioctl(VFIO_IOMMU_MAP_DMA) pool 'dpdk_mbuf_pool_socket0': Invalid 
> > > 
> > > argument
> > > > (errno 22)
> > > > Sep 06 16:30:55 turing-04 vnet[2339]: dpdk_pool_create: failed to 
> > > 
> > > create
> > > > dpdk_mbuf_pool_socket1
> > > > Sep 06 16:30:55 turing-04 vnet[2339]: dpdk_buffer_pool_create:616: 
> > > 
> > > WARNING:
> > > > Failed to allocate mempool for CPU socket 1. Threads running on 
> > > 
> > > socket 1
> > > > will use socket 0 mempool.
> > 
> > I suppose you're running on a NUMA machine? Apparently the hugepages 
> > allocation
> > has run out on one of the two socke

Re: [vpp-dev] 18.07.1 dot release

[Marco Varlese]

Cool... thanks!
On Wed, 2018-09-05 at 11:00 -0700, Gonsalves, Avinash (Nokia - IN/Bangalore)
wrote:
> Done. Added feature Multi-Core Crypto Dev support for VPP for Release 18.10
> -=-=-=-=-=-=-=-=-=-=-=-Links: You receive all messages sent to this group.
> View/Reply Online (#10386): https://lists.fd.io/g/vpp-dev/message/10386Mute
> This Topic: https://lists.fd.io/mt/25177447/675056Group Owner: vpp-
> dev+ow...@lists.fd.ioUnsubscribe: https://lists.fd.io/g/vpp-dev/unsubb  [mvarl
> e...@suse.de]-=-=-=-=-=-=-=-=-=-=-=-
-- 
Marco V


SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10397): https://lists.fd.io/g/vpp-dev/message/10397
Mute This Topic: https://lists.fd.io/mt/25177447/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Issue in adding 10 G NIC to VPP

[Marco Varlese]

On Thu, 2018-09-06 at 01:05 +0530, Arijit Pramanik wrote:
> 
> Hi Marco,
> Thanks a lot for your prompt reply and assistance.
> 
> We are using Intel X540 NIC. 
> 
> I'll try with one of them. Which one do you think is best suited for my NIC,
> How do I ensure that the driver module is loaded in the kernel beforehand?
Like any other kernel drivers "modprobe vfio-pci"

We want vpp with dpdk plugin. I've just installed vpp using apt-get following 
the steps on this link : 
https://wiki.fd.io/view/VPP/Installing_VPP_binaries_from_packages.
Does DPDK have to be spearely installed to be able to use the dpdk plugin?

Thanks a lot,
Arijit.



On Wed, Sep 5, 2018 at 8:30 PM Marco Varlese  wrote:
Arijit,

Few questions:
1) What NIC is your 10G NIC?
2) Your configuration is wrong:
ixgbe is not a uio-driver... you should choose between vfio-pci, 
uio-pci-generic or igb_uio (and make sure to have that driver module loaded in 
the kernel beforehand).
3) I assume you're trying to use VPP with DPDK plugin enabled. Can you confirm?


- Marco

On Wed, 2018-09-05 at 23:18 +0530, Arijit Pramanik wrote:
ng VPP with DPDK on our intel Xeon 24 core server. We have installed VPP and 
our 1G card was visible when 
$ sudo vppctl show interface
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg



On Wed, Sep 5, 2018 at 8:30 PM Marco Varlese  wrote:
Arijit,

Few questions:
1) What NIC is your 10G NIC?
2) Your configuration is wrong:
ixgbe is not a uio-driver... you should choose between vfio-pci, 
uio-pci-generic or igb_uio (and make sure to have that driver module loaded in 
the kernel beforehand).
3) I assume you're trying to use VPP with DPDK plugin enabled. Can you confirm?


- Marco

On Wed, 2018-09-05 at 23:18 +0530, Arijit Pramanik wrote:
ng VPP with DPDK on our intel Xeon 24 core server. We have installed VPP and 
our 1G card was visible when 
$ sudo vppctl show interface 
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
-- 
Marco V


SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10395): https://lists.fd.io/g/vpp-dev/message/10395
Mute This Topic: https://lists.fd.io/mt/25209728/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Issue in adding 10 G NIC to VPP

[Marco Varlese]

On Thu, 2018-09-06 at 11:23 +0530, Avinash Dhar Dubey wrote:
> Arijit,
> Share the output of "cat /proc/meminfo | grep -i huge" and "free -h".
> You are using 1GB hugepages and you have not configured them.
> Better use 2MB hugepages if you are running vpp just for learning.
> 
> Also share the contents of "/etc/default/grub". Looks like you have set 1GB as
> default hugepage size.
Actually the output log is the complete opposite!!!That log is simply stating
that you have _NOT_ reserved 1GB hugepages but rather the 2MB ones. See below
for the actual "problem"...
> Regards,
> Avinash  
> 
> On Thu, Sep 6, 2018 at 4:41 PM, Arijit Pramanik  wrote:
> > I have added the plugin path  as /usr/lib/vpp/vpp_plugins and enabled only
> > dpdk_plugin.so
> > 
> > But I'm getting the error currently as 
> > 
> > Sep 06 16:30:54 turing-04 vpp[2339]: EAL: No free hugepages reported in
> > hugepages-1048576kB
> > Sep 06 16:30:54 turing-04 vpp[2339]: EAL: VFIO support initialized
> > Sep 06 16:30:54 turing-04 vnet[2339]: EAL: VFIO support initialized
> > Sep 06 16:30:54 turing-04 vpp[2339]: EAL: Requested device :81:00.1
> > cannot be used
> > Sep 06 16:30:54 turing-04 vnet[2339]: EAL: Requested device :81:00.1
> > cannot be used
> > Sep 06 16:30:55 turing-04 vnet[2339]: dpdk_pool_create:550:
> > ioctl(VFIO_IOMMU_MAP_DMA) pool 'dpdk_mbuf_pool_socket0': Invalid argument
> > (errno 22)
> > Sep 06 16:30:55 turing-04 vnet[2339]: dpdk_pool_create: failed to create
> > dpdk_mbuf_pool_socket1
> > Sep 06 16:30:55 turing-04 vnet[2339]: dpdk_buffer_pool_create:616: WARNING:
> > Failed to allocate mempool for CPU socket 1. Threads running on socket 1
> > will use socket 0 mempool.
I suppose you're running on a NUMA machine? Apparently the hugepages allocation
has run out on one of the two socket and it's _warning_ you that memory will be
taken from the other one. It's warning you because it's a performance hit to
access remote-node memory...Again this is a _warning_ not an error. Having said
all that, why don't you follow this page (DPDK) on how to reserve hugepages for
NUMA machines?https://doc.dpdk.org/guides/linux_gsg/sys_reqs.htmlSomething
like:echo 1024 > 
/sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages
echo 1024 > /sys/devices/system/node/node1/hugepages/hugepages-
2048kB/nr_hugepages
> > Sep 06 16:30:55 turing-04 vnet[2339]: dpdk_ipsec_process:1018: not enough
> > DPDK crypto resources, default to OpenSSL
> > Sep 06 16:30:55 turing-04 vnet[2339]: dpdk_lib_init:230: DPDK drivers found
> > no ports...
You have not binded any port to be used by DPDK... again, take a look at this
webpagehttps://doc.dpdk.org/guides/tools/devbind.htmlSomething like 
dpdk-devbind 
--bind=vfio-pci PCI_BAR_ADDRESSwill map your port (identified by
PCI_BAR_ADDRESS) to the vfio-pci driver.
> > Thanks,
> > Arijit.
- Marco
> > 
> > On Thu, Sep 6, 2018 at 9:44 AM Avinash Dhar Dubey  > > wrote:
> > > Arijit,
> > > 
> > > 
> > > We are using Intel X540 NIC. 
> > > >>  Intel X540 NIC  is supported by DPDK.
> > > 
> > > 
> > > 
> > > I'll try with one of them. Which one do you think is best suited for my
> > > NIC, How do I ensure that the driver module is loaded in the kernel
> > > beforehand?
> > > >>
> > > 
> > >  You can use uio_pci_generic driver. To ensure that the driver is loaded
> > > before you start vpp, you can run "modprobe uio_pci_generic". It will load
> > > the driver if its already present as part of your kernel distribution. If
> > > not found you can get it by installing linux-image-extra--
> > > generic package.
> > > 
> > > 
> > > 
> > > We want vpp with dpdk plugin. I've just installed vpp using apt-get
> > > following the steps on this link : 
> > > https://wiki.fd.io/view/VPP/Installing_VPP_binaries_from_packages.
> > > Does DPDK have to be spearely installed to be able to use the dpdk plugin?
> > > >>  No, when you compile vpp it creates dpdk_plugin.so which gets loaded
> > > if you have specified the plugin_path in startup.conf
> > > 
> > > Hope this helps.
> > > 
> > > Avinash 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > On Thu, Sep 6, 2018 at 1:05 AM, Arijit Pramanik 
> > > wrote:
> > > > Hi Marco,
> > > > Thanks a lot for your prompt reply and assistance.
> > > > 
> > > > We are using Intel X540 NIC. 
> > > > 
>

Re: [vpp-dev] Issue in adding 10 G NIC to VPP

[Marco Varlese]

Arijit,
Few questions:1) What NIC is your 10G NIC?2) Your configuration is wrong:ixgbe
is not a uio-driver... you should choose between vfio-pci, uio-pci-generic or
igb_uio (and make sure to have that driver module loaded in the kernel
beforehand).3) I assume you're trying to use VPP with DPDK plugin enabled. Can
you confirm?

- Marco
On Wed, 2018-09-05 at 23:18 +0530, Arijit Pramanik wrote:
> ng VPP with DPDK on our intel Xeon 24 core server. We have installed VPP and
> our 1G card was visible when 
> $ sudo vppctl show interface 
-- 
Marco V


SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10381): https://lists.fd.io/g/vpp-dev/message/10381
Mute This Topic: https://lists.fd.io/mt/25209728/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] VPP Release 18.10 (F0): 4 weeks notice reminder

[Marco Varlese]

Dear all,

I would like to remind you all that API freeze (F0) for release 18.10 is exaclty
in 4 weeks from now. If you are not aware yet of the release schedule, please,
take a moment to familiarize yourself with it by visiting [1]. 

Further, I would kindly ask you to, please, take few moments to add any release
deliverables to it [1]. I believe there are plenty of new cool features going
into 18.10 and the list does not reflect that at all.

If you cannot edit the wiki page yourself, please, send the list of deliverables
to me and I will be glad to do that on your behalf.

I look forward to everybody's help, input and collaboration.

[1] https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_18.10


Best regards,
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10379): https://lists.fd.io/g/vpp-dev/message/10379
Mute This Topic: https://lists.fd.io/mt/25210758/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[FD.io Helpdesk #60548] [linuxfoundation.org #60548] Re: [infra-steering] [vpp-dev] Suspicious login on fd.io wiki

[Marco Varlese via RT]

On Wed, 2018-09-05 at 13:40 +, Vratko Polak -X (vrpolak - PANTHEON
TECHNOLOGIES at Cisco) via Lists.Fd.Io wrote:
> > suggest a workaround?
> 
> Navigate to https://wiki.fd.io/view/Main_Page before logging in.
> Vratko.
Thanks!!!
> 
> -Original Message-
> From: vpp-dev@lists.fd.io  On Behalf Of Marco Varlese
> Sent: Wednesday, 2018-September-05 15:31
> To: Vanessa Valderrama via RT 
> Cc: vpp-dev@lists.fd.io; infra-steer...@lists.fd.io
> Subject: [vpp-dev] Suspicious login on fd.io wiki
> 
> Hi,
> 
> I am not able to login to edit any page of the FD.io wiki. 
> 
> The error I get, by simply clicking on "Log in/Register..." is:
> "suspicious request, please try again"
> 
> Can anybody take a look or suggest a workaround?
> 
> 
> Cheers,
> --
> Marco V
> 
> SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB
> 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#532): https://lists.fd.io/g/infra-steering/message/532
> Mute This Topic: https://lists.fd.io/mt/25210404/535416
> Group Owner: infra-steering+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/infra-steering/unsubb  [marco.varlese@suse.
> de]
> -=-=-=-=-=-=-=-=-=-=-=-
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10376): https://lists.fd.io/g/vpp-dev/message/10376
Mute This Topic: https://lists.fd.io/mt/25210661/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Suspicious login on fd.io wiki

[Marco Varlese]

Hi,

I am not able to login to edit any page of the FD.io wiki. 

The error I get, by simply clicking on "Log in/Register..." is:
"suspicious request, please try again"

Can anybody take a look or suggest a workaround?


Cheers,
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10372): https://lists.fd.io/g/vpp-dev/message/10372
Mute This Topic: https://lists.fd.io/mt/25210301/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] 18.07.1 dot release

[Marco Varlese]

+1 
@avinash: if you plan to add that feature in 18.10, please, take a moment to add
that to the list here:
https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_18.10

Cheers,
On Tue, 2018-09-04 at 10:22 -0700, Edward Warnicke wrote:
> Second that… bug fixes in 18.07.1… new features on master for 18.10
> 
> Ed
>  
>   
> On September 4, 2018 at 12:21:28 PM, Damjan Marion via Lists.Fd.Io (
> dmarion=me@lists.fd.io) wrote:
>  
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Dear Avinash,
> > 
> > 
> > Dot releases are only for bug fixes, new features
> > should not go there...
> > 
> > 
> > 
> > 
> > -- 
> > 
> > Damjan
> > 
> > 
> > 
> > > On 4 Sep 2018, at 18:12, avinash.gonsal...@nokia.com wrote:
> > > 
> > > 
> > > 
> > > I would like to propose an enhancement for vpp to work
> > > with dpdk multicore-crypto scheduler (
> > > http://doc.dpdk.org/guides-18.02/cryptodevs/scheduler.html).
> > > For the software crypto pmd to be scheduled on multiple
> > > cores the following dpdk configuration is required:
> > > vdev
> > > crypto_scheduler,slave=aesni_mb_1,slave=aesni_mb_2,mode=multi-
> > > core,corelist=3-4,ordering=enable
> > > This does not work directly with base VPP code, the
> > > following enhancements are required
> > > 1. VPP Changes:
> > > - Recognize slave-lcore corelist assigned
> > > for multi-core crypto and pass the configuration during dpdk plugin
> > > device init(startup.conf)
> > > - Start the multi-core crypto scheduler
> > > for the correct device_id.
> > > 2. DPDK Patch 
> > > - Enable
> > > RTE_LIBRTE_PMD_CRYPTO_SCHEDULER
> > > - Enable PER_SLAVE_BUFF_SIZE to be
> > > configurable from start parameters(slave_buff_size=8192)
> > > - Ordering Fix for Multi Producer
> > > Queue
> > > A patch was performance tested off VPP 17.10 (DPDK
> > > 17.08) release with 2,3,4 crypto cores.
> > > If everyone thinks this merits going into 18.07.1, i'll
> > > initiate a review (there have been a couple of posts on this
> > > already)
> > > -=-=-=-=-=-=-=-=-=-=-=-
> > > 
> > > Links: You receive all messages sent to this group.
> > > 
> > > 
> > > 
> > > View/Reply Online (#10353): https://lists.fd.io/g/vpp-dev/message/10353
> > > 
> > > Mute This Topic: https://lists.fd.io/mt/25177447/675642
> > > 
> > > Group Owner: vpp-dev+ow...@lists.fd.io
> > > 
> > > Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [dmar...@me.com]
> > > 
> > > -=-=-=-=-=-=-=-=-=-=-=-
> > > 
> > 
> > 
> > 
> > 
> > 
> > -=-=-=-=-=-=-=-=-=-=-=-
> > 
> > Links: You receive all messages sent to this group.
> > 
> > 
> > 
> > View/Reply Online (#10356): https://lists.fd.io/g/vpp-dev/message/10356
> > 
> > Mute This Topic: https://lists.fd.io/mt/25177447/464962
> > 
> > Group Owner: vpp-dev+ow...@lists.fd.io
> > 
> > Unsubscribe: https://lists.fd.io/g/vpp-dev/unsubb  [hagb...@gmail.com]
> > 
> > -=-=-=-=-=-=-=-=-=-=-=-
> > 
> 
> -=-=-=-=-=-=-=-=-=-=-=-Links: You receive all messages sent to this group.
> View/Reply Online (#10357): https://lists.fd.io/g/vpp-dev/message/10357Mute
> This Topic: https://lists.fd.io/mt/25177447/675056Group Owner: vpp-
> dev+ow...@lists.fd.ioUnsubscribe: https://lists.fd.io/g/vpp-dev/unsubb  [mvarl
> e...@suse.de]-=-=-=-=-=-=-=-=-=-=-=-
-- 
Marco V


SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10371): https://lists.fd.io/g/vpp-dev/message/10371
Mute This Topic: https://lists.fd.io/mt/25177447/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] VPP 18.10 Release Plan

[Marco Varlese]

All,

During today VPP project meeting call it has been discussed about the release
milestones for 18.10.

The release plan and agreed schedule can be found at the release wiki-page:
https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_18.10

Starting from today, I would like to start gathering the release deliverables
for 18.10. You can either edit the wiki-page directly or send on to me what you
are planning to release in October.

Look forward to everybody's help and contribution!!!


Cheers,
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10239): https://lists.fd.io/g/vpp-dev/message/10239
Mute This Topic: https://lists.fd.io/mt/24877316/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] No space left on device :(

[Marco Varlese]

+ 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-
> 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  } // namespace VOM
> 15:50:53  ^
> 15:50:53 compilation terminated.
> 15:50:53 Makefile:877: recipe for target 'pipe_cmds.lo' failed
> 15:50:53 make[3]: *** [pipe_cmds.lo] Error 1
> 15:50:53 make[3]: *** Waiting for unfinished jobs
> 15:50:55 Makefile:877: recipe for target 'neighbour.lo' failed
> 15:50:55 make[3]: *** [neighbour.lo] Error 1
> 15:51:00 Makefile:877: recipe for target 'neighbour_cmds.lo' failed
> 15:51:00 make[3]: *** [neighbour_cmds.lo] Error 1
> 15:51:10 /w/workspace/vpp-arm-verify-master-ubuntu1604/build-
> data/../extras/vom/vom/pipe.cpp:203:2: fatal error: error writing to
> /tmp/ccxe70KB.s: No space left on device
> 15:51:10  }; // namespace VOM
> 15:51:10   ^
> 15:51:10 compilation terminated.
> 
> 
> Cheers,
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#10220): https://lists.fd.io/g/vpp-dev/message/10220
> Mute This Topic: https://lists.fd.io/mt/24819110/675056
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsubb  [mvarl...@suse.de]
> -=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10222): https://lists.fd.io/g/vpp-dev/message/10222
Mute This Topic: https://lists.fd.io/mt/24819110/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] No space left on device :(

[Marco Varlese]

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  } // namespace VOM
15:50:53  ^
15:50:53 compilation terminated.
15:50:53 Makefile:877: recipe for target 'pipe_cmds.lo' failed
15:50:53 make[3]: *** [pipe_cmds.lo] Error 1
15:50:53 make[3]: *** Waiting for unfinished jobs
15:50:55 Makefile:877: recipe for target 'neighbour.lo' failed
15:50:55 make[3]: *** [neighbour.lo] Error 1
15:51:00 Makefile:877: recipe for target 'neighbour_cmds.lo' failed
15:51:00 make[3]: *** [neighbour_cmds.lo] Error 1
15:51:10 /w/workspace/vpp-arm-verify-master-ubuntu1604/build-
data/../extras/vom/vom/pipe.cpp:203:2: fatal error: error writing to
/tmp/ccxe70KB.s: No space left on device
15:51:10  }; // namespace VOM
15:51:10   ^
15:51:10 compilation terminated.


Cheers,
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10220): https://lists.fd.io/g/vpp-dev/message/10220
Mute This Topic: https://lists.fd.io/mt/24819110/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Revert of gerrit 13408 / "vppinfra: AVX2 blend" in progress..

[Marco Varlese]

Hi Dave & allm
Sorry about that,I actually merged the patch. However, it was indeed Verified+1
:(
I have gone now to see the actual CLANG build failure and wondering: is it
possible that job is not configured as voting/gating job in Jenkins so the
verification process succeeds anyway?

- Marco
On Thu, 2018-07-12 at 22:49 +, Dave Barach via Lists.Fd.Io wrote:
> Revert complete... HTH... Dave
>  
> 
> 
> From: Dave Barach (dbarach) 
> 
> Sent: Thursday, July 12, 2018 5:01 PM
> 
> To: Damjan Marion (damarion) ; Florin Coras (fcoras)  a...@cisco.com>; 'Marco Varlese' ; Ed Kern (ejk) 
>  m>
> 
> Cc: vpp-dev@lists.fd.io
> 
> Subject: Revert of gerrit 13408 / "vppinfra: AVX2 blend" in progress..
> 
> Importance: High
> 
> 
>  
> Folks,
>  
> Unfortunately, the AVX2 blend patch causes 100% clang validation failures on
> unrelated patches. The clang validation job actually failed on the original
> patch, but somehow fd.io JJB voted +1 anyhow.
>  
> See 
> https://gerrit.fd.io/r/#/c/13457 – revert, 
> https://gerrit.fd.io/r/#/c/13408 - original patch.
>  
> Thanks... Dave
>  
> 
> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-Links: You receive all messages sent to this group.
> View/Reply Online (#9830): https://lists.fd.io/g/vpp-dev/message/9830Mute This
> Topic: https://lists.fd.io/mt/23297899/675056Group Owner: vpp-
> dev+ow...@lists.fd.ioUnsubscribe: https://lists.fd.io/g/vpp-dev/unsubb  [mvarl
> e...@suse.de]-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#9831): https://lists.fd.io/g/vpp-dev/message/9831
Mute This Topic: https://lists.fd.io/mt/23297899/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] VPP Vnet crash with vhost-user interface

[Marco Varlese]

Ravi,

On Sun, 2018-05-27 at 12:20 -0700, Ravi Kerur wrote:
> Hello,
> 
> I have a VM(16.04.4 Ubuntu x86_64) with 2 cores and 4G RAM. I have
> installed VPP successfully on it. Later I have created vhost-user
> interfaces via
> 
> create vhost socket /var/run/vpp/sock1.sock server
> create vhost socket /var/run/vpp/sock2.sock server
> set interface state VirtualEthernet0/0/0 up
> set interface state VirtualEthernet0/0/1 up
> 
> set interface l2 bridge VirtualEthernet0/0/0 1
> set interface l2 bridge VirtualEthernet0/0/1 1
> 
> I then run 'DPDK/testpmd' inside a container which will use
> virtio-user interfaces using the following command
> 
> docker run -it --privileged -v
> /var/run/vpp/sock1.sock:/var/run/usvhost1 -v
> /var/run/vpp/sock2.sock:/var/run/usvhost2 -v
> /dev/hugepages:/dev/hugepages dpdk-app-testpmd ./bin/testpmd -c 0x3 -n
> 4 --log-level=9 -m 64 --no-pci --single-file-segments
> --vdev=virtio_user0,path=/var/run/usvhost1,mac=54:01:00:01:01:01
> --vdev=virtio_user1,path=/var/run/usvhost2,mac=54:01:00:01:01:02 --
> -i
> 
> VPP Vnet crashes with following message
> 
> May 27 11:44:00 localhost vnet[6818]: received signal SIGSEGV, PC
> 0x7fcca4620187, faulting address 0x7fcb317ac000
> 
> Questions:
> I have 'ulimit -c unlimited' and /etc/vpp/startup.conf has
> unix {
>   nodaemon
>   log /var/log/vpp/vpp.log
>   full-coredump
>   cli-listen /run/vpp/cli.sock
>   gid vpp
> }
> 
> But I couldn't locate corefile?
The location of the coredump file depends on your system configuration.

Please, check "cat /proc/sys/kernel/core_pattern"

If you have systemd-coredump in the output of the above command, then likely the
location of the coredump files is "/var/lib/systemd/coredump/"

You can also change the location of where your system places the coredump files:
echo '/PATH_TO_YOU_LOCATION/core_%e.%p' | sudo tee /proc/sys/kernel/core_pattern

See if that helps...

> 
> (2) How to enable debugs? I have used 'make build' but no additional
> logs other than those shown below
> 
> 
> VPP logs from /var/log/syslog is shown below
> cat /var/log/syslog
> May 27 11:40:28 localhost vpp[6818]: vlib_plugin_early_init:361:
> plugin path /usr/lib/vpp_plugins:/usr/lib64/vpp_plugins
> May 27 11:40:28 localhost vpp[6818]: load_one_plugin:189: Loaded
> plugin: abf_plugin.so (ACL based Forwarding)
> May 27 11:40:28 localhost vpp[6818]: load_one_plugin:189: Loaded
> plugin: acl_plugin.so (Access Control Lists)
> May 27 11:40:28 localhost vpp[6818]: load_one_plugin:189: Loaded
> plugin: avf_plugin.so (Intel Adaptive Virtual Function (AVF) Device
> Plugin)
> May 27 11:40:28 localhost vpp[6818]: load_one_plugin:191: Loaded
> plugin: cdp_plugin.so
> May 27 11:40:28 localhost vpp[6818]: load_one_plugin:189: Loaded
> plugin: dpdk_plugin.so (Data Plane Development Kit (DPDK))
> May 27 11:40:28 localhost vpp[6818]: load_one_plugin:189: Loaded
> plugin: flowprobe_plugin.so (Flow per Packet)
> May 27 11:40:28 localhost vpp[6818]: load_one_plugin:189: Loaded
> plugin: gbp_plugin.so (Group Based Policy)
> May 27 11:40:28 localhost vpp[6818]: load_one_plugin:189: Loaded
> plugin: gtpu_plugin.so (GTPv1-U)
> May 27 11:40:28 localhost vpp[6818]: load_one_plugin:189: Loaded
> plugin: igmp_plugin.so (IGMP messaging)
> May 27 11:40:28 localhost vpp[6818]: load_one_plugin:189: Loaded
> plugin: ila_plugin.so (Identifier-locator addressing for IPv6)
> May 27 11:40:28 localhost vpp[6818]: load_one_plugin:189: Loaded
> plugin: ioam_plugin.so (Inbound OAM)
> May 27 11:40:28 localhost vpp[6818]: load_one_plugin:117: Plugin
> disabled (default): ixge_plugin.so
> May 27 11:40:28 localhost vpp[6818]: load_one_plugin:189: Loaded
> plugin: l2e_plugin.so (L2 Emulation)
> May 27 11:40:28 localhost vpp[6818]: load_one_plugin:189: Loaded
> plugin: lacp_plugin.so (Link Aggregation Control Protocol)
> May 27 11:40:28 localhost vpp[6818]: load_one_plugin:189: Loaded
> plugin: lb_plugin.so (Load Balancer)
> May 27 11:40:28 localhost vpp[6818]: load_one_plugin:189: Loaded
> plugin: memif_plugin.so (Packet Memory Interface (experimetal))
> May 27 11:40:28 localhost vpp[6818]: load_one_plugin:189: Loaded
> plugin: nat_plugin.so (Network Address Translation)
> May 27 11:40:28 localhost vpp[6818]: load_one_plugin:189: Loaded
> plugin: pppoe_plugin.so (PPPoE)
> May 27 11:40:28 localhost vpp[6818]: load_one_plugin:189: Loaded
> plugin: srv6ad_plugin.so (Dynamic SRv6 proxy)
> May 27 11:40:28 localhost vpp[6818]: load_one_plugin:189: Loaded
> plugin: srv6am_plugin.so (Masquerading SRv6 proxy)
> May 27 11:40:28 localhost vpp[6818]: load_one_plugin:189: Loaded
> plugin: srv6as_plugin.so (Static SRv6 proxy)
> May 27 11:40:29 localhost vpp[6818]: load_one_plugin:189: Loaded
> plugin: stn_plugin.so (VPP Steals the NIC for Container integration)
> May 27 11:40:29 localhost vpp[6818]: load_one_plugin:189: Loaded
> plugin: tlsmbedtls_plugin.so (mbedtls based TLS Engine)
> May 27 11:40:29 localhost vpp[6818]: load_one_plugin:189: Loaded
> plugin: tlsopenssl_plugin.so (openssl 

[FD.io Helpdesk #56282] [linuxfoundation.org #56282] Re: [vpp-dev] git.fd.io not updating

[Marco Varlese via RT]

Roughly a week ago, I noticed there was a DNS/IP change when cloning a new VPP
repo... I wonder if what I saw is somehow connected to this issue.
On Mon, 2018-05-21 at 16:34 -0700, Florin Coras wrote:
> Hi, 
> It would seem that git.fd.io [1] thinks that we last committed a patch to vpp
> almost 1 week ago. Any idea what might’ve triggered this? 
> Thanks, Florin
> [1] https://git.fd.io/vpp/log/
> 
> 
> 
-- 
Marco V


SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#9356): https://lists.fd.io/g/vpp-dev/message/9356
View All Messages In Topic (1): https://lists.fd.io/g/vpp-dev/topic/19743864
Mute This Topic: https://lists.fd.io/mt/19743864/21656
New Topic: https://lists.fd.io/g/vpp-dev/post

Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656
Group Home: https://lists.fd.io/g/vpp-dev
Contact Group Owner: vpp-dev+ow...@lists.fd.io
Terms of Service: https://lists.fd.io/static/tos
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] git.fd.io not updating

[Marco Varlese]

Roughly a week ago, I noticed there was a DNS/IP change when cloning a new VPP
repo... I wonder if what I saw is somehow connected to this issue.
On Mon, 2018-05-21 at 16:34 -0700, Florin Coras wrote:
> Hi, 
> It would seem that git.fd.io [1] thinks that we last committed a patch to vpp
> almost 1 week ago. Any idea what might’ve triggered this? 
> Thanks, Florin
> [1] https://git.fd.io/vpp/log/
> 
> 
> 
-- 
Marco V


SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

Re: [vpp-dev] segfault due to movaps unaligned access

[Marco Varlese]

On Thu, 2018-05-03 at 11:52 +, Dave Barach (dbarach) wrote:
> Dear Marco,
> 
> The condition that I'm testing for is different from the condition checked for
> by -fsanitize=alignment. 
> 
> Let's say that someone defines a packed structure which is ten bytes long.
> Clearly the compiler will not generate an aligned vector operation, nor will
> -fsanitize=alignment complain.
> 
> However, it doesn't make sense to allocate them in an aligned vector or pool -
> to a 64-byte boundary - since only the first element of the vector/pool will
> be aligned.
Thanks for taking the time to explain. Now, it makes sense to me.
> 
> The ASSERT I'm testing says that one of three things must be true: no
> alignment request, or the object size evenly divides the alignment request, or
> the alignment request evenly divides the object size.
Got you.
> 
> There are a certain number of mistakes to clean up.
> 
> HTH... Dave
Thanks,
Marco
> 
> -Original Message-
> From: Marco Varlese <mvarl...@suse.de> 
> Sent: Thursday, May 3, 2018 3:02 AM
> To: Dave Barach (dbarach) <dbar...@cisco.com>; Ray Kinsella <m...@ashroe.eu>; 
> v
> pp-...@lists.fd.io
> Subject: Re: [vpp-dev] segfault due to movaps unaligned access
> 
> Hi Dave,
> 
> On Wed, 2018-05-02 at 19:20 +, Dave Barach wrote:
> > Quick update. I added the obvious ASSERT, and immediately found a 
> > couple of non-compliant data structures. With two (trivial) fixes, vpp 
> > makes it to the debug CLI prompt. I'm going to start looking at "make 
> > test-debug", to see how many additional issues we may encounter.
> 
> Not sure if you missed my prev email but something I did in the past with this
> sort of errors was to compile the code with "-fsanitize=undefined" (or even
> simply -fsanitize=alignment).
> In that way, you don't have to place ASSERT statements yourself around
> "potential runtime error code" since the compiler will take care of
> highlighting those instances when you launch the executable.
> 
> Basically, once you compile it with that option and launch the tests you
> should be in a position to see all misalignments highlighted.
> 
> Don't know if you missed my email just wanted to follow up, maybe it might be
> quicker?
> 
> 
> Cheers,
> Marco
> > 
> > D. 
> > 
> > -Original Message-
> > From: Dave Barach (dbarach)
> > Sent: Tuesday, May 1, 2018 3:29 PM
> > To: Ray Kinsella <m...@ashroe.eu>; vpp-dev@lists.fd.io
> > Subject: RE: [vpp-dev] segfault due to movaps unaligned access
> > 
> > Hey Ray,
> > 
> > That's a good idea, and none too hard to implement. It's on my list.
> > 
> > I'm a bit afraid of what I may find when I turn it on, but anyhow...
> > 
> > Thanks... D.
> > 
> > -Original Message-
> > From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Ray 
> > Kinsella
> > Sent: Tuesday, May 1, 2018 10:58 AM
> > To: vpp-dev@lists.fd.io
> > Subject: Re: [vpp-dev] segfault due to movaps unaligned access
> > 
> > Is it worth to use an assert (or similar) to validate the assumption 
> > in the debug build at least. Well at least until the compiler bugs get's
> > sorted?
> > 
> > Ray K
> > 
> > On 26/04/2018 17:08, Dave Barach wrote:
> > > Yes, it’s arguably a compiler bug.
> > > 
> > > But, it makes no sense to vec_validate_aligned(…), 
> > > pool_get_aligned(…) etc. objects whose size is not a multiple of the
> > > alignment request.
> > > Only the first element will be aligned to the specified boundary.
> > > 
> > > __attribute__((aligned(xxx))) is not the same thing as ensuring that 
> > > objects are _sized_ correctly.
> > > 
> > > D.
> > > 
> > > *From:*vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> *On Behalf Of *Radu 
> > > Nicolau
> > > *Sent:* Thursday, April 26, 2018 4:54 AM
> > > *To:* Florin Coras <fcoras.li...@gmail.com>
> > > *Cc:* vpp-dev@lists.fd.io
> > > *Subject:* Re: [vpp-dev] segfault due to movaps unaligned access
> > > 
> > > Hi Florin,
> > > 
> > > Thanks! The patch fixes the issue.
> > > 
> > > Any idea why is it happening?
> > > 
> > > Regards,
> > > 
> > > Radu
> > > 
> > > *From:*vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> 
> > > [mailto:vpp-dev@lists.fd.io] *On Behalf Of *Florin Coras
> > > *Sent:* Tuesday, April 24, 2018 11:25 PM
> > > *To:* Nicolau, Radu <radu.nico

Re: [vpp-dev] segfault due to movaps unaligned access

[Marco Varlese]

Hi Dave,

On Wed, 2018-05-02 at 19:20 +, Dave Barach wrote:
> Quick update. I added the obvious ASSERT, and immediately found a couple of
> non-compliant data structures. With two (trivial) fixes, vpp makes it to the
> debug CLI prompt. I'm going to start looking at "make test-debug", to see how
> many additional issues we may encounter.
Not sure if you missed my prev email but something I did in the past with this
sort of errors was to compile the code with "-fsanitize=undefined" (or even
simply -fsanitize=alignment).
In that way, you don't have to place ASSERT statements yourself around
"potential runtime error code" since the compiler will take care of highlighting
those instances when you launch the executable.

Basically, once you compile it with that option and launch the tests you should
be in a position to see all misalignments highlighted.

Don't know if you missed my email just wanted to follow up, maybe it might be
quicker?


Cheers,
Marco
> 
> D. 
> 
> -Original Message-
> From: Dave Barach (dbarach) 
> Sent: Tuesday, May 1, 2018 3:29 PM
> To: Ray Kinsella ; vpp-dev@lists.fd.io
> Subject: RE: [vpp-dev] segfault due to movaps unaligned access
> 
> Hey Ray,
> 
> That's a good idea, and none too hard to implement. It's on my list.
> 
> I'm a bit afraid of what I may find when I turn it on, but anyhow...
> 
> Thanks... D.
> 
> -Original Message-
> From: vpp-dev@lists.fd.io  On Behalf Of Ray Kinsella
> Sent: Tuesday, May 1, 2018 10:58 AM
> To: vpp-dev@lists.fd.io
> Subject: Re: [vpp-dev] segfault due to movaps unaligned access
> 
> Is it worth to use an assert (or similar) to validate the assumption in the
> debug build at least. Well at least until the compiler bugs get's sorted?
> 
> Ray K
> 
> On 26/04/2018 17:08, Dave Barach wrote:
> > Yes, it’s arguably a compiler bug.
> > 
> > But, it makes no sense to vec_validate_aligned(…), pool_get_aligned(…) 
> > etc. objects whose size is not a multiple of the alignment request.
> > Only the first element will be aligned to the specified boundary.
> > 
> > __attribute__((aligned(xxx))) is not the same thing as ensuring that 
> > objects are _sized_ correctly.
> > 
> > D.
> > 
> > *From:*vpp-dev@lists.fd.io  *On Behalf Of *Radu 
> > Nicolau
> > *Sent:* Thursday, April 26, 2018 4:54 AM
> > *To:* Florin Coras 
> > *Cc:* vpp-dev@lists.fd.io
> > *Subject:* Re: [vpp-dev] segfault due to movaps unaligned access
> > 
> > Hi Florin,
> > 
> > Thanks! The patch fixes the issue.
> > 
> > Any idea why is it happening?
> > 
> > Regards,
> > 
> > Radu
> > 
> > *From:*vpp-dev@lists.fd.io  
> > [mailto:vpp-dev@lists.fd.io] *On Behalf Of *Florin Coras
> > *Sent:* Tuesday, April 24, 2018 11:25 PM
> > *To:* Nicolau, Radu  > >
> > *Cc:* vpp-dev@lists.fd.io 
> > *Subject:* Re: [vpp-dev] segfault due to movaps unaligned access
> > 
> > Hi Radu,
> > 
> > Making the crypto_worker_main_t a full cache line in size (see patch
> > [1]) seems to solve the issue. Could you confirm?
> > 
> > Florin
> > 
> > [1] https://gerrit.fd.io/r/#/c/12086/
> > 
> > On Apr 24, 2018, at 9:23 AM, Radu Nicolau  > > wrote:
> > 
> > Hello all,
> > 
> > We’re seeing a weird issue, that is a segfault that looks to be
> > caused by a movaps instruction that is trying to access an address
> > that is not 16 byte aligned.
> > 
> > The call originates from a vec_validate_init_empty_aligned that has
> > the argument aligned to 16 bytes.
> > 
> > I have seen something like this in the past, we couldn’t find a root
> > cause and considered it a GCC bug (version 5 then), but now it pops
> > up again on version 7, so probably it isn’t.
> > 
> > Any idea? A snapshot of the gdb screen below.
> > 
> > gcc (Ubuntu 7.2.0-8ubuntu3.2) 7.2.0
> > 
> > https://postimg.cc/image/9jy4p38at/
> > 
> > thanks and I will appreciate any help,
> > 
> > Radu
> > 
> > 
> 
> 
> 
> 
> 
> 
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#9157): https://lists.fd.io/g/vpp-dev/message/9157
View All Messages In Topic (15): https://lists.fd.io/g/vpp-dev/topic/18058213
Mute This Topic: https://lists.fd.io/mt/18058213/21656
New Topic: https://lists.fd.io/g/vpp-dev/post

Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656
Group Home: https://lists.fd.io/g/vpp-dev
Contact Group Owner: vpp-dev+ow...@lists.fd.io
Terms of Service: https://lists.fd.io/static/tos
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] segfault due to movaps unaligned access

[Marco Varlese]

Hi,
On Fri, 2018-04-27 at 10:04 +, Sergio Gonzalez Monroy wrote:
> Hi,
> 
>
> 
> I have to admit that the intention (when I wrote the code) of the
> __attribute__ ((aligned(64))) on the typedef struct was to have elements
> properly sized.
> 
>
> 
> I thought to remember that I did look at this attribute behavior before but
> then again my memory is not as reliable as I wish for, so nothing like some
> testing to find out.
> 
>
> 
> struct A {
> 
> short f[3];
> 
> } __attribute__ ((aligned (64)));
> 
>
> 
> struct A a[2];
> 
>
> 
> sizeof(struct A) = 64, sizeof(a) = 128 for both GCC and CLANG.
> 
> This is the sort of behavior I was expecting. 
> 
>
> 
> typedef struct B {
> 
> short f[3];
> 
> } b_t __attribute__ ((aligned (64)));
> 
>
> 
> b_t b[2];
> 
>
> 
> Interestingly enough, when defining the typedef like above, GCC fails to
> compile with:
> 
> error: alignment of array elements is greater than element size
> 
> sizeof(b_t) = 6 for CLANG and what it looks wrong to me is sizeof(b) = 64.
> 
>
> 
> typedef struct C {
> 
> short f[3];
> 
> } __attribute__ ((aligned (64))) c_t;
> 
>
> 
> c_t c[2];
> 
>
> 
> sizeof(c_t) = 64, sizeof(c) = 128 for both GCC and CLANG.
> 
>
> 
> As far as allocations from the heap, __attribute__ ((aligned(xxx))) should
> have the desired effect.
> 
>
> 
> That being said and even though it seems to behave as I thought it should, the
> error GCC throws in one of the cases makes me wonder if we should not rely on
> the compiler and just add mark fields to the struct to achieve the desired
> size.
According to the GCC documentation (https://gcc.gnu.org/onlinedocs/gcc-3.3/gcc/T
ype-Attributes.html): id="-x-evo-selection-start-marker">"Note that the
effectiveness of aligned attributes may be limited by inherent limitations in
your linker. On many systems, the linker is only able to arrange for variables
to be aligned up to a certain maximum alignment. (For some linkers, the maximum
supported alignment may be very very small.) If your linker is only able to
align variables up to a maximum of 8 byte alignment, then specifying aligned(16)
in an __attribute__ will still only provide you with 8 byte alignment. See your
linker documentation for further information."
Having said that, it is always possible to compile the code (temporarily) with
"-fsanitize=undefined" which would show up all the misaligned accesses which
could cause run-time errors.
>
> Below is the link with some code to play around:
> https://godbolt.org/g/7RDBQG
>
> Regards,
> Sergio
>
>
> 
> From: Radu Nicolau
> 
> Sent: Friday 27 April 2018 10:34
> 
> To: Dave Barach (dbarach); 
> Florin Coras
> 
> Cc: vpp-dev@lists.fd.io
> 
> Subject: Re: [vpp-dev] segfault due to movaps unaligned access
> 
>
> Thanks for looking into it!
>
> In addition, If I understand correctly, using __attribute__((aligned(xxx))) on
> structs that are only allocated from heap doesn’t actually do anything (but
> sometimes confuse gcc into generating misaligned
>  accesses).
>
> 
> 
> From: Dave Barach (dbarach) [mailto:dbar...@cisco.com]
> 
> 
> Sent: Thursday, April 26, 2018 5:08 PM
> 
> To: Nicolau, Radu ; Florin Coras  om>
> 
> Cc: vpp-dev@lists.fd.io
> 
> Subject: RE: [vpp-dev] segfault due to movaps unaligned access
> 
> 
>
> Yes, it’s arguably a compiler bug.
>
> But, it makes no sense to vec_validate_aligned(…), pool_get_aligned(…) etc.
> objects whose size is not a multiple of the alignment request. Only the first
> element will be aligned to the
>  specified boundary. 
>
> __attribute__((aligned(xxx))) is not the same thing as ensuring that objects
> are
> sized correctly.
>
> D.
>
> 
> 
> From: 
> vpp-dev@lists.fd.io 
> On Behalf Of Radu Nicolau
> 
> Sent: Thursday, April 26, 2018 4:54 AM
> 
> To: Florin Coras 
> 
> Cc: vpp-dev@lists.fd.io
> 
> Subject: Re: [vpp-dev] segfault due to movaps unaligned access
> 
> 
>
> Hi Florin,
>
> Thanks! The patch fixes the issue.
> 
> Any idea why is it happening?
>
> Regards,
> Radu
>
> 
> 
> From: 
> vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io]
> On Behalf Of Florin Coras
> 
> Sent: Tuesday, April 24, 2018 11:25 PM
> 
> To: Nicolau, Radu 
> 
> Cc: vpp-dev@lists.fd.io
> 
> Subject: Re: [vpp-dev] segfault due to movaps unaligned access
> 
> 
>
> Hi Radu, 
> 
>
> 
> 
> Making the crypto_worker_main_t a full cache line in size (see patch [1])
> seems to solve the issue. Could you confirm?
> 
> 
>
> 
> 
> Florin
> 
> 
>
> 
> 
> [1] https://gerrit.fd.io/r/#/c/12086/
> 
>
> > On Apr 24, 2018, at 9:23 AM, Radu Nicolau  wrote:
> > 
> >
> > 
> > 
> > Hello all,
> > 
> > 
> >
> > 
> > 
> > We’re seeing a weird issue, that is a segfault that looks to be caused by a
> > movaps instruction that is trying to access an address that is not 16 byte
> > aligned.
> > 
> > 
> > The call originates from a vec_validate_init_empty_aligned that has the
> > 

Re: [vpp-dev] VPP with DPDK drops packet, but it sends ok

[Marco Varlese]

If I remember correctly, you mentioned in early email that you do _NOT_ modify
the startup.conf file for VPP. Can you confirm that?
By looking at the startup.conf file coming with VPP v18.04 the default mechanism
driver used is vfio-pci. That as mentioned before (and found out by you too)
won't work.Also, by default the DPDK section is completely commented out so all
the defaults are being used...
Can you please take a look at your startup.conf file and make sure to use
igb_uio by specifying "uio-driver igb_uio"
And, first of all, make sure the dpdk section is not commented out?
I think something like the below should help you to get going...
dpdk {  uio-driver igb_uio  }

- Marco
On Wed, 2018-04-11 at 16:12 +0900, Moon-Sang Lee wrote:
> I'm back with a little progress.
> Anyway, I found that vpp interface has MTU size as 9220B.
> And I just tried to change it to 1500B as below.
> # vppctl set interface mtu 1500 VirtualFunctionEthernet0/8/0
> 
> It works!
> My VM with VPP/DPDK ping/pong to outside server via VF of Intel 82599 10G NIC.
> But, I could not understand why MTU configuration affect to simple ping test. 
> 
> In addition, I need to measure this VM's performance with pktgen-dpdk which
> has no MTU option as far as I know. 
> When I shoot packets from pktgen, VM does not receive packets nor ping does
> not work again. 
> (i.e. pktgen and VM are directly connected with 10G link.)
> 
> I appreciate any comment. 
> 
> 
> 
> On Tue, Apr 10, 2018 at 9:16 PM, Moon-Sang Lee <sang0...@gmail.com> wrote:
> > On Tue, Apr 10, 2018 at 8:24 PM, Marco Varlese <mvarl...@suse.de> wrote:
> > > On Tue, 2018-04-10 at 19:33 +0900, Moon-Sang Lee wrote:
> > > > Thanks for your interest, Marco.
> > > > I follows the intel guideline, "As an SR-IOV VF network adapter using a
> > > > KVM virtual network pool of adapters"
> > > > from https://software.intel.com/en-us/articles/configure-sr-iov-network-
> > > > virtual-functions-in-linux-kvm. 
> > > > 
> > > > In summary, I modprobe ixgbe on host side and creates one VF per PF. 
> > > > When I start VM using virsh, libvirt binds the VF to vfio-pci in host
> > > > side.
> > > > After VM finishes booting, I login to VM and bind the VF to igb_uio
> > > > using dpdk-dev command.
> > > > (i.e. only igb_uio works and other drivers like uio_pci_generic and
> > > > vfio-pci fail to bind VF in VM side.) 
> > > Yes, that's expected. 
> > > If you want to use vfio-pci in the VM you'll need to enable the "no-
> > > iommu":
> > > # echo 1 > /sys/module/vfio/parameters/enable_unsafe_noiommu_mode
> > 
> > well, I cannot find such file in host nor VM.
> >
> > > > I don't edit startup.conf in VM, but I just bind the VF to dpdk-
> > > > compatible driver, igb_uio, inside VM.
> > > > With above configuration, I can bind the VF to guest kernel driver,
> > > > ixgbevf, and also to DPDK PMD, igb_uio.
> > > > As a result,  I can run VPP without DPDK using ixgbevf, and also DPDK
> > > > applications using igb_uio.
> > > > (i.e. I successfully runs l2fwd/l3fwd sample applications inside VM, so
> > > > I guess VF biding has no problem.)
> > > > 
> > > > However, I cannot run VPP with DPDK and I suspect hugepage is related to
> > > > this problem as shown in my VPP log.
> > > So, what does the command "cat /proc/meminfo |grep HugePages_" shows?
> > 
> > well, 'cat /proc/meminfo |grep HugePages' seems ok even though I cannot find
> > any rtemap files neither in /dev/hugepages nor /run/vpp/hugepages. 
> > When I run dpdk application, I can see rtemap files in /dev/hugepages. 
> > 
> > HugePages_Total:1024
> > HugePages_Free:  972
> > HugePages_Rsvd:0
> > HugePages_Surp:0
> > Hugepagesize:   2048 kB
> > 
> > FYI.Apr 10 05:12:35 ubuntu1604 /usr/bin/vpp[1720]: dpdk_config:1271: EAL
> > init args: -c 1 -n 4 --huge-dir /run/vpp/hugepages --file-prefix vpp -b
> > :00:05.0 -b :00:06.0 -b :00:07.0 --master-lcore 0 --socket-mem
> > 64
> > 
> >
> > > > Every packet sent from the VM is traversed via VF to the opposite side,
> > > > a pktgen server. 
> > > > And pktgen replies to those packets, but VM does not receive those
> > > > replies.
> > > > (i.e. I ping to pktgen port from VM, where host server port is directly
> > > > linked to pktgen server port.)
> > > >
> > > > Here is my vpp-config script.
>

Re: [vpp-dev] VPP with DPDK drops packet, but it sends ok

[Marco Varlese]

On Tue, 2018-04-10 at 19:33 +0900, Moon-Sang Lee wrote:
> Thanks for your interest, Marco.
> I follows the intel guideline, "As an SR-IOV VF network adapter using a KVM
> virtual network pool of adapters"
> from https://software.intel.com/en-us/articles/configure-sr-iov-network-virtua
> l-functions-in-linux-kvm. 
> 
> In summary, I modprobe ixgbe on host side and creates one VF per PF. 
> When I start VM using virsh, libvirt binds the VF to vfio-pci in host side.
> After VM finishes booting, I login to VM and bind the VF to igb_uio using
> dpdk-dev command.
> (i.e. only igb_uio works and other drivers like uio_pci_generic and vfio-pci
> fail to bind VF in VM side.) 
Yes, that's expected. If you want to use vfio-pci in the VM you'll need to
enable the "no-iommu":# echo 1 >
/sys/module/vfio/parameters/enable_unsafe_noiommu_mode
> I don't edit startup.conf in VM, but I just bind the VF to dpdk-compatible
> driver, igb_uio, inside VM.
> With above configuration, I can bind the VF to guest kernel driver, ixgbevf,
> and also to DPDK PMD, igb_uio.  
> As a result,  I can run VPP without DPDK using ixgbevf, and also DPDK
> applications using igb_uio.
> (i.e. I successfully runs l2fwd/l3fwd sample applications inside VM, so I
> guess VF biding has no problem.)
> 
> However, I cannot run VPP with DPDK and I suspect hugepage is related to this
> problem as shown in my VPP log.  
So, what does the command "cat /proc/meminfo |grep HugePages_" shows?
> Every packet sent from the VM is traversed via VF to the opposite side, a
> pktgen server. 
> And pktgen replies to those packets, but VM does not receive those replies.
> (i.e. I ping to pktgen port from VM, where host server port is directly linked
> to pktgen server port.)  
>  
> Here is my vpp-config script.
> I test ping after running this script. 
> 
> #!/bin/sh
> 
> vppctl enable tap-inject
> vppctl create loopback interface
> vppctl set interface state loop0 up
> 
> vppctl show interface
> vppctl show hardware
> vppctl set interface state VirtualFunctionEthernet0/6/0 up
> vppctl set interface state VirtualFunctionEthernet0/7/0 up
> vppctl set interface ip address loop0 2.2.2.2/32
> vppctl set interface ip address VirtualFunctionEthernet0/6/0 192.168.0.1/24
> vppctl set interface ip address VirtualFunctionEthernet0/7/0 192.168.1.1/24
> vppctl show interface address
> vppctl show tap-inject
> 
> ip addr add 2.2.2.2/32 dev vpp0
> ip addr add 192.168.0.1/24 dev vpp1
> ip addr add 192.168.1.1/24 dev vpp2
> ip link set dev vpp0 up
> ip link set dev vpp1 up
> ip link set dev vpp2 up
> 
> 
> 
> On Tue, Apr 10, 2018 at 4:51 PM, Marco Varlese <mvarl...@suse.de> wrote:
> > On Mon, 2018-04-09 at 22:53 +0900, Moon-Sang Lee wrote:
> > > I've configured a VM with KVM, and the VM is intended to run VPP with
> > > DPDK.
> > > In particular, the VM is connected to one of VFs. (i.e. SR-IOV)
> > > I can run DPDK sample applications,including l2fwd and l3fwd, in the VM, 
> > > therefore I guess VM is successfully connected to the 
> > > outside-world(pktgen 
> > > server) via VFs. 
> > > 
> > > However, I cannot receive a packet when I run VPP/DPDK. 
> > > I can see TX packets from the VM on the opposite side, pktgen server, 
> > > but the VM does not receive any reply from  pktgen server which reports
> > > RX/TX packet count.
> > > (i.e. arping/ping from VM arrives in pktgen, but the reply from pktgen is
> > > not received in VM.)
> > > I found some strange log messages regarding vpp launching as below. 
> > > 
> > > I appreciate for any comment.
> > > Thanks in advance...
> > > 
> > > - Host NIC: Intel 82599 10G NIC (i.e. VF binding with vfio-pci)
> > > - VM: 1 socket 4 vCPU
> > > - VPP: 18.04
> > > - DPDK binding: igb_uio 
> > It isn't clear to me who manages the PF in the host and how you created the
> > VFs (kernel module or via DPDK binding)?
> > 
> > Second, what do you mean by DPDK binding in the last line above?
> > Is that what you have configured in startup.conf in the VM for VPP to be
> > used?
> > 
> > If so, what is the different between VF binding and DPDK binding in your
> > short setup summary above? I'm confused by reading vfio-pci in one place and
> > then igb_uio later on.
> > 
> > Can you provide us with the startup.conf you have in the VM?
> > 
> > Finally, if you are interested in using vfio-pci then you'll need to have
> > the no-IOMMU enabled otherwise you can't use VFIO in the VM... 
> > probably, the easiest would be to use igb_uio every

Re: [vpp-dev] VPP with DPDK drops packet, but it sends ok

[Marco Varlese]

On Mon, 2018-04-09 at 22:53 +0900, Moon-Sang Lee wrote:
> I've configured a VM with KVM, and the VM is intended to run VPP with DPDK.
> In particular, the VM is connected to one of VFs. (i.e. SR-IOV)
> I can run DPDK sample applications,including l2fwd and l3fwd, in the VM, 
> therefore I guess VM is successfully connected to the outside-world(pktgen
> server) via VFs. 
> 
> However, I cannot receive a packet when I run VPP/DPDK. 
> I can see TX packets from the VM on the opposite side, pktgen server, 
> but the VM does not receive any reply from  pktgen server which reports RX/TX
> packet count.
> (i.e. arping/ping from VM arrives in pktgen, but the reply from pktgen is not
> received in VM.)
> I found some strange log messages regarding vpp launching as below. 
> 
> I appreciate for any comment.
> Thanks in advance...
> 
> - Host NIC: Intel 82599 10G NIC (i.e. VF binding with vfio-pci)
> - VM: 1 socket 4 vCPU
> - VPP: 18.04
> - DPDK binding: igb_uio 
It isn't clear to me who manages the PF in the host and how you created the VFs
(kernel module or via DPDK binding)?
Second, what do you mean by DPDK binding in the last line above?Is that what you
have configured in startup.conf in the VM for VPP to be used?
If so, what is the different between VF binding and DPDK binding in your short
setup summary above? I'm confused by reading vfio-pci in one place and then
igb_uio later on.
Can you provide us with the startup.conf you have in the VM?
Finally, if you are interested in using vfio-pci then you'll need to have the
no-IOMMU enabled otherwise you can't use VFIO in the VM... probably, the easiest
would be to use igb_uio everywhere...
> root@xenial-vpp-frr:~# vpp -c /etc/vpp/startup.conf
> vlib_plugin_early_init:359: plugin path /usr/lib/vpp_plugins
> load_one_plugin:187: Loaded plugin: acl_plugin.so (Access Control Lists)
> load_one_plugin:187: Loaded plugin: avf_plugin.so (Intel Adaptive Virtual
> Function (AVF) Device Plugin)
> load_one_plugin:189: Loaded plugin: cdp_plugin.so
> load_one_plugin:187: Loaded plugin: dpdk_plugin.so (Data Plane Development Kit
> (DPDK))
> load_one_plugin:187: Loaded plugin: flowprobe_plugin.so (Flow per Packet)
> load_one_plugin:187: Loaded plugin: gbp_plugin.so (Group Based Policy)
> load_one_plugin:187: Loaded plugin: gtpu_plugin.so (GTPv1-U)
> load_one_plugin:187: Loaded plugin: igmp_plugin.so (IGMP messaging)
> load_one_plugin:187: Loaded plugin: ila_plugin.so (Identifier-locator
> addressing for IPv6)
> load_one_plugin:187: Loaded plugin: ioam_plugin.so (Inbound OAM)
> load_one_plugin:117: Plugin disabled (default): ixge_plugin.so
> load_one_plugin:187: Loaded plugin: kubeproxy_plugin.so (kube-proxy data
> plane)
> load_one_plugin:187: Loaded plugin: l2e_plugin.so (L2 Emulation)
> load_one_plugin:187: Loaded plugin: lacp_plugin.so (Link Aggregation Control
> Protocol)
> load_one_plugin:187: Loaded plugin: lb_plugin.so (Load Balancer)
> load_one_plugin:187: Loaded plugin: memif_plugin.so (Packet Memory Interface
> (experimetal))
> load_one_plugin:187: Loaded plugin: nat_plugin.so (Network Address
> Translation)
> load_one_plugin:187: Loaded plugin: pppoe_plugin.so (PPPoE)
> load_one_plugin:187: Loaded plugin: router.so (router)
> load_one_plugin:187: Loaded plugin: srv6ad_plugin.so (Dynamic SRv6 proxy)
> load_one_plugin:187: Loaded plugin: srv6am_plugin.so (Masquerading SRv6 proxy)
> load_one_plugin:187: Loaded plugin: srv6as_plugin.so (Static SRv6 proxy)
> load_one_plugin:187: Loaded plugin: stn_plugin.so (VPP Steals the NIC for
> Container integration)
> load_one_plugin:187: Loaded plugin: tlsmbedtls_plugin.so (mbedtls based TLS
> Engine)
> load_one_plugin:187: Loaded plugin: tlsopenssl_plugin.so (openssl based TLS
> Engine)
> load_one_plugin:67: Loaded plugin:
> /usr/lib/vpp_api_test_plugins/flowprobe_test_plugin.so
> load_one_plugin:67: Loaded plugin:
> /usr/lib/vpp_api_test_plugins/dpdk_test_plugin.so
> load_one_plugin:67: Loaded plugin:
> /usr/lib/vpp_api_test_plugins/ioam_export_test_plugin.so
> load_one_plugin:67: Loaded plugin:
> /usr/lib/vpp_api_test_plugins/cdp_test_plugin.so
> load_one_plugin:67: Loaded plugin:
> /usr/lib/vpp_api_test_plugins/kubeproxy_test_plugin.so
> load_one_plugin:67: Loaded plugin:
> /usr/lib/vpp_api_test_plugins/ioam_vxlan_gpe_test_plugin.so
> load_one_plugin:67: Loaded plugin:
> /usr/lib/vpp_api_test_plugins/stn_test_plugin.so
> load_one_plugin:67: Loaded plugin:
> /usr/lib/vpp_api_test_plugins/acl_test_plugin.so
> load_one_plugin:67: Loaded plugin:
> /usr/lib/vpp_api_test_plugins/lb_test_plugin.so
> load_one_plugin:67: Loaded plugin:
> /usr/lib/vpp_api_test_plugins/lacp_test_plugin.so
> load_one_plugin:67: Loaded plugin:
> /usr/lib/vpp_api_test_plugins/ioam_pot_test_plugin.so
> load_one_plugin:67: Loaded plugin:
> /usr/lib/vpp_api_test_plugins/pppoe_test_plugin.so
> load_one_plugin:67: Loaded plugin:
> /usr/lib/vpp_api_test_plugins/udp_ping_test_plugin.so
> load_one_plugin:67: Loaded plugin:
> 

Re: [vpp-dev] Sad News from Intel - Venky Venkatesan

[Marco Varlese]

It is a very sad and shocking news. 
Venky was a visioner, a scientist whilst being a humble and kind person. He has
been a mentor to me and it has been a true privilige to get to know him and work
with him. I am sure he'll be missed and remembered by so many people in our
industry.
May he rest in peace.
On Thu, 2018-04-05 at 18:36 +, St Leger, Jim wrote:
> Several of you have already heard the very sad news of the passing of our dear
> friend and colleague Venky.  He was “Mr. DPDK” to many, a nod to his invention
>  and creation of DPDK about ten years ago (before it was called DPDK.)  Of
> course his footprints across the industry and literally across the globe are
> everywhere. If you know what ATCA is, well, Venky had his hands and inventions
> deeply into the creation of
>  that PICMG spec and many of the first revision products. He touched on and
> gave guidance to projects spanning Linux/netdev, DPDK, Intel QuickAssist
> Technology, BSD stacks, OVS, OPNFV, FD.io, all-things-virtualization (KVM,
> Xen, VMware, Hyper-V, etc.), ETSI,
>  IETF, containers, and so many other arenas that my brain can’t remember at
> this dark moment.
>
> If you knew him and engaged him, especially on deep technical discussions, you
> knew you were talking to someone with the rare combination of skills that went
>  incredibly deep both on the hardware, silicon side of platforms but also on
> the software, networking side of the platforms.  Rarely did I find a topic
> that Venky wasn’t well versed on. And by “topic” I mean everything from
> football to photography to history
>  to politics and many other subjects well beyond the technical realm our day
> jobs find us in. Conversations with Venky were a treat. Traveling with him was
> an adventure. Debating with him was a lesson. I will so miss all of him.
>
> Below are some details on a memorial service this Sunday in Oregon and also a
> GoFundMe page. If you’re in Oregon or close by please join the service. Venky
>  left behind a wife, Priya, and two young girls, Adhiti and Namrata. While I’m
> sure they are overwhelmed with sadness and grief at the moment they can use
> our support. Please consider supporting the GoFundMe memorial fund for his
> family.
>
> Lastly, my network extends through this distribution list.  But Venky’s
> network was one hundred times broader. Please share this sad news through your
> own
>  networks. 
>
> Thanks,
> Jim
>
> 
> 
> From: A message from Sandra Rivera
> 
> 
> Sent: Thursday, April 5, 2018 10:58 AM
> 
> Subject: Follow-up: A loss for our NPG organization
> 
> 
>
> All,
> We have an update on the memorial service plans in celebration of Venky
> Venkatesan’s life.
>
> The service will be held on Sunday, April 8th at our Jones Farm Conference
> Center (JFCC) in Hillsboro, OR from 2-4PM, and is open to all
>  who would like to join.
>
> Venky’s family will plan to attend, as well as friends and others who have
> worked closely with him over the years.
> Please note that this is not an Intel-sponsored event and therefore any travel
> or expenses related to attending need to be managed personally.
>
> Many of you have asked about donations, and we have helped setup a GoFundMe
> account for his family which will be used to fund scholarships for his
>  children.
> https://www.gofundme.com/venky-venkatesan-memorial-fund
>
> If you have any questions about the service, please contact
> Udayan Mukherjee.
>
> Thank you all very much for your support during this difficult time.
> Sandra
>
> 
>
> 
>
>
> From: A message from Sandra Rivera 
> 
> Sent: Tuesday, April 3, 2018 9:34 PM
> 
> Subject: A loss for our NPG organization
>
> To All,
> Today is a very sad day for our NPG team and Intel.  Our dear friend and
> colleague, Venky Venkatesan, passed away early morning today after a tough
> battle with cancer.
>
> Aside from his deep contributions to the organization, Venky provided
> technical mentorship to many employees and greatly impacted our technical
> leadership pipeline.
> 
>
> On a personal level, Venky was very dedicated to his family and also cared
> deeply about mentoring the next generation of engineers and scientists through
> efforts like coaching robotics
>  teams and providing guidance to many interns and Intel employees. 
> His passion, dedication and commitment to this organization, Intel, and the
> external community will be greatly missed.
>
> We will let you know as soon as more information is available for Venky’s
> memorial/celebration service.
> Sandra
>
>
>
> 
> 
> 
> 
> 
> 
-- 
Marco V


SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

Re: [vpp-dev] how to compile for Mellanox ConnectX-5 for VPP 18.01 and DPDK 18.02?

[Marco Varlese]

Hi Ronald,

I think you may need to set "vpp_dpdk_shared_lib = yes", I see that is set to
"no" in your configuration pasted below.

Can you try and see if that works for you?


Cheers,
Marco

On Fri, 2018-03-09 at 21:32 +0100, Ronald van der Pol wrote:
> I am trying to get VPP working with a Mellanox ConnectX-5 NIC. I have
> tried various configs, but I cannot get it working.
> 
> This is what I have now:
> 
> I am using:
> $ ofed_info -s
> MLNX_OFED_LINUX-4.3-1.0.1.0
> 
> In dpdk-18.02/config/common_base:
> CONFIG_RTE_LIBRTE_MLX5_PMD=y
> CONFIG_RTE_LIBRTE_MLX5_DEBUG=n
> CONFIG_RTE_LIBRTE_MLX5_DLOPEN_DEPS=y
> CONFIG_RTE_LIBRTE_MLX5_TX_MP_CACHE=8
> 
> $ make config T=x86_64-native-linuxapp-
> gcc
> $ make install T=x86_64-native-linuxapp-gcc DESTDIR=install
> 
> For VPP:
> $ git clone https://gerrit.fd.io/r/vpp
>   
> $ git checkout origin/stable/1801 
> 
> In build-data/platforms/vpp.mk:   
> ---
> --   
> vpp_uses_dpdk_mlx5_pmd =
> yes
> vpp_uses_external_dpdk =
> yes
> vpp_dpdk_inc_dir = /home/rvdp/src/dpdk-
> 18.02/install/include/dpdk   
> vpp_dpdk_lib_dir = /home/rvdp/src/dpdk-
> 18.02/install/lib
> vpp_dpdk_shared_lib =
> no
> - 
> 
> $ make dpdk-install-dev
> DPDK_MLX5_PMD=y 
> $ make install-
> dep
> $ make build-release
> 
> This fails with:
> 
>   CCLD ila_plugin.la
>   CCLD libsixrd_plugin.la
>   CCLD dpdk_plugin.la
> /usr/bin/ld: /home/rvdp/src/dpdk-18.02/install/lib/librte_acl.a(tb_mem.o):
> relocation R_X86_64_32 against `.rodata' can not be used when making a shared
> object; recompile with -fPIC
> /home/rvdp/src/dpdk-18.02/install/lib/librte_acl.a(tb_mem.o): error adding
> symbols: Bad value
> collect2: error: ld returned 1 exit status
> Makefile:1883: recipe for target 'dpdk_plugin.la' failed
> 
> Can somebody tell me what the proper config setting are?
> 
> Thanks,
> 
> rvdp
> 
> 
> 
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#8817): https://lists.fd.io/g/vpp-dev/message/8817
View All Messages In Topic (2): https://lists.fd.io/g/vpp-dev/topic/14304652
Mute This Topic: https://lists.fd.io/mt/14304652/21656
New Topic: https://lists.fd.io/g/vpp-dev/post

Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656
Group Home: https://lists.fd.io/g/vpp-dev
Contact Group Owner: vpp-dev+ow...@lists.fd.io
Terms of Service: https://lists.fd.io/static/tos
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] LOG and ERROR handlers

[Marco Varlese]

On Thu, 2018-03-15 at 10:33 +0200, Sara Gittlin wrote:
> Thank you Keith
> I mean the  error/log macros that write to the log files
Maybe you're looking for clib_warning() ?
> 
> Regards
> -Sara
> 
> On Wed, Mar 14, 2018 at 10:30 PM, Keith Burns  wrote:
> > If using default startup.conf found;
> > src/vpp/conf/startup.conf
> > it is /var/log/vpp/vpp.log
> > 
> > 
> > On Wed, Mar 14, 2018 at 9:27 AM Sara Gittlin  wrote:
> > > 
> > > Hello  All,
> > > 
> > > what are the VPP  standard log and error  handlers ?
> > > 
> > > Thank you
> > > -Sara
> > > 
> > > 
> > > 
> 
> 
> 
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#8551): https://lists.fd.io/g/vpp-dev/message/8551
View All Messages In Topic (4): https://lists.fd.io/g/vpp-dev/topic/14665458
Mute This Topic: https://lists.fd.io/mt/14665458/21656
New Topic: https://lists.fd.io/g/vpp-dev/post

Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656
Group Home: https://lists.fd.io/g/vpp-dev
Contact Group Owner: vpp-dev+ow...@lists.fd.io
Terms of Service: https://lists.fd.io/static/tos
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] VPP build error

[Marco Varlese]

"make dpdk-install-dev" should take care of fixing all that...

On Thu, 2018-03-08 at 15:06 +, Sirshak Das wrote:
> I did get an error on something related to nasm and I installed nasm and went
> past it. I know this is a obvious question but did u try installing nasm
> package via package manager ?
> 
> ++
> Sirshak Das
> > On Mar 8, 2018, at 8:51 AM, Sara Gittlin  wrote:
> > 
> > Hello
> > Has anyone encountered this build error ?
> > --
> > checking whether the C compiler works... no
> > configure: error: in
> > `/home/sarag/vpp/build-root/build-vpp-native/dpdk/nasm-2.13.01':
> > configure: error: C compiler cannot create executables
> > See `config.log' for more details
> > Makefile:294: recipe for target 'build-nasm' failed
> > ---
> > 
> > Thanks in advance
> > -Sara
> > 
> > 
> > 
> 
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy the
> information in any medium. Thank you.
> 
> 
> 
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#8478): https://lists.fd.io/g/vpp-dev/message/8478
View All Messages In Topic (4): https://lists.fd.io/g/vpp-dev/topic/14245689
Mute This Topic: https://lists.fd.io/mt/14245689/21656
New Topic: https://lists.fd.io/g/vpp-dev/post

Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656
Group Home: https://lists.fd.io/g/vpp-dev
Contact Group Owner: vpp-dev+ow...@lists.fd.io
Terms of Service: https://lists.fd.io/static/tos
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] dpdk drivers

[Marco Varlese]

Unless you set the DPDK_DOWNLOAD_DIR environment variable, VPP will keep using
the source downloaded in its default location.
Within the vpp repository, at the top-level directory you find a dpdk folder;
try to look at the Makefile in there to understand the logic. Bottom-line: you
need to specify (via the DPDK_DOWNLOAD_DIR) the location where the DPDK
tarball/source code lives if you are trying to use "your own" modified version
of DPDK...
- Marco
On Thu, 2018-03-08 at 18:20 +0800, xulang wrote:
> Hi all,
> I'v changed a dpdk driver file which is rte_eth_bond_pmd.c,
> Then I would like to compile dpdk to become effiective.
> I start vpp with gdb, and use gdb cmd "list slave_configure", there is no
> change, I hope to hearing  from  you.
> 
>  Here are my operations.
> DPDK compile:
> export RTE_SDK="/home/wangzy/test/VBRASV100R001_trunk/vpp1704/dpdk/dpdk-17.02"
> export RTE_TARGET="x86_64-native-linuxapp-gcc"
> export DESTDIR=/
> make config T=x86_64-native-linuxapp-gcc && make
> make install T=x86_64-native-linuxapp-gcc
> modprobe uio
> insmod build/kmod/igb_uio.ko
> 
> VPP compile:
> make distclean
> ./bootstrap.sh
>  make V=0 PLATFORM=vpp TAG=vpp install-deb
> dpkg -i  *.deb
> 
> GDB result:
> (gdb) list slave_configure
> 1310  }
> 1311  
> 1312  int
> 1313  slave_configure(struct rte_eth_dev *bonded_eth_dev,
> 1314  struct rte_eth_dev *slave_eth_dev)
> 1315  {
> 1316  struct bond_rx_queue *bd_rx_q;
> 1317  struct bond_tx_queue *bd_tx_q;
> 1318  
> 1319  int errval;
> (gdb) 
> 1320  uint16_t q_id;
> 1321  
> 1322  /* Stop slave */
> 1323  rte_eth_dev_stop(slave_eth_dev->data->port_id);
> 1324  
> 1325  /* Enable interrupts on slave device if supported */
> 1326  if (slave_eth_dev->data->dev_flags & RTE_ETH_DEV_INTR_LSC)
> 1327  slave_eth_dev->data->dev_conf.intr_conf.lsc = 1;
> 1328  
> 1329  /* If RSS is enabled for bonding, try to enable it for
> slaves  */
> (gdb) 
> 
> Regards,
> xulang
> 
> 
> 
> 
>
> 
> 
-- 
Marco V


SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

Re: [vpp-dev] download specific version vpp

[Marco Varlese]

Dear Xulang,
Use "git tag -l" to see all the tags applied to the VPP repo.Once you choose the
tag (representing the version you want to use) simply do the "git checkout
NAME_OF_THE_TAG".

- Marco
On Thu, 2018-03-08 at 19:21 +0800, xulang wrote:
> Hi all,
> How could I download one specific version vpp, for example if I would like to
> download version 17.02 with git, what should I do?
> 
> Regards,
> xulang
> 
>
> 
> 
-- 
Marco V


SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

Re: [vpp-dev] VPP DPDK build failure with Mellanox interface(aarch64)

[Marco Varlese]

> ^
>   symbol:   class WantIp6NbrStatsCallback
>   location: package io.fd.vpp.jvpp.core.callback
> jvpp-core/target/io/fd/vpp/jvpp/core/future/FutureJVppCoreFacade.java:1815:
> error: incompatible types: inference variable REPLY has incompatible bounds
> return send(request);
>^
> equality constraints: WantIp4NbrStats
> upper bounds: JVppReply
>   where REPLY,REQ are type-variables:
> REPLY extends JVppReply declared in method <REQ,REPLY>send(REQ)
> REQ extends JVppRequest declared in method <REQ,REPLY>send(REQ)
> jvpp-core/target/io/fd/vpp/jvpp/core/future/FutureJVppCoreFacade.java:1820:
> error: incompatible types: inference variable REPLY has incompatible bounds
> return send(request);
>^
> equality constraints: WantIp6NbrStats
> upper bounds: JVppReply
>   where REPLY,REQ are type-variables:
> REPLY extends JVppReply declared in method <REQ,REPLY>send(REQ)
> REQ extends JVppRequest declared in method <REQ,REPLY>send(REQ)
> 
> 
> If you or anybody else could help me with the issue it will be great.
I see Dave W already replied to you about this and can confirm that the revert
of that patch fixes the above issue.
> 
> Thank you
> Sirshak Das
> 
> 
> Marco Varlese writes:
> 
> > Hi Sirshak,
> > 
> > Can you please take a look at this thread:
> > https://lists.fd.io/g/vpp-dev/message/8219
> > 
> > Also, take a look at http://dpdk.org/doc/guides/nics/mlx5.html for detailed
> > explanations and steps for DPDK to work with Mellanox NICs...
> > 
> > Likely, it's a kernel issue: for Mellanox latest PMD drivers (DPDK 17.11 and
> > above) you're required to have 4.15.x whilst I see you're running 4.10.x
> > 
> > Hope this helps.
> > 
> > 
> > Cheers,
> > Marco
> > 
> > On Thu, 2018-03-01 at 18:02 -0600, Sirshak Das wrote:
> > > Hi all,
> > > 
> > > I am facing an issue with building VPP with DPDK (Mellanox Drivers
> > > enabled) on aarch64.
> > > 
> > > The OFED version installed:
> > > $ ofed_info -s
> > > MLNX_OFED_LINUX-4.2-1.2.0.0:
> > > 
> > > Kernel Version:
> > > $ uname -r
> > > 4.10.0-28-generic
> > > 
> > > Operating System Version:
> > > Ubuntu 16.04.4 LTS (GNU/Linux 4.10.0-28-generic aarch64)
> > > 
> > > gcc version:
> > > gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9)
> > > 
> > > Target Machine:
> > > Qualcomm Centriq
> > > 
> > > lspci:
> > > 0004:01:00.0 Ethernet controller: Mellanox Technologies MT27700 Family
> > > [ConnectX-4]
> > > 
> > > Steps I followed:
> > > 
> > > $ git clone ssh://@gerrit.fd.io:29418/vpp.git
> > > $ cd vpp/
> > > $ sed -i '/vpp_uses_dpdk_mlx5_pmd/s/^# //g' build-data/platforms/vpp.mk
> > > $ make dpdk-install-dev DPDK_MLX5_PMD=y
> > > 
> > > /vpp/dpdk/deb/_build/dpdk-
> > > 18.02/drivers/net/mlx5/mlx5_flow.c:38:8: error: redefinition of ‘struct
> > > ibv_flow_spec_counter_action’
> > >  struct ibv_flow_spec_counter_action {
> > > ^
> > > In file included from /vpp/dpdk/deb/_build/dpdk-
> > > 18.02/drivers/net/mlx5/mlx5_flow.c:14:0:
> > > /usr/include/infiniband/verbs.h:1360:8: note: originally defined here
> > >  struct ibv_flow_spec_counter_action {
> > > 
> > > 
> > > By looking at this file:
> > >  > > DIR>/vpp/dpdk/deb/_build/dpdk-18.02/arm64-armv8a-linuxapp-
> > > gcc/build/drivers/net/mlx5/mlx5_autoconf.h
> > > 
> > > Which looks like this:
> > > 
> > > /* HAVE_IBV_DEVICE_VXLAN_SUPPORT is not defined.
> > > */
> > > 
> > >   
> > > 
> > > 
> > >   
> > > 
> > >   
> > > 
> > >
> > > /* HAVE_IBV_WQ_FLAG_RX_END_PADDING is not defined.
> > > */
> > > 
> > >   
> > > 
> > >   
> > >  

Re: [vpp-dev] Dramatic dropping caused by VPP?

[Marco Varlese]

I wonder if the issue was caused by a different window size used by iperf3 vs
iperf2.
Maybe, worth trying again iperf3 passing the same window size as iperf2. To do
that you need to pass the "-w" option on the command line of iperf2/3. I think
it's worth giving it a try...

- Marco
On Mon, 2018-03-05 at 18:22 +, Hao Fu (haof) wrote:
> Solved by using iperf2 instead.
>
> 
> From:  on behalf of "Hao Fu (haof)" 
> 
> Date: Friday, March 2, 2018 at 11:23 AM
> 
> To: "vpp-dev@lists.fd.io" 
> 
> Subject: [vpp-dev] Dramatic dropping caused by VPP?
> 
> 
>
> 
> Dear All,
>
> I created two vms with vpp installed and connected them with host-net. No drop
> was observed between the two vms with Iperf3.
> 
> I then leverage tap to make the vms talk through vpp.
> In vm compute0: [host 123.0.1.1/24]—tap—[123.0.1.2/24,  GigabitEthernet0/8/0
> (up) 192.167.1.1/24 vpp]
> In vm compute1: [host 123.0.2.1/24]---tap---[123.0.2.2/24,
> GigabitEthernet0/8/0 (up): 192.167.1.2/24 vpp].
>
> Now I can see dramatic drops after calling the cmd “iperf3 -c 123.0.2.1 -u -b
> 1g”:
> Accepted connection from 123.0.1.1, port 59798
> [  5] local 123.0.2.1 port 5201 connected to 123.0.1.1 port 57969
> [ ID] Interval   Transfer Bandwidth   JitterLost/Total
> Datagrams
> [  5]   0.00-1.01   sec  11.6 MBytes  96.5 Mbits/sec  0.088 ms  12300/13783
> (89%)
> [  5]   1.01-2.00   sec  16.0 MBytes   135 Mbits/sec  0.042 ms  13696/15739
> (87%)
> [  5]   2.00-3.00   sec  31.0 MBytes   260 Mbits/sec  0.034 ms  11529/15498
> (74%)
> [  5]   3.00-4.02   sec  12.9 MBytes   106 Mbits/sec  0.048 ms  13361/15009
> (89%)
> [  5]   4.02-5.01   sec  11.5 MBytes  97.5 Mbits/sec  0.065 ms  13925/15400
> (90%)
> [  5]   5.01-6.00   sec  11.2 MBytes  94.9 Mbits/sec  0.038 ms  13521/14958
> (90%)
> [  5]   6.00-7.00   sec  19.4 MBytes   162 Mbits/sec  0.043 ms  12867/15350
> (84%)
> [  5]   7.00-8.00   sec  25.7 MBytes   216 Mbits/sec  0.024 ms  12026/15312
> (79%)
> [  5]   8.00-9.02   sec  21.4 MBytes   177 Mbits/sec  0.035 ms  12529/15268
> (82%)
> [  5]   9.02-10.02  sec  17.4 MBytes   146 Mbits/sec  0.048 ms  12957/15189
> (85%)
> [  5]  10.02-10.04  sec  0.00 Bytes  0.00 bits/sec  0.048 ms  0/0 (-nan%)
>
> Any advice and suggestions will be greatly appreciated.
>
> Thanks,
> Hao
>
> 
> 
> 
> 
> 
> 
> 
> 
> 
-- 
Marco V


SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

Re: [vpp-dev] VPP DPDK build failure with Mellanox interface(aarch64)

[Marco Varlese]

Hi Sirshak,

Can you please take a look at this thread:
https://lists.fd.io/g/vpp-dev/message/8219

Also, take a look at http://dpdk.org/doc/guides/nics/mlx5.html for detailed
explanations and steps for DPDK to work with Mellanox NICs...

Likely, it's a kernel issue: for Mellanox latest PMD drivers (DPDK 17.11 and
above) you're required to have 4.15.x whilst I see you're running 4.10.x

Hope this helps.


Cheers,
Marco

On Thu, 2018-03-01 at 18:02 -0600, Sirshak Das wrote:
> Hi all,
> 
> I am facing an issue with building VPP with DPDK (Mellanox Drivers
> enabled) on aarch64.
> 
> The OFED version installed:
> $ ofed_info -s
> MLNX_OFED_LINUX-4.2-1.2.0.0:
> 
> Kernel Version:
> $ uname -r
> 4.10.0-28-generic
> 
> Operating System Version:
> Ubuntu 16.04.4 LTS (GNU/Linux 4.10.0-28-generic aarch64)
> 
> gcc version:
> gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9)
> 
> Target Machine:
> Qualcomm Centriq
> 
> lspci:
> 0004:01:00.0 Ethernet controller: Mellanox Technologies MT27700 Family
> [ConnectX-4]
> 
> Steps I followed:
> 
> $ git clone ssh://@gerrit.fd.io:29418/vpp.git
> $ cd vpp/
> $ sed -i '/vpp_uses_dpdk_mlx5_pmd/s/^# //g' build-data/platforms/vpp.mk
> $ make dpdk-install-dev DPDK_MLX5_PMD=y
> 
> /vpp/dpdk/deb/_build/dpdk-
> 18.02/drivers/net/mlx5/mlx5_flow.c:38:8: error: redefinition of ‘struct
> ibv_flow_spec_counter_action’
>  struct ibv_flow_spec_counter_action {
> ^
> In file included from /vpp/dpdk/deb/_build/dpdk-
> 18.02/drivers/net/mlx5/mlx5_flow.c:14:0:
> /usr/include/infiniband/verbs.h:1360:8: note: originally defined here
>  struct ibv_flow_spec_counter_action {
> 
> 
> By looking at this file:
>  DIR>/vpp/dpdk/deb/_build/dpdk-18.02/arm64-armv8a-linuxapp-
> gcc/build/drivers/net/mlx5/mlx5_autoconf.h
> 
> Which looks like this:
> 
> /* HAVE_IBV_DEVICE_VXLAN_SUPPORT is not defined.
> */
>   
> 
>   
>   
>
> /* HAVE_IBV_WQ_FLAG_RX_END_PADDING is not defined.
> */
>   
>   
>   
>   
>
> /* HAVE_IBV_MLX5_MOD_MPW is not defined.
> */
>   
> 
>   
>   
>
> /* HAVE_IBV_MLX5_MOD_CQE_128B_COMP is not defined.
> */
>   
>   
>   
>   
>
> /* HAVE_ETHTOOL_LINK_MODE_25G is not defined. */
> 
> /* HAVE_ETHTOOL_LINK_MODE_50G is not defined.
> */
>   
>
>   
>   
>
> /* HAVE_ETHTOOL_LINK_MODE_100G is not defined.
> */
>   
>   
>   
>   
>
> /* HAVE_IBV_DEVICE_COUNTERS_SET_SUPPORT is not defined. */ 
> 
> So I moved my attentions to this file:
> /vpp/dpdk/deb/_build/dpdk-18.02/drivers/net/mlx5/Makefile
> This whole section fails:
> mlx5_autoconf.h.new: $(RTE_SDK)/buildtools/auto-config-
> h.sh
> 
> $Q $(RM) -f --
> '$@'
>   
>
> $Q sh -- '$<' '$@'
> \ 
>   
>
> HAVE_IBV_DEVICE_VXLAN_SUPPORT
> \ 
>   
>   
> infiniband/verbs.h
> \ 
>   
>
> enum IBV_DEVICE_VXLAN_SUPPORT
> \ 
>   
>   
> 

Re: [vpp-dev] Mellanox interface is not binding to vpp on ARM.

[Marco Varlese]

Hi Addi,
I hope you don't mind me redirecting to the email thread covering the exact same
issue  https://lists.fd.io/g/vpp-dev/message/8219You'll find a link to http://dp
dk.org/doc/guides/nics/mlx5.html and some explanations on how to go about the
issue you see...
Hope this helps.

Cheers,Marco
On Wed, 2018-02-28 at 07:21 +,  via Lists.Fd.Io wrote:
> Hi,
> 
> Mellanox card is not binding to vpp but the same process is working for intel
> card.
> 
> Logs :
> ubuntu@vasily:~/khem/vpp/build-root/build-vpp-native/dpdk/dpdk-
> 17.11/usertools$ sudo service vpp status
> ● vpp.service - vector packet processing engine
>Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset:
> enabled)
>Active: active (running) since Wed 2018-02-28 15:09:13 CST; 4s ago
>   Process: 46649 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm
> /dev/shm/vpe-api (code=exited, status=0/SUCCESS)
>   Process: 46687 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited,
> status=0/SUCCESS)
>   Process: 46686 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm
> /dev/shm/vpe-api (code=exited, status=0/SUCCESS)
>  Main PID: 46688 (vpp_main)
> Tasks: 4 (limit: 9830)
>CGroup: /system.slice/vpp.service
>└─46688 /usr/bin/vpp -c /etc/vpp/startup.conf
> 
> Feb 28 15:09:13 vasily vpp[46688]: /usr/bin/vpp[46688]: dpdk_config:1240: EAL
> init args: -c 1 -n 4 --huge-dir /run/vpp/hugepages --file-prefix
> Feb 28 15:09:13 vasily /usr/bin/vpp[46688]: dpdk_config:1240: EAL init args:
> -c 1 -n 4 --huge-dir /run/vpp/hugepages --file-prefix vpp -w 0002
> Feb 28 15:09:13 vasily vpp[46688]: EAL: VFIO support initialized
> Feb 28 15:09:13 vasily vnet[46688]: EAL: VFIO support initialized
> Feb 28 15:09:15 vasily vnet[46688]: unix_physmem_region_iommu_register: ioctl
> (VFIO_IOMMU_MAP_DMA): Invalid argument
> Feb 28 15:09:15 vasily vnet[46688]: unix_physmem_region_iommu_register: ioctl
> (VFIO_IOMMU_MAP_DMA): Invalid argument
> Feb 28 15:09:15 vasily vnet[46688]: unix_physmem_region_iommu_register: ioctl
> (VFIO_IOMMU_MAP_DMA): Invalid argument
> Feb 28 15:09:15 vasily vnet[46688]: unix_physmem_region_iommu_register: ioctl
> (VFIO_IOMMU_MAP_DMA): Invalid argument
> Feb 28 15:09:15 vasily vnet[46688]: dpdk_ipsec_process:1011: not enough DPDK
> crypto resources, default to OpenSSL
> Feb 28 15:09:15 vasily vnet[46688]: dpdk_lib_init:221: DPDK drivers found no
> ports...
> ubuntu@vasily:~/khem/vpp/build-root/build-vpp-native/dpdk/dpdk-
> 17.11/usertools$ sudo vppctl show int
>   Name   Idx   State  Counter 
> Count 
> local00down
> ubuntu@vasily:~/khem/vpp/build-root/build-vpp-native/dpdk/dpdk-
> 17.11/usertools$ sudo vppctl show pci
> Address  Sock VID:PID Link Speed   Driver  Product
> NameVital Product Data
> 0002:f9:00.0   0  15b3:1015   8.0 GT/s x8  uio_pci_generic CX4121A - ConnectX-
> 4 LX SFP28   PN: MCX4121A-ACAT_C12
>   
>  EC: A1
>   
>  SN: MT1729X00861
>   
>  V0: 0x 50 43 49 65 47 65 6e 33 ...
>   
>  RV: 0x a5
> 0002:f9:00.1   0  15b3:1015   8.0 GT/s x8  igb_uio CX4121A - ConnectX-
> 4 LX SFP28   PN: MCX4121A-ACAT_C12
>   
>  EC: A1
>   
>  SN: MT1729X00861
>   
>  V0: 0x 50 43 49 65 47 65 6e 33 ...
>   
>  RV: 0x a5
> ubuntu@vasily:~/khem/vpp/build-root/build-vpp-native/dpdk/dpdk-
> 17.11/usertools$ lspci
> :10:00.0 PCI bridge: Huawei Technologies Co., Ltd. Device 1610 (rev 01)
> 0002:f8:00.0 PCI bridge: Huawei Technologies Co., Ltd. Device 1610 (rev 01)
> 0002:f9:00.0 Ethernet controller: Mellanox Technologies MT27710 Family
> [ConnectX-4 Lx]
> 0002:f9:00.1 Ethernet controller: Mellanox Technologies MT27710 Family
> [ConnectX-4 Lx]
> 0004:88:00.0 PCI bridge: Huawei Technologies Co., Ltd. Device 1610 (rev 01)
> 0005:78:00.0 PCI bridge: Huawei Technologies Co., Ltd. Device 1610 (rev 01)
> 0006:c0:00.0 PCI bridge: Huawei Technologies Co., Ltd. Device 1610 (rev 01)
> 0007:90:00.0 PCI bridge: Huawei Technologies Co., Ltd. Device 1610 (rev 01)
> 0007:91:00.0 VGA compatible controller: Huawei Technologies Co., Ltd. Hi1710
> [iBMC Intelligent Management system chip w/VGA support] (rev 01)
> 000c:20:00.0 PCI bridge: Huawei Technologies Co., Ltd. Device 1610 (rev 01)
> 

Re: [vpp-dev] [Fwd: [dpdk-dev] DPDK 18.02 on ARM64 is broken]

[Marco Varlese]

Hi Brian,

On Thu, 2018-02-22 at 11:48 -0600, Brian Brooks wrote:
> On 02/22 15:35:06, Marco Varlese wrote:
> > Please, see below...
> > 
> > Maybe we should go back to 17.11 as the default version for now
> > (18.02 is broken
> > for arm64 - confirmed over #dpdk channel on IRC).
> > 
> > Alternatively, a workaround is to disable the DPAA stuff:
> > CONFIG_RTE_LIBRTE_DPAA_BUS=n
> > CONFIG_RTE_LIBRTE_DPAA_MEMPOOL=n
> > CONFIG_RTE_LIBRTE_DPAA_PMD=n
> 
> Since there is a specialized dpaa2.mk platform build, would
> it be possible to always disable unused DPDK platform config
> for the native platform build and then re-enable certain DPDK
> config for specialized platform builds like dpaa2.mk?
I am not sure... apparently though, the issue I reported on the DPDK
mailing-list for ARM64 is not the only one. 
I saw another report of something similar by somebody else.
I guess something is simply wrong with the linking stage and it needs
to be looked at upstream by the DPDK community, specifically the DPAA
maintainer(s).
Since, it's an issue not affecting VPP I think it's best to keep follow
the evolution of the problem on the d...@dpdk.org mailing-list. I
pointed that out here since we're consuming DPDK and we just recently
upgraded to 18.02.


Cheers,
Marco
> 
> 
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#8311): https://lists.fd.io/g/vpp-dev/message/8311
View All Messages In Topic (3): https://lists.fd.io/g/vpp-dev/topic/12439043
Mute This Topic: https://lists.fd.io/mt/12439043/21656
New Topic: https://lists.fd.io/g/vpp-dev/post

Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656
Group Home: https://lists.fd.io/g/vpp-dev
Contact Group Owner: vpp-dev+ow...@lists.fd.io
Terms of Service: https://lists.fd.io/static/tos
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] [Fwd: [dpdk-dev] DPDK 18.02 on ARM64 is broken]

[Marco Varlese]

Please, see below...

Maybe we should go back to 17.11 as the default version for now (18.02 is broken
for arm64 - confirmed over #dpdk channel on IRC).

Alternatively, a workaround is to disable the DPAA stuff:
CONFIG_RTE_LIBRTE_DPAA_BUS=n
CONFIG_RTE_LIBRTE_DPAA_MEMPOOL=n
CONFIG_RTE_LIBRTE_DPAA_PMD=n


Cheers,
Marco

 Forwarded Message 
From: Marco Varlese <mvarl...@suse.de>
To: d...@dpdk.org
Subject: [dpdk-dev] DPDK 18.02 on ARM64 is broken
Date: Thu, 22 Feb 2018 15:23:47 +0100

> Hi,
> 
> I am trying to build the latest DPDK (18.02) but facing some issues on ARM64
> platform.
> 
> I'm using the option CONFIG_RTE_MAJOR_ABI to set the SONAME to 18.02.
> 
> = START = 
> The error is connected to building the librte_pmd_dpaa.so. Please, see below:
> [  405s] /usr/lib64/gcc/aarch64-suse-linux/7/../../../../aarch64-suse-
> linux/bin/ld: warning: librte_bus_dpaa.so.18.02, needed by
> /home/abuild/rpmbuild/BUILD/dpdk-18.02/arm64-armv8a-linuxapp-gcc-
> default/lib/librte_pmd_dpaa.so, not found (try using -rpath or -rpath-link)
> [  405s] /usr/lib64/gcc/aarch64-suse-linux/7/../../../../aarch64-suse-
> linux/bin/ld: warning: librte_mempool_dpaa.so.18.02, needed by
> /home/abuild/rpmbuild/BUILD/dpdk-18.02/arm64-armv8a-linuxapp-gcc-
> default/lib/librte_pmd_dpaa.so, not found (try using -rpath or -rpath-link)
> [  405s] /home/abuild/rpmbuild/BUILD/dpdk-18.02/arm64-armv8a-linuxapp-gcc-
> default/lib/librte_pmd_dpaa.so: undefined reference to
> `fman_if_reset_mcast_filt
> er_table@DPDK_17.11'
> [  405s] /home/abuild/rpmbuild/BUILD/dpdk-18.02/arm64-armv8a-linuxapp-gcc-
> default/lib/librte_pmd_dpaa.so: undefined reference to `qman_alloc_pool_range@
> DP
> DK_18.02'
> [  405s] /home/abuild/rpmbuild/BUILD/dpdk-18.02/arm64-armv8a-linuxapp-gcc-
> default/lib/librte_pmd_dpaa.so: undefined reference to `rte_dpaa_portal_init@D
> PD
> K_17.11'
> [  405s] /home/abuild/rpmbuild/BUILD/dpdk-18.02/arm64-armv8a-linuxapp-gcc-
> default/lib/librte_pmd_dpaa.so: undefined reference to `fman_if_add_mac_addr@D
> PD
> K_17.11'
> [  405s] /home/abuild/rpmbuild/BUILD/dpdk-18.02/arm64-armv8a-linuxapp-gcc-
> default/lib/librte_pmd_dpaa.so: undefined reference to `fman_if_disable_rx@DPD
> K_
> 17.11'
> [  405s] /home/abuild/rpmbuild/BUILD/dpdk-18.02/arm64-armv8a-linuxapp-gcc-
> default/lib/librte_pmd_dpaa.so: undefined reference to
> `fman_if_set_fc_threshold
> @DPDK_17.11'
> [  405s] /home/abuild/rpmbuild/BUILD/dpdk-18.02/arm64-armv8a-linuxapp-gcc-
> default/lib/librte_pmd_dpaa.so: undefined reference to `qman_delete_cgr@DPDK_1
> 8.
> 02'
> [  405s] /home/abuild/rpmbuild/BUILD/dpdk-18.02/arm64-armv8a-linuxapp-gcc-
> default/lib/librte_pmd_dpaa.so: undefined reference to `qman_create_cgr@DPDK_1
> 8.
> 02'
> [  405s] /home/abuild/rpmbuild/BUILD/dpdk-18.02/arm64-armv8a-linuxapp-gcc-
> default/lib/librte_pmd_dpaa.so: undefined reference to `qman_dqrr_consume@DPDK
> _1
> 7.11'
> [  405s] /home/abuild/rpmbuild/BUILD/dpdk-18.02/arm64-armv8a-linuxapp-gcc-
> default/lib/librte_pmd_dpaa.so: undefined reference to `qman_global_init@DPDK_
> 17
> .11'
> [  405s] /home/abuild/rpmbuild/BUILD/dpdk-18.02/arm64-armv8a-linuxapp-gcc-
> default/lib/librte_pmd_dpaa.so: undefined reference to
> `fman_if_promiscuous_disa
> ble@DPDK_17.11'
> [  405s] /home/abuild/rpmbuild/BUILD/dpdk-18.02/arm64-armv8a-linuxapp-gcc-
> default/lib/librte_pmd_dpaa.so: undefined reference to `per_lcore_dpaa_io@DPDK
> _1
> 8.02'
> [  405s] /home/abuild/rpmbuild/BUILD/dpdk-18.02/arm64-armv8a-linuxapp-gcc-
> default/lib/librte_pmd_dpaa.so: undefined reference to `dpaa_svr_family@DPDK_1
> 8.
> 02'
> [  405s] /home/abuild/rpmbuild/BUILD/dpdk-18.02/arm64-armv8a-linuxapp-gcc-
> default/lib/librte_pmd_dpaa.so: undefined reference to `fman_if_clear_mac_addr
> @D
> PDK_17.11'
> [  405s] /home/abuild/rpmbuild/BUILD/dpdk-18.02/arm64-armv8a-linuxapp-gcc-
> default/lib/librte_pmd_dpaa.so: undefined reference to `fman_if_enable_rx@DPDK
> _1
> 7.11'
> [  405s] /home/abuild/rpmbuild/BUILD/dpdk-18.02/arm64-armv8a-linuxapp-gcc-
> default/lib/librte_pmd_dpaa.so: undefined reference to `qman_init_fq@DPDK_17.1
> 1'
> [  405s] /home/abuild/rpmbuild/BUILD/dpdk-18.02/arm64-armv8a-linuxapp-gcc-
> default/lib/librte_pmd_dpaa.so: undefined reference to `per_lcore_held_bufs@DP
> DK
> _18.02'
> [  405s] /home/abuild/rpmbuild/BUILD/dpdk-18.02/arm64-armv8a-linuxapp-gcc-
> default/lib/librte_pmd_dpaa.so: undefined reference to `dpaa_logtype_pmd@DPDK_
> 17
> .11'
> [  405s] /home/abuild/rpmbuild/BUILD/dpdk-18.02/arm64-armv8a-linuxapp-gcc-
> default/lib/librte_pmd_dpaa.so: undefined reference to `fman_if_set_maxfrm@DPD
> K_
> 17.11'
> [  405s] /home/abuild/rpmbuild/BUILD/dpdk-18.02/arm64-armv8a-linuxapp-gcc-
> defau

Re: [vpp-dev] make test patch failing on OpenSuse yum

[Marco Varlese]

And yes, indeed, a patch added the below code into Jenkins which is obviously
wrong.


elif [ "${OS_ID}" == "opensuse" ]; then
yum list installed
pip list
fi



- Marco

On Wed, 2018-02-21 at 15:19 +0100, Marco Varlese wrote:
> So, since this whole thing looks suspicious... I have done a bit of
> investigation on our GERRIT and...
> 
> I see the last time that everything was GREEN was yesterday (Feb 20th) when a
> patch on openSUSE kicked off at 17:28pm (https://jenkins.fd.io/job/vpp-verify-
> ma
> ster-opensuse/1647/consoleFull). I am not sure about the timezone used to
> display the time here...
> 
> After that time, few patches were merged on the ci-management side which maybe
> (I am not an expert with Jenkins at all) are causing this hiccup.
> 
> 
> - Marco
> 
> On Wed, 2018-02-21 at 14:34 +0100, Marco Varlese wrote:
> > Hi Keith,
> > 
> > On Wed, 2018-02-21 at 12:46 +, Keith Burns wrote:
> > > https://gerrit.fd.io/r/#/c/10702/ 
> > > 
> > > Fails due to:
> > > "01:58:10 AttributeError: 'RPMDBAdditionalData' object has no attribute
> > > 'yumdb_cache'"
> > > 
> > > 
> > > (ref: https://jenkins.fd.io/job/vpp-verify-master-opensuse/1658/console)
> > > 
> > > 
> > > 
> > > The Google Way-back machine says https://forums.opensuse.org/showthread.ph
> > > p/
> > > 50
> > > 8461-yum-broken
> > > 
> > > Which apart from helpful suggestions like "don't use yum" suggests we may
> > > want
> > > to clear /var/lib/yum/yumdb or that we don't have some folder somewhere
> > > (???)
> > > 
> > > I'm not suggesting a fix since I don't know OpenSUSE, nor do I know how
> > > our
> > > verify VMs are caching things (*cough* DPDK tar *cough*) ... but has
> > > anyone
> > > hit this before?
> > 
> > I haven't seen this before.
> > What looks strange to me - since openSUSE uses 'zypper' as the tool to
> > install/update the distribution - is seeing 'yum' mentioned in the logs...
> >
> > It almost looks like the build was kicked off for openSUSE but running with
> > CentOS commands?
> > 
> > Would you know which commands are executed by the script
> > 01:58:10 [vpp-verify-master-opensuse] $ /bin/bash
> > /tmp/jenkins289299237563396461.sh
> > 
> > (It seems the one generating all those errors...)
> > 
> > > We tried rebasing after the other issues with intrinsics etc bit us, but
> > > this
> > > seems like a "new and improved" form of Jenkins telling us to fetch a rock
> > > :D 
> > > 
> > > 
> > > 
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#8298): https://lists.fd.io/g/vpp-dev/message/8298
View All Messages In Topic (4): https://lists.fd.io/g/vpp-dev/topic/12433083
Mute This Topic: https://lists.fd.io/mt/12433083/21656
New Topic: https://lists.fd.io/g/vpp-dev/post

Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656
Group Home: https://lists.fd.io/g/vpp-dev
Contact Group Owner: vpp-dev+ow...@lists.fd.io
Terms of Service: https://lists.fd.io/static/tos
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] make test patch failing on OpenSuse yum

[Marco Varlese]

So, since this whole thing looks suspicious... I have done a bit of
investigation on our GERRIT and...

I see the last time that everything was GREEN was yesterday (Feb 20th) when a
patch on openSUSE kicked off at 17:28pm (https://jenkins.fd.io/job/vpp-verify-ma
ster-opensuse/1647/consoleFull). I am not sure about the timezone used to
display the time here...

After that time, few patches were merged on the ci-management side which maybe
(I am not an expert with Jenkins at all) are causing this hiccup.


- Marco

On Wed, 2018-02-21 at 14:34 +0100, Marco Varlese wrote:
> Hi Keith,
> 
> On Wed, 2018-02-21 at 12:46 +, Keith Burns wrote:
> > https://gerrit.fd.io/r/#/c/10702/ 
> > 
> > Fails due to:
> > "01:58:10 AttributeError: 'RPMDBAdditionalData' object has no attribute
> > 'yumdb_cache'"
> > 
> > 
> > (ref: https://jenkins.fd.io/job/vpp-verify-master-opensuse/1658/console)
> > 
> > 
> > 
> > The Google Way-back machine says https://forums.opensuse.org/showthread.php/
> > 50
> > 8461-yum-broken
> > 
> > Which apart from helpful suggestions like "don't use yum" suggests we may
> > want
> > to clear /var/lib/yum/yumdb or that we don't have some folder somewhere
> > (???)
> > 
> > I'm not suggesting a fix since I don't know OpenSUSE, nor do I know how our
> > verify VMs are caching things (*cough* DPDK tar *cough*) ... but has anyone
> > hit this before?
> 
> I haven't seen this before.
> What looks strange to me - since openSUSE uses 'zypper' as the tool to
> install/update the distribution - is seeing 'yum' mentioned in the logs...
>
> It almost looks like the build was kicked off for openSUSE but running with
> CentOS commands?
> 
> Would you know which commands are executed by the script
> 01:58:10 [vpp-verify-master-opensuse] $ /bin/bash
> /tmp/jenkins289299237563396461.sh
> 
> (It seems the one generating all those errors...)
> 
> > We tried rebasing after the other issues with intrinsics etc bit us, but
> > this
> > seems like a "new and improved" form of Jenkins telling us to fetch a rock
> > :D 
> > 
> > 
> > 
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#8297): https://lists.fd.io/g/vpp-dev/message/8297
View All Messages In Topic (3): https://lists.fd.io/g/vpp-dev/topic/12433083
Mute This Topic: https://lists.fd.io/mt/12433083/21656
New Topic: https://lists.fd.io/g/vpp-dev/post

Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656
Group Home: https://lists.fd.io/g/vpp-dev
Contact Group Owner: vpp-dev+ow...@lists.fd.io
Terms of Service: https://lists.fd.io/static/tos
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] make test patch failing on OpenSuse yum

[Marco Varlese]

Hi Keith,

On Wed, 2018-02-21 at 12:46 +, Keith Burns wrote:
> https://gerrit.fd.io/r/#/c/10702/ 
> 
> Fails due to:
> "01:58:10 AttributeError: 'RPMDBAdditionalData' object has no attribute
> 'yumdb_cache'"
> 
> 
> (ref: https://jenkins.fd.io/job/vpp-verify-master-opensuse/1658/console)
> 
> 
> 
> The Google Way-back machine says https://forums.opensuse.org/showthread.php/50
> 8461-yum-broken
> 
> Which apart from helpful suggestions like "don't use yum" suggests we may want
> to clear /var/lib/yum/yumdb or that we don't have some folder somewhere (???)
> 
> I'm not suggesting a fix since I don't know OpenSUSE, nor do I know how our
> verify VMs are caching things (*cough* DPDK tar *cough*) ... but has anyone
> hit this before?

I haven't seen this before.
What looks strange to me - since openSUSE uses 'zypper' as the tool to
install/update the distribution - is seeing 'yum' mentioned in the logs...
 
It almost looks like the build was kicked off for openSUSE but running with
CentOS commands?

Would you know which commands are executed by the script
01:58:10 [vpp-verify-master-opensuse] $ /bin/bash
/tmp/jenkins289299237563396461.sh

(It seems the one generating all those errors...)

> We tried rebasing after the other issues with intrinsics etc bit us, but this
> seems like a "new and improved" form of Jenkins telling us to fetch a rock :D 
> 
> 
> 
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#8296): https://lists.fd.io/g/vpp-dev/message/8296
View All Messages In Topic (2): https://lists.fd.io/g/vpp-dev/topic/12433083
Mute This Topic: https://lists.fd.io/mt/12433083/21656
New Topic: https://lists.fd.io/g/vpp-dev/post

Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656
Group Home: https://lists.fd.io/g/vpp-dev
Contact Group Owner: vpp-dev+ow...@lists.fd.io
Terms of Service: https://lists.fd.io/static/tos
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Issues with CentOS jenkins job

[Marco Varlese]

Hi,

This morning I see another issue affecting the CentOS jenkins job. All others
are fine.

The error marking the build as "Verified-1" can be found below.

10:59:17 make[2]: Leaving directory `/w/workspace/vpp-verify-master-
centos7/dpdk'
10:59:17 sudo rpm -Uih vpp-dpdk-devel-17.11-vpp1.x86_64.rpm
10:59:17 
10:59:17package vpp-dpdk-devel-18.02-vpp1.x86_64 (which is newer than
vpp-dpdk-devel-17.11-vpp1.x86_64) is already installed
10:59:17 make[1]: *** [install-rpm] Error 2
10:59:17 make[1]: Leaving directory `/w/workspace/vpp-verify-master-
centos7/dpdk'
10:59:17 make: *** [dpdk-install-dev] Error 2
10:59:17 Build step 'Execute shell' marked build as failure
10:59:17 $ ssh-agent -k

Full logs are here:
https://jenkins.fd.io/job/vpp-verify-master-centos7/9519/consoleFull


Cheers,
-- 
Marco V

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#8279): https://lists.fd.io/g/vpp-dev/message/8279
View All Messages In Topic (1): https://lists.fd.io/g/vpp-dev/topic/12326385
Mute This Topic: https://lists.fd.io/mt/12326385/21656
New Topic: https://lists.fd.io/g/vpp-dev/post

Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656
Group Home: https://lists.fd.io/g/vpp-dev
Contact Group Owner: vpp-dev+ow...@lists.fd.io
Terms of Service: https://lists.fd.io/static/tos
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] [infra-steering] Something wrong with the CentOS repo?

[Marco Varlese]

Done.

Cheers,Marco
On Fri, 2018-02-16 at 09:52 -0500, Dave Wallace wrote:
> Marco,
> 
>   
> 
>   If you haven't already done so, please open a trouble-ticket with
>   LF by sending an email to helpd...@fd.io
> 
>   
> 
>   Thanks,
> 
>   -daw-
> 
>   
> 
> 
> 
> On 02/16/2018 09:36 AM, Marco Varlese
>   wrote:
> 
> 
> 
> >   I tried a 'recheck' and the error is still there so likely is really
> > broken?
> > 
> > On Fri, 2018-02-16 at 13:34 +0100, Marco Varlese wrote:
> > 
> >   
> > > Hi,
> > > 
> > > I am not sure whether this was just an hiccup or something "more serious"
> > > so
> > > just letting you know...
> > > 
> > > Please, see the logs below which happened on the build for CentOS:
> > > 
> > > 09:58:32 REPO_URL: https://nexus.fd.io/content/repositories/fd.io.master.c
> > > ento
> > > s7
> > > 09:58:33 Loaded plugins: fastestmirror, langpacks
> > > 09:59:06 https://nexus.fd.io/content/repositories/fd.io.master.centos7/rep
> > > odat
> > > a/
> > > repomd.xml: [Errno 12] Timeout on https://nexus.fd.io/content/repositories
> > > /fd.
> > > io
> > > .master.centos7/repodata/repomd.xml: (28, 'Operation too slow. Less than
> > > 1000
> > > bytes/sec transferred the last 30 seconds')
> > > 09:59:06 Trying other mirror.
> > > 
> > > [... MANY MORE LOGS SIMILAR TO THE ABOVE ]
> > > 
> > > 10:03:43 https://nexus.fd.io/content/repositories/fd.io.master.centos7/rep
> > > odat
> > > a/
> > > repomd.xml: [Errno 12] Timeout on https://nexus.fd.io/content/repositories
> > > /fd.
> > > io
> > > .master.centos7/repodata/repomd.xml: (28, 'Operation too slow. Less than
> > > 1000
> > > bytes/sec transferred the last 30 seconds')
> > > 10:03:43 Trying other mirror.
> > > 10:03:43 
> > > 10:03:43 
> > > 10:03:43  One of the configured repositories failed (fd.io master branch
> > > latest
> > > merge),
> > > 10:03:43  and yum doesn't have enough cached data to continue. At this
> > > point
> > > the
> > > only
> > > 10:03:43  safe thing yum can do is fail. There are a few ways to work
> > > "fix"
> > > this:
> > > [...]
> > > 10:03:43 failure: repodata/repomd.xml from fdio-master: [Errno 256] No
> > > more
> > > mirrors to try.
> > > 
> > > Full logs at https://jenkins.fd.io/job/vpp-verify-master-centos7/9475/cons
> > > ole
> > > 
> > > 
> > > Cheers,
> > > 
> > >   
> > 
> > 
> 
> 
> 
>   
> 
-- 
Marco V


SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg