From: Stephen Hemminger <stephen@networkplumber.org>
To: Jon Ross <jonross@gmail.com>
Cc: users@dpdk.org
Subject: Re: how to enable lib_pdump?
Date: Wed, 19 Jan 2022 08:37:29 -0800 [thread overview]
Message-ID: <20220119083729.48d9732b@hermes.local> (raw)
In-Reply-To: <CA+CupnzA9ZAjWOqMQFVgV81wSOfHm7jasH2JXYyCLoP8EwzKmA@mail.gmail.com>
On Tue, 18 Jan 2022 10:42:16 -0800
Jon Ross <jonross@gmail.com> wrote:
> dpdk-dumpcap works fine w/ dpdk-testpmd running, but I can't get it to
> work while my app is running.
>
> The docs say to do it the way testmpd does it. But testpmd does...
> everything? It's hard to tell what's needed to get capture working.
>
You need at a minimum:
1. primary/secondary process support
2. ethedev rx/tx callbacks enabled
3. rte_pdump_init() called in primary
4. enough shared memory (huge pages) for additional copies.
> The only reference to anything related to lib_pdump in testpmd is the
> call to rte_pdump_init(). But adding this call seems to have no
> effect.
>
> Just to make sure "it's not me" I added the call to the
> examples/skeleton app, and dpdk-dumpcap will not run w/ the modified
> sample app. So it seems like it's more than just calling
> rte_pdump_init(). Can anyone shed some light on what needs to happen
> to get an app working w/ dpdk-dumpcap?
>
> I'm using dpdk version v21.11, compile from source via github.
>
> Thanks,
> -Jon
Most failures are because of doing something that breaks primary/secondary
process support. Like using --in-memory or having a device that won't support
primary/secondary.
prev parent reply other threads:[~2022-01-19 16:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 18:42 Jon Ross
2022-01-19 16:37 ` 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=20220119083729.48d9732b@hermes.local \
--to=stephen@networkplumber.org \
--cc=jonross@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).