* Unable to run dpdk -dumpcap with Mellanox
@ 2022-03-25 8:00 Ariba Ehtesham
2022-03-29 8:56 ` Дмитрий Степанов
2022-04-01 6:18 ` Stephen Hemminger
0 siblings, 2 replies; 3+ messages in thread
From: Ariba Ehtesham @ 2022-03-25 8:00 UTC (permalink / raw)
To: users
[-- 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 --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Unable to run dpdk -dumpcap with Mellanox
2022-03-25 8:00 Unable to run dpdk -dumpcap with Mellanox Ariba Ehtesham
@ 2022-03-29 8:56 ` Дмитрий Степанов
2022-04-01 6:18 ` Stephen Hemminger
1 sibling, 0 replies; 3+ messages in thread
From: Дмитрий Степанов @ 2022-03-29 8:56 UTC (permalink / raw)
To: Ariba Ehtesham; +Cc: users
[-- 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 --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Unable to run dpdk -dumpcap with Mellanox
2022-03-25 8:00 Unable to run dpdk -dumpcap with Mellanox Ariba Ehtesham
2022-03-29 8:56 ` Дмитрий Степанов
@ 2022-04-01 6:18 ` Stephen Hemminger
1 sibling, 0 replies; 3+ messages in thread
From: Stephen Hemminger @ 2022-04-01 6:18 UTC (permalink / raw)
To: Ariba Ehtesham; +Cc: users
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-04-01 6:18 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-03-25 8:00 Unable to run dpdk -dumpcap with Mellanox Ariba Ehtesham
2022-03-29 8:56 ` Дмитрий Степанов
2022-04-01 6:18 ` Stephen Hemminger
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).