From: Stephen Hemminger <stephen@networkplumber.org>
To: "Sylvia Grundwürmer" <sylvia.grundwuermer@b-plus.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: DPDK PDUMP pcapng usage
Date: Wed, 12 Oct 2022 08:16:36 -0700 [thread overview]
Message-ID: <20221012081636.4639ac16@hermes.local> (raw)
In-Reply-To: <1f5f87b63b94410fb651546d1b4a0937@b-plus.com>
On Tue, 11 Oct 2022 15:11:02 +0000
Sylvia Grundwürmer <sylvia.grundwuermer@b-plus.com> wrote:
> Hi,
>
> i am running DPDK 22.03 on a NXP platform, using 2 eth ports (dpmac, dpni, dprc config should be OK, as i get bursts of packets with testpmd and in a little customized app
> which is just checking if packets are bursted in mempool.
>
> So then i tried to use pdump and pcapng to write out a capture.pcapng file.
>
> I created mempool and ringbuffer according tot o the dumpcap-example, (rte_eth_dev_configure, rte_eth_dev_adjust_nb_rx_tx_desc, rte_eth_rx/tx_queue_setup, rte_eth_dev_start with the portid i have and which was veryfied by my little customized app as working properly)
> but when i call enable_pdump i am running into a segmentation fault.
>
> Validation of port, ring, mp, flags are ok.
> the problem seems to come from snprintf. There is no different behaviour no matter if i use enable_pdump or enable_pdump_by_deviceID or enable_pdump_bpf.
> PDUMP seems to have trouble whith my portID or deviceID.
>
> Can you give any hint, what might go wrong here? Or what i could try to get this stuff running?
> Thanks in advance.
>
> [cid:image003.png@01D8DD94.70449230]
Sample code would help, and the dpdk mailing list blocked your image attachment
next prev parent reply other threads:[~2022-10-12 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 15:11 Sylvia Grundwürmer
2022-10-12 15:16 ` Stephen Hemminger [this message]
2022-10-19 16:37 ` [PATCH] pdump: do not allow enable/disable in primary process Stephen Hemminger
2022-10-21 13:08 ` David Marchand
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=20221012081636.4639ac16@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=sylvia.grundwuermer@b-plus.com \
/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).