[vpp-dev] 1 week until VPP 22.06 RC1 milestone !

2022-05-18 Thread Andrew Yourtchenko
Hi all,

Just a gentle reminder that on the 25th May, or, less than in a week’s time, at 
12:00 UTC I will be cutting the branch stable/2206 for the upcoming release and 
preparing the RC1 artifacts. Please let me know by Friday if there is any 
changes they you need merged that still are not in. Thanks!  

--a /* your friendly 22.06 release manager */
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21418): https://lists.fd.io/g/vpp-dev/message/21418
Mute This Topic: https://lists.fd.io/mt/91195528/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] Query on VPP in Aure

2022-05-18 Thread John Martinez
Hello Matt,

Can you *please *confirm which DPDK and VPP versions you have that are
working in Azure?

I am hoping to get a base build with no errors and the ability to set MTU
size...

*Thank you in advance for your help!!!*

--
John M.


On Mon, May 2, 2022 at 1:42 PM Matthew Smith  wrote:

>
> Sorry, there was a typo. You should use DPDK_MLX5_COMMON_PMD=y instead
> of DPDK_MLX_COMMON_PMD=y.
>
> -Matt
>
>
> On Mon, May 2, 2022 at 11:28 AM Johnny Martinez 
> wrote:
>
>> Hello Matt!
>>
>> *Thank you very much for the reply!*
>>
>> Our end goal is to be using Alma Linux but we went ahead and tried it in
>> a fresh Ubuntu 20.04 installation with the same result.
>>
>> It looks like it is unable to compile the *mlx5 drivers*.
>>
>> *I’ve attached the complete build log for your review.*
>>
>>
>>
>> *Build was started with:*
>>
>> *make DPDK_MLX4_PMD=y DPDK_MLX5_PMD=y DPDK_MLX_COMMON_PMD=y pkg-deb | tee
>> /root/vpp-build.log*
>>
>>
>>
>> As an extra precaution, the vpp.mk content is:
>>
>>
>>
>> *MACHINE=$(shell uname -m)*
>>
>> *vpp_arch = native*
>>
>> *vpp_root_packages = vpp*
>>
>> *vpp_debug_TAG_BUILD_TYPE = debug*
>>
>> *vpp_TAG_BUILD_TYPE = release*
>>
>> *vpp_clang_TAG_BUILD_TYPE = release*
>>
>> *vpp_gcov_TAG_BUILD_TYPE = gcov*
>>
>> *vpp_coverity_TAG_BUILD_TYPE = coverity*
>>
>> *vpp_dpdk_inc_dir = /usr/include/dpdk/*
>>
>> *vpp_dpdk_lib_dir = /usr/lib64/*
>>
>> *vpp_uses_dpdk_mlx4_pmd = yes*
>>
>> *DPDK_MLX4_PMD=y*
>>
>> *DPDK_MLX5_PMD=y*
>>
>> *DPDK_MLX_COMMON_PMD=y*
>>
>>
>>
>> The build completes, but there’s an issue with the MLX5 driver. As seen
>> in the build log, the *MLX4 is built, but MLX5 is not*. I’ve tried
>> searching online, but there’s reference to *glue* with regard to the
>> MLX5, but nothing actionable I could find:
>>
>>
>>
>> *Part 1: Shows that the library “mlx4” and “mlx5” are included as part of
>> “make” (means our build options were correctly interperated):*
>>
>>
>>
>> *cmake3 --build
>> /root/azure/vpp/build-root/rpmbuild/vpp-22.06/build-root/build-vpp-native/external/build-rdma-core
>> -- libccan.a libibverbs.a librdma_util.a libmlx5.a libmlx4.a >
>> /root/azure/vpp/build-root/rpmbuild/vpp-22.06/build-root/build-vpp-native/external/rdma-core.build.log*
>>
>> *sed 's/^Libs.private:.*/Libs.private: -lmlx4 -lmlx5 -libverbs
>> -lrdma_util -lccan -lpthread/' -i
>> /root/azure/vpp/build-root/rpmbuild/vpp-22.06/build-root/build-vpp-native/external/build-rdma-core/lib/pkgconfig/libibverbs.pc
>> >>
>> /root/azure/vpp/build-root/rpmbuild/vpp-22.06/build-root/build-vpp-native/external/rdma-core.build.log*
>>
>>
>> *Part 2: Shows that MLX5 is missing “common_mlx5” (which I can’t find a
>> way to install…?) so is disabled. MLX4 however, is built:*
>>
>>
>>
>> *Using 'PKG_CONFIG_PATH' from environment with value:
>> '/root/azure/vpp/build-root/rpmbuild/vpp-22.06/build-root/install-vpp-native/external/lib/pkgconfig'*
>>
>> *Run-time dependency libmlx4 found: YES 1.0.39.1*
>>
>> *Using 'PKG_CONFIG_PATH' from environment with value:
>> '/root/azure/vpp/build-root/rpmbuild/vpp-22.06/build-root/install-vpp-native/external/lib/pkgconfig'*
>>
>> *Run-time dependency libibverbs found: YES 1.14.39.1*
>>
>> *Compiler for C supports arguments -std=c11: YES*
>>
>> *Compiler for C supports arguments -Wno-strict-prototypes
>> -Wstrict-prototypes: YES*
>>
>> *Compiler for C supports arguments -D_BSD_SOURCE: YES*
>>
>> *Compiler for C supports arguments -D_DEFAULT_SOURCE: YES*
>>
>> *Compiler for C supports arguments -D_XOPEN_SOURCE=600: YES*
>>
>> *Header  has symbol
>> "MLX4DV_SET_CTX_ATTR_BUF_ALLOCATORS" with dependencies libmlx4, libibverbs:
>> YES*
>>
>> *Header  has symbol "MLX4DV_QP_MASK_UAR_MMAP_OFFSET"
>> with dependencies libmlx4, libibverbs: YES*
>>
>> *Checking whether type "struct mlx4_wqe_lso_seg" has member
>> "mss_hdr_size" with dependencies libmlx4, libibverbs: YES*
>>
>> *Configuring mlx4_autoconf.h using configuration*
>>
>> *Compiler for C supports arguments -std=c11: YES*
>>
>> *Compiler for C supports arguments -Wno-strict-prototypes
>> -Wstrict-prototypes: YES*
>>
>> *Compiler for C supports arguments -D_BSD_SOURCE: YES*
>>
>> *Compiler for C supports arguments -D_DEFAULT_SOURCE: YES*
>>
>> *Compiler for C supports arguments -D_XOPEN_SOURCE=600: YES*
>>
>> *Message: Disabling mlx5 [drivers/net/mlx5]: missing internal dependency
>> "common_mlx5"*
>>
>> *Run-time dependency libmusdk found: NO (tried pkgconfig)*
>>
>> *Run-time dependency libmusdk found: NO (tried pkgconfig)*
>>
>> *Run-time dependency netcope-common found: NO (tried pkgconfig)*
>>
>>
>>
>> *Part 3: Shows multiple missing “internal dependency” issues:*
>>
>>
>>
>> *Message: Disabling dpaa [drivers/dma/dpaa]: missing internal dependency
>> "bus_dpaa"*
>>
>> *Message: Disabling dpaa [drivers/net/dpaa]: missing internal dependency
>> "mempool_dpaa"*
>>
>> *Message: Disabling kni [drivers/net/kni]: missing internal dependency
>> "kni"*
>>
>> *Message: Disabling mlx5 [drivers/net/mlx5]: missing internal dependency
>> 

[vpp-dev] hw_if_index API

2022-05-18 Thread Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) via lists.fd.io

TL;DR: Is there an API way to get hw_if_index value?

CLI "show hardware-interfaces" works for humans,
but some parsing is needed for machines to extract the index value.

For software interfaces, there is sw_interface_dump,
but I do not see any API way to get hw_if_index.

API users need that value for calls related to hardware capabilities:
flow_enable, flow_disable, vxlan_offload_rx and gtpu_offload_rx
(implementations call vnet_get_hw_interface).

Some of them are used in CSIT, which happens to work [0]
just because that suite does not create any non-hardware interfaces
(before the target hardware interface is created).

Vratko.

[0] 
https://gerrit.fd.io/r/c/csit/+/36120/4/resources/libraries/python/InterfaceUtil.py#1127

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21416): https://lists.fd.io/g/vpp-dev/message/21416
Mute This Topic: https://lists.fd.io/mt/91183386/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-