From: Stephen Hemminger <stephen@networkplumber.org>
To: Alex Chapman <alex.chapman@arm.com>
Cc: dev@dpdk.org, "Aman Singh" <aman.deep.singh@intel.com>,
"Jeremy Spewock" <jspewock@iol.unh.edu>,
"Honnappa Nagarahalli" <honnappa.nagarahalli@arm.com>,
"Juraj Linkeš" <juraj.linkes@pantheon.tech>,
"Luca Vizzarro" <luca.vizzarro@arm.com>,
"Paul Szczepanek" <paul.szczepanek@arm.com>
Subject: Re: [PATCH] app/testpmd: add L4 port to verbose output
Date: Sun, 24 Nov 2024 09:44:09 -0800 [thread overview]
Message-ID: <20241124094409.71c172a4@hermes.local> (raw)
In-Reply-To: <20240815142051.531978-1-alex.chapman@arm.com>
On Thu, 15 Aug 2024 15:20:51 +0100
Alex Chapman <alex.chapman@arm.com> wrote:
> To help distinguish packets we want to add more identifiable
> information and print port number for all packets.
> This will make packet metadata more uniform as previously it
> only printed port number for encapsulated packets.
>
> Bugzilla-ID: 1517
>
> Signed-off-by: Alex Chapman <alex.chapman@arm.com>
> Reviewed-by: Luca Vizzarro <luca.vizzarro@arm.com>
> Reviewed-by: Paul Szczepanek <paul.szczepanek@arm.com>
Having more diagnostic output here is a good idea, the output
is pretty verbose. So both printing here and having it in the
dissect output is helpful.
Applied to next-net
prev parent reply other threads:[~2024-11-24 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 14:20 [PATCH] app/testpmd: add L4 port to verbose output Alex Chapman
2024-08-15 15:22 ` Stephen Hemminger
2024-08-16 11:46 ` Luca Vizzarro
2024-09-09 8:32 ` Juraj Linkeš
2024-11-24 17:44 ` 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=20241124094409.71c172a4@hermes.local \
--to=stephen@networkplumber.org \
--cc=alex.chapman@arm.com \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=jspewock@iol.unh.edu \
--cc=juraj.linkes@pantheon.tech \
--cc=luca.vizzarro@arm.com \
--cc=paul.szczepanek@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.