From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Wilks <thomas.wilks@arm.com>
Cc: dev@dpdk.org, Paul Szczepanek <paul.szczepanek@arm.com>,
Luca Vizzarro <luca.vizzarro@arm.com>,
Patrick Robb <probb@iol.unh.edu>
Subject: Re: [PATCH 1/2] dts: add packet capture test suite
Date: Thu, 10 Apr 2025 15:46:48 -0700 [thread overview]
Message-ID: <20250410154648.74fa8f97@hermes.local> (raw)
In-Reply-To: <20250331155800.449823-2-thomas.wilks@arm.com>
On Mon, 31 Mar 2025 16:57:59 +0100
Thomas Wilks <thomas.wilks@arm.com> wrote:
> + def _start_pdump(
> + self,
> + pdump_params: list[PdumpParameters],
> + eal_params: EalParams | None = None,
> + ) -> BlockingDPDKApp:
> + if eal_params is None:
> + eal_params = EalParams()
> +
> + eal_params.append_str(" ".join([f'--pdump "{param}"' for param in pdump_params]))
> +
> + pdump = BlockingDPDKApp(PurePath("app/dpdk-pdump"), app_params=eal_params)
Please test dpdk-dumpcap not pdump. The old pdump is legacy, has too complex an options,
can't work in many cases and is a general mess. Dpdk-dumpcap was built as a replacement
and has way more features and will be supported.
I intend to deprecate pdump and remove it in 25.11.
next prev parent reply other threads:[~2025-04-10 22:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 15:57 [PATCH 0/2] dts: add packet capture test suite Thomas Wilks
2025-03-31 15:57 ` [PATCH 1/2] " Thomas Wilks
2025-04-10 17:04 ` Dean Marx
2025-04-10 22:46 ` Stephen Hemminger [this message]
2025-03-31 15:58 ` [PATCH 2/2] dts: import lldp package in scapy Thomas Wilks
2025-04-10 17:06 ` Dean Marx
2025-05-06 13:29 ` [PATCH v2 0/3] dts: add packet capture test suite Luca Vizzarro
2025-05-06 13:29 ` [PATCH v2 1/3] dts: import lldp package in scapy Luca Vizzarro
2025-05-06 13:29 ` [PATCH v2 2/3] dts: add facility to change file permissions Luca Vizzarro
2025-06-03 14:18 ` Dean Marx
2025-05-06 13:29 ` [PATCH v2 3/3] dts: add packet capture test suite Luca Vizzarro
2025-06-03 14:33 ` Dean Marx
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=20250410154648.74fa8f97@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=luca.vizzarro@arm.com \
--cc=paul.szczepanek@arm.com \
--cc=probb@iol.unh.edu \
--cc=thomas.wilks@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.