DPDK patches and discussions
 help / color / mirror / Atom feed
From: Dean Marx <dmarx@iol.unh.edu>
To: Patrick Robb <probb@iol.unh.edu>
Cc: Nicholas Pratte <npratte@iol.unh.edu>,
	Luca Vizzarro <Luca.Vizzarro@arm.com>,
	 Paul Szczepanek <Paul.Szczepanek@arm.com>, dev <dev@dpdk.org>
Subject: Re: Ethertype and Rx/Tx offload suites - collaborate with Luca
Date: Thu, 6 Mar 2025 17:06:25 -0500	[thread overview]
Message-ID: <CABD7UXOHriaajKFyuvYy5m6DunD=rEziKbW_124+nsojUTyYJA@mail.gmail.com> (raw)
In-Reply-To: <CAJvnSUCwRgakHWimtK2hjsmF__RKkgRSc5wK-ZyJ6kSp04ddcg@mail.gmail.com>

> rx/tx offload:
>
> 1.Dean has rebased this series but is running into a bug with the capability check test parser returning no flags. He confirmed from running the steps manually that the flags we expect are being reported by testpmd.
>
> 2. Dean please provide a summary to Luca so there is no double work.

Hi Luca,

Essentially what I ran into while trying to rebase the series was an
issue with the parser in the OffloadCapability class. The make_parser
function contains an argument called "find_multiple", which will match
all port/queue capabilities/configurations found in testpmd, rather
than just the first instance. This argument is set to True and runs
during test suite execution, but causes an error because one of the
variables sent to from_list() during the parser creation is not a list
of strings (like it's supposed to be) but instead the string "0". I
moved away from the series to work on some other items in the
meantime, but I was thinking it could be an issue with the regex that
is grabbing an extra string. In this instance, the command "show port
0 rx_offload configuration" is sent to testpmd, which prints something
like the following:

testpmd> show port 0 rx_offload configuration
Rx Offloading Configuration of port 0 :
  Port :
  Queue[ 0] :

If I had to guess, the "0" string is coming from the last line, but
again I never finished debugging so just an educated guess. If you run
into the same problem let me know.

Cheers

      reply	other threads:[~2025-03-06 22:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-06 18:52 Patrick Robb
2025-03-06 22:06 ` Dean Marx [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='CABD7UXOHriaajKFyuvYy5m6DunD=rEziKbW_124+nsojUTyYJA@mail.gmail.com' \
    --to=dmarx@iol.unh.edu \
    --cc=Luca.Vizzarro@arm.com \
    --cc=Paul.Szczepanek@arm.com \
    --cc=dev@dpdk.org \
    --cc=npratte@iol.unh.edu \
    --cc=probb@iol.unh.edu \
    /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).