Re: [vpp-dev] Packet processing time.

resources in unicast, don’t hesitate to contact me :) Cheers, Mohammed Hawari Software Engineer & PhD student Cisco Systems > On 18 Apr 2020, at 22:14, Dave Barach via lists.fd.io > wrote: > > If you turn on the main loop dispatch event logs and look at the results in > the

Re: [vpp-dev] Latest master, dpdk and mlx5 failing

Hello Chris, Matthew, Thanks for raising that issue. Just to be clear and better understand, does the problem occur with the default config, i.e., without trying to compile any MLX driver in DPDK? Or does it only appear when setting DPDK_MLX5_PMD=y ? Thanks Best regards Mohammed > On 1 Oct 2020,

Re: [vpp-dev] vpp crashing on latest master branch with mlx5 enabled

Hi Ashish, The DPDK plugin for mlx5 NICs is not supported by the current code on master. We strongly encourage you to try the rdma plugin, which offers a native VPP driver for mlx5 NICs without relying on DPDK. The use of this driver is documented in src/plugins/rdma/rdma_doc.md. Best regards

Re: [vpp-dev] vpp crashing on latest master branch with mlx5 enabled

Hi Ashish, Support for the DPDK plugin with Mellanox cards has been restored on master since https://gerrit.fd.io/r/c/vpp/+/30051 . However, I can’t stress enough that you should get better performance (and more stability) with the rdma plugin. Due to the D

Re: [vpp-dev] vpp unable to send or receive packets

Hi Ashish, Given that -12 corresponds to -ENOMEM in the DPDK source code, I would suggest to increase the number of buffers allocated, via the buffers-per-numa option in startup.conf. Regards Mohammed > On 11 Jan 2021, at 15:27, ashish.sax...@hsc.com wrote: > > Hi All, > > We are using vpp-

Re: [vpp-dev] DPDK change in link speed convention

Hi everyone, I agree with opinion #3 as well. It allows us to keep 0 as “unknown" (i.e., not set by the driver), and we can specify ~0 as “Not Applicable” (typically the case for virtual links) and change format_vnet_hw_interface_link_speed accordingly. Best regards, Mohammed > On 18 Jan 202

Re: [vpp-dev] vpp crashing on latest master branch with mlx5 enabled

Hi Ashish, Building DPDK with mlx support in the VPP build system is experimental and not well tested (especially with CentOS), as I explained in my previous email. Don’t hesitate to contribute patches if you want to improve that support, I’ll happily take a look and help. About your issue, ple

Re: [vpp-dev] How to enable Mellanox compilation in VPP 21.01

Hi Chetan, If you are using CentOS, I’d suggest to cherry-pick https://gerrit.fd.io/r/c/vpp/+/31876 . Also please change the dpdk.mk to also set DPDK_MLX5_COMMON_PMD = y. I hope this solves your issue. Otherwise, please consider using the rdma native drive

Re: [vpp-dev] How to enable Mellanox compilation in VPP 21.01

gt; 'drivers/a715181@@tmp_rte_net_mlx4@sta/net_mlx4_mlx4_flow.c.o' > > ninja: build stopped: subcommand failed. > > On Thu, Apr 1, 2021 at 4:33 PM Юрий Иванов <mailto:format_...@outlook.com>> wrote: > Hi, > > Or you can use nativa rdma driver as written

Re: [vpp-dev] How to enable Mellanox compilation in VPP 21.01

lt;mailto:gmail@lists.fd.io>> wrote: > Thanks a lot Mohammed! > > Let me try with the rdma-core and patch mentioned by you and > > Thanks, > Chetan > > On Wed, Apr 14, 2021 at 6:20 PM Mohammed Hawari <mailto:moham...@hawari.fr>> wrote: > Hi Cheta

Re: [vpp-dev] How to enable Mellanox compilation in VPP 21.01

n, which I was not able to achieve yet. > Or am I completely wrong? > > Best regards > Julius > > On Fri, 16 Apr 2021 at 09:49, Mohammed Hawari <mailto:moham...@hawari.fr>> wrote: > > Hi Chetan, > >> On 16 Apr 2021, at 07:04, chetan bhasin > <mailto:

Re: [vpp-dev] How to enable Mellanox compilation in VPP 21.01

:= y > +DPDK_MLX5_PMD:= y > +DPDK_MLX5_COMMON_PMD := y > DPDK_TAP_PMD ?= n > DPDK_FAILSAFE_PMD ?= n > DPDK_MACHINE ?= default > > Best regards > Julius > > On Fri, 16 Apr 2021 at 17:27, Mohammed H

Re: [vpp-dev] vlib_get_plugin_symbol returning null after upgrading to 21.06 version

Hi, Please note that starting with v21.01, plugin symbols are hidden by default and can’t be used from another plugin (or any other linked object). You need to add the __clib_export attribute to the symbols you want to expose to other plugins. For example, in the dns plugin, the dns_resolve_nam

Re: [vpp-dev] vlib_get_plugin_symbol returning null after upgrading to 21.06 version

The cleanest solution would be to write a wrapper for each one of those autogenerated functions, and mark the wrapper as __clib_export Best regards Mohammed > On 29 Sep 2021, at 15:46, Satya Murthy wrote: > > This works fine for me where the code is fully written by us. > But, I have few funct