DPDK usage discussions
 help / color / mirror / Atom feed
From: Licj <272465698@qq.com>
To: USERS <USERS@DPDK.ORG>
Subject: [dpdk-users] Dpdk-pdump fails with error "no ethernet port" when running with Mellanox MCX454A-FCAT nic
Date: Wed, 17 Jun 2020 17:11:56 +0800	[thread overview]
Message-ID: <tencent_5CC5AD70D89A9CE5178B04EE2B08F5E2E909@qq.com> (raw)

Hi all,&nbsp;

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).


&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".
The initial info with dpdk-pdump shows that it only probes ixgbe driver and 2 Intel nics But not Mellanox nic.&nbsp;


Anyone knows why and how to solve it? Thank you.

             reply	other threads:[~2020-06-17 20:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-17  9:11 Licj [this message]
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

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_5CC5AD70D89A9CE5178B04EE2B08F5E2E909@qq.com \
    --to=272465698@qq.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).