DPDK usage discussions
 help / color / mirror / Atom feed
From: Licj <272465698@qq.com>
To: "Stephen Hemminger" <stephen@networkplumber.org>
Cc: USERS <users@dpdk.org>
Subject: Re: [dpdk-users] Dpdk-pdump fails with error "no ethernet port" when running with Mellanox MCX454A-FCAT nic
Date: Thu, 18 Jun 2020 10:33:22 +0800	[thread overview]
Message-ID: <tencent_17CC8440F1E7E284381F4D28F23145EDF708@qq.com> (raw)
In-Reply-To: <20200617080005.75ac1ed9@hermes.lan>

Thank you.


I have enabled Mellanox mlx5 driver and recompiled dpdk. The testpmd is running ok.


The problem is dpdk-pdump can't run with testpmd.


------------------ Original ------------------
From: Stephen Hemminger <stephen@networkplumber.org&gt;
Date: Wed,Jun 17,2020 11:00 PM
To: Licj <272465698@qq.com&gt;
Cc: USERS <USERS@DPDK.ORG&gt;
Subject: Re: [dpdk-users] Dpdk-pdump fails with error "no ethernet port" when running with Mellanox MCX454A-FCAT nic



On Wed, 17 Jun 2020 17:22:49 +0800
"Licj" <272465698@qq.com&gt; wrote:

&gt; Hi all, 
&gt; 
&gt; I have run dpdk testpmd successfully with Mellanox MCX454A-FCAT nic(mlx5 driver). I can capture the dpdk packets on the recv side using tcpdump. But the througput does not reach line rate(24gbps throughput with 40gbps line rate).
&gt; 
&gt; 
&gt; &amp;nbsp;Then I want to capture packets on the send side using dpdk-pdump. But the dpdk-pdump failed with error "No Ethernet ports - bye".
&gt; The initial info with dpdk-pdump shows that it only probes ixgbe driver and 2 Intel nics But not Mellanox nic. 
&gt; 
&gt; 
&gt; Anyone knows why and how to solve it? Thank you.

Mellanox DPDK drivers are not enabled by default in the build.
You need to have rdma-core installed and enable it in the DPDK build config file.

  reply	other threads:[~2020-06-18  2:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-17  9:22 Licj
2020-06-17 14:16 ` Nishant Verma
2020-06-17 15:00 ` Stephen Hemminger
2020-06-18  2:33   ` Licj [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-06-17  9:11 Licj

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=tencent_17CC8440F1E7E284381F4D28F23145EDF708@qq.com \
    --to=272465698@qq.com \
    --cc=stephen@networkplumber.org \
    --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).