Unable to run dpdk -dumpcap with Mellanox

Unable to run dpdk -dumpcap with Mellanox

[Ariba Ehtesham]

[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]

Hi ,
Can someone please guide me about dpdk dumpcap application with testpmd .
while running application I am getting following errors:

sudo ./build/app/dpdk-dumpcap  -i 04:00.1 -w /tmp/capture.pcapng
Device 0000:04:00.0 is not driven by the primary process
mlx5_net: can not attach rte ethdev
mlx5_net: probe of PCI device 0000:04:00.0 aborted after encountering an error: Cannot allocate memory
mlx5_common: Failed to load driver mlx5_eth
EAL: Requested device 0000:04:00.0 cannot be used
Device 0000:04:00.1 is not driven by the primary process
mlx5_net: can not attach rte ethdev
mlx5_net: probe of PCI device 0000:04:00.1 aborted after encountering an error: Cannot allocate memory
mlx5_common: Failed to load driver mlx5_eth
EAL: Requested device 0000:04:00.1 cannot be used
Device 0000:81:00.0 is not driven by the primary process
mlx5_net: can not attach rte ethdev
mlx5_net: probe of PCI device 0000:81:00.0 aborted after encountering an error: Cannot allocate memory
mlx5_common: Failed to load driver mlx5_eth
EAL: Requested device 0000:81:00.0 cannot be used
Device 0000:81:00.1 is not driven by the primary process
mlx5_net: can not attach rte ethdev
mlx5_net: probe of PCI device 0000:81:00.1 aborted after encountering an error: Cannot allocate memory
mlx5_common: Failed to load driver mlx5_eth
EAL: Requested device 0000:81:00.1 cannot be used
EAL: Error - exiting with code: 1
  Cause: No Ethernet ports found

Commands :
dpdk -22.03
sudo ./build/app/dpdk-dumpcap  -i 04:00.1 -w /tmp/capture.pcapng

sudo ./build/app/dpdk-testpmd -c 0xf0 -n 4 -a 04:00.1 -- -i --port-topology=chained



Regards,
Ariba Ehtesham


[-- Attachment #2: Type: text/html, Size: 4964 bytes --]

Re: Unable to run dpdk -dumpcap with Mellanox

[Дмитрий Степанов]

[-- Attachment #1: Type: text/plain, Size: 2030 bytes --]

Have you allocated huge pages?
http://doc.dpdk.org/guides/linux_gsg/sys_reqs.html#use-of-hugepages-in-the-linux-environment
Check huge pages using ./dpdk-hugepages.py -s

вт, 29 мар. 2022 г. в 11:21, Ariba Ehtesham <ariba@dreambigsemi.com>:

> Hi ,
> Can someone please guide me about dpdk dumpcap application with testpmd .
> while running application I am getting following errors:
>
> sudo ./build/app/dpdk-dumpcap  -i 04:00.1 -w /tmp/capture.pcapng
> Device 0000:04:00.0 is not driven by the primary process
> mlx5_net: can not attach rte ethdev
> mlx5_net: probe of PCI device 0000:04:00.0 aborted after encountering an
> error: Cannot allocate memory
> mlx5_common: Failed to load driver mlx5_eth
> EAL: Requested device 0000:04:00.0 cannot be used
> Device 0000:04:00.1 is not driven by the primary process
> mlx5_net: can not attach rte ethdev
> mlx5_net: probe of PCI device 0000:04:00.1 aborted after encountering an
> error: Cannot allocate memory
> mlx5_common: Failed to load driver mlx5_eth
> EAL: Requested device 0000:04:00.1 cannot be used
> Device 0000:81:00.0 is not driven by the primary process
> mlx5_net: can not attach rte ethdev
> mlx5_net: probe of PCI device 0000:81:00.0 aborted after encountering an
> error: Cannot allocate memory
> mlx5_common: Failed to load driver mlx5_eth
> EAL: Requested device 0000:81:00.0 cannot be used
> Device 0000:81:00.1 is not driven by the primary process
> mlx5_net: can not attach rte ethdev
> mlx5_net: probe of PCI device 0000:81:00.1 aborted after encountering an
> error: Cannot allocate memory
> mlx5_common: Failed to load driver mlx5_eth
> EAL: Requested device 0000:81:00.1 cannot be used
> EAL: Error - exiting with code: 1
>   Cause: No Ethernet ports found
>
> *Commands :*
> *dpdk -22.03*
>
> *sudo ./build/app/dpdk-dumpcap  -i 04:00.1 -w /tmp/capture.pcapng *
>
>
> *sudo ./build/app/dpdk-testpmd -c 0xf0 -n 4 -a 04:00.1 -- -i
> --port-topology=chained *
>
>
>
> Regards,
> Ariba Ehtesham
>
>

[-- Attachment #2: Type: text/html, Size: 5156 bytes --]

Re: Unable to run dpdk -dumpcap with Mellanox

[Stephen Hemminger]

On Fri, 25 Mar 2022 08:00:45 +0000
Ariba Ehtesham <ariba@dreambigsemi.com> wrote:

> sudo ./build/app/dpdk-dumpcap  -i 04:00.1 -w /tmp/capture.pcapng
> Device 0000:04:00.0 is not driven by the primary process

First you must have a primary process running doing something.
DPDK-dumpcap is a secondary only process.

The interface you gave is not being controlled by primary process.
Use dpdk-dumpcap -D described in documentation to show the available
devices.