DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Sylvia Grundwürmer" <sylvia.grundwuermer@b-plus.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: DPDK PDUMP pcapng usage
Date: Tue, 11 Oct 2022 15:11:02 +0000	[thread overview]
Message-ID: <1f5f87b63b94410fb651546d1b4a0937@b-plus.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2514 bytes --]

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]


Mit freundlichen Grüßen / Best regards

i.A. Sylvia Grundwürmer
Software-Entwicklerin / Software Developer

b-plus GmbH
Ulrichsberger Straße 17 | 94469 Deggendorf
sylvia.grundwuermer@b-plus.com

Besucheradresse / Visitor address:
b-plus GmbH
Ulrichsberger Str. 17, 94469 Deggendorf, Germany
Website<http://www.b-plus.com/> | XING<https://www.xing.com/companies/b-plusgmbh> | FACEBOOK<https://www.facebook.com/bplusGmbH/> | LinkedIn<https://www.linkedin.com/company/b-plus-gmbh/>


[cid:image004.jpg@01D8DD94.70449230]<https://karriere.b-plus.com/jobs>
b-plus GmbH
Geschäftsführer / Managing Director: Dipl.-Ing.(FH) Michael Sieg
Gerichtsstand /Handelsregister / Place of jurisdiction / Commercial register: HRB 1753 Deggendorf / Germany
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und löschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the contents in this e-mail is strictly forbidden.



















[-- Attachment #1.2: Type: text/html, Size: 10937 bytes --]

[-- Attachment #2: image003.png --]
[-- Type: image/png, Size: 313423 bytes --]

[-- Attachment #3: image004.jpg --]
[-- Type: image/jpeg, Size: 12799 bytes --]

             reply	other threads:[~2022-10-12  8:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11 15:11 Sylvia Grundwürmer [this message]
2022-10-12 15:16 ` Stephen Hemminger
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=1f5f87b63b94410fb651546d1b4a0937@b-plus.com \
    --to=sylvia.grundwuermer@b-plus.com \
    --cc=dev@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).