From: Stephen Hemminger <stephen@networkplumber.org>
To: RANJEETH NEDUNURI <ranjeethnedunuri9966@gmail.com>
Cc: users@dpdk.org, "dineshramesh46@gmail.com" <dineshramesh46@gmail.com>
Subject: Re: Dpdk test_pmd with pdump
Date: Mon, 6 Mar 2023 08:52:15 -0800 [thread overview]
Message-ID: <20230306085215.59451000@hermes.local> (raw)
In-Reply-To: <CAG6azpyHMea053uz88f_KCbhpaf6x901FKRRG=+X=eCY+5jqxw@mail.gmail.com>
On Wed, 1 Mar 2023 11:55:21 +0530
RANJEETH NEDUNURI <ranjeethnedunuri9966@gmail.com> wrote:
> Hi ,
> I hope you are doing great, I have gone through your patches related to
> dpdk,I am working on dpdk, while executing dpdk testpmd and pdump we are
> getting errors.
> We are using dpdk 22.07 version and virtual nic on top of physical nic in
> Linux
This is not a supported version, please use 22.11.
> We are following this link:
> https://www.intel.com/content/www/us/en/developer/articles/technical/dpdk-packet-capture-framework.html
Intel article is out of date, it pre-dates meson build etc.
The current docs for pdump is on website:
https://doc.dpdk.org/guides/tools/pdump.html
> Error: EAL: failed to parse device "EAL: failed to parse device
> "vdev:net_pcap_rx_0" EAL: Failed to hotplug add device on primary"
>
> And one more how to give pcap file input to testpmd.
>
> Could you please answer this we very thankful to you.
You may find that the newer DPDK dumpcap application is easier to work with.
It has less dependencies and more options.
https://doc.dpdk.org/guides/tools/dumpcap.html
prev parent reply other threads:[~2023-03-06 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 6:25 RANJEETH NEDUNURI
2023-03-01 14:49 ` RANJEETH NEDUNURI
2023-03-06 16:52 ` Stephen Hemminger [this message]
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=20230306085215.59451000@hermes.local \
--to=stephen@networkplumber.org \
--cc=dineshramesh46@gmail.com \
--cc=ranjeethnedunuri9966@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).