DPDK usage discussions
 help / color / mirror / Atom feed
From: "Дмитрий Степанов" <stepanov.dmit@gmail.com>
To: Ariba Ehtesham <ariba@dreambigsemi.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: Unable to run dpdk -dumpcap with Mellanox
Date: Tue, 29 Mar 2022 11:56:35 +0300	[thread overview]
Message-ID: <CA+-SuJ2Q9szTpwd8YvmFewyc1yCBfweWud3jU2VJ9nEAGf6HPg@mail.gmail.com> (raw)
In-Reply-To: <MW3PR22MB2332D050C9F7F1EA2EE7D68CCD1A9@MW3PR22MB2332.namprd22.prod.outlook.com>

[-- 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 --]

  reply	other threads:[~2022-03-29  8:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25  8:00 Ariba Ehtesham
2022-03-29  8:56 ` Дмитрий Степанов [this message]
2022-04-01  6:18 ` Stephen Hemminger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+-SuJ2Q9szTpwd8YvmFewyc1yCBfweWud3jU2VJ9nEAGf6HPg@mail.gmail.com \
    --to=stepanov.dmit@gmail.com \
    --cc=ariba@dreambigsemi.com \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).