From: Stephen Hemminger <stephen@networkplumber.org>
To: 廖書華 <sim860927@gmail.com>
Cc: users@dpdk.org
Subject: Re: Troubles using pdump to capture the packets
Date: Wed, 13 Oct 2021 09:55:39 -0700 [thread overview]
Message-ID: <20211013095539.2169b008@hermes.local> (raw)
In-Reply-To: <CANq=q420eozrKh_jE1TLt+zysaaHZS4rwLMFafGRJV3icsOU3A@mail.gmail.com>
On Wed, 13 Oct 2021 14:10:17 +0800
廖書華 <sim860927@gmail.com> wrote:
> Dear all,
>
> In our environment, the DPDK version is for 19.11.
> Currently, we try to use pdump to capture the packet of our own
> application, however, we got the below error in our application and pdump
> respectively. (If we replace our application with test-pmd, pdump will not
> get the error)
>
> Error in our application :
> EAL: failed to parse device “vdev:net_pcap_rx_0”
The pdump support requires the pcap PMD to be enabled in the build.
What is your DPDK config?
next prev parent reply other threads:[~2021-10-13 16:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 6:10 廖書華
2021-10-13 16:55 ` Stephen Hemminger [this message]
2021-10-14 1:28 ` 廖書華
2021-10-14 9:51 ` Pattan, Reshma
2021-10-15 4:16 ` 廖書華
2021-10-15 10:33 ` Pattan, Reshma
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=20211013095539.2169b008@hermes.local \
--to=stephen@networkplumber.org \
--cc=sim860927@gmail.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).