DPDK patches and discussions
 help / color / mirror / Atom feed
From: Luca Vizzarro <Luca.Vizzarro@arm.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
	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>,
	"Paul Szczepanek" <paul.szczepanek@arm.com>
Subject: Re: [PATCH] app/testpmd: add L4 port to verbose output
Date: Fri, 16 Aug 2024 12:46:18 +0100	[thread overview]
Message-ID: <64c84d76-f40e-4a1e-aee0-f06d29004d4d@arm.com> (raw)
In-Reply-To: <20240815082209.5c2813bf@hermes.local>

On 15/08/2024 16:22, Stephen Hemminger wrote:
> The verbose output is already too verbose.
> Maybe you would like the simpler format (which does include the port number)
> see the network packet dissector patches.

Hi Stephen,

Thank you for the reply you left to Alex's patch. This is actually quite 
helpful.

I've had a look at your patch series and the hexdump is actually quite 
great for our purpose at DTS, as it will allow us to detect a preset 
packet identifier in the payload.

Unfortunately, your patch doesn't solve the problem that Alex is having. 
He's currently writing up a test suite to test the RSS hash keys and the 
respective queues to which the incoming packets are placed into. To 
correctly match the packets to the queue and hash key, he needs a way to 
identify them. We explored some solutions and the L4 port seemed to be 
the most problem-free with the least effort. Using the payload is 
probably best and you've already posted the required changes too. The 
only problem is that your hexdump output does not print the required RSS 
values.

Would you be be keen to add these to your patch? Otherwise, do you have 
any ideas and/or solutions to tackle this specific problem?

Thank you,
Luca Vizzarro

  reply	other threads:[~2024-08-16 11:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-15 14:20 Alex Chapman
2024-08-15 15:22 ` Stephen Hemminger
2024-08-16 11:46   ` Luca Vizzarro [this message]
2024-09-09  8:32     ` Juraj Linkeš

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=64c84d76-f40e-4a1e-aee0-f06d29004d4d@arm.com \
    --to=luca.vizzarro@arm.com \
    --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=paul.szczepanek@arm.com \
    --cc=stephen@networkplumber.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).