app/testpmd: add L4 port to verbose output

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>
---
 app/test-pmd/util.c | 71 +++++++++++++++++++++++++++------------------
 1 file changed, 42 insertions(+), 29 deletions(-)
  

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>

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.
  

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
  

On 16. 8. 2024 13:46, Luca Vizzarro wrote:
> 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?
> 

Hi Stephen,

Do you have any advice for us?

Thanks,
Juraj

> Thank you,
> Luca Vizzarro