DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH] app/testpmd: enable warnings for possibly invalid config
Date: Tue, 16 Sep 2025 08:47:54 +0100	[thread overview]
Message-ID: <aMkWKrJPlVFH45JE@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20250915105308.46c31d44@hermes.local>

On Mon, Sep 15, 2025 at 10:53:08AM -0700, Stephen Hemminger wrote:
> On Fri, 12 Sep 2025 17:02:10 +0100
> Bruce Richardson <bruce.richardson@intel.com> wrote:
> 
> > When dealing with multi-segment packets, there are separate offload
> > flags which should be enabled on Rx (scattered flag) and on Tx
> > (multi-segment flag). Print warnings on testpmd startup if we detect a
> > situation where we suspect the user is missing these flags, e.g. we
> > allow scattered packets on Rx, but not on Tx.
> > 
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> > ---
> 
> Should also check for RTE_ETH_RX_OFFLOAD_BUFFER_SPLIT which should require
> multiple segment support.
> 
> Could testpmd also check the descriptor limits of the device?
> Does it validate nb_seg_max for TSO, and nb_mtu_seg_max for all cases?
> 

There are indeed lots of other checks that testpmd could do, but I'm not
going to try and implement them all in this one patch. The main reason for
doing these particular checks is that it's comparatively easy to enable
scattered support on Rx - since there is an explicit flag for it, and some
drivers enable the support automatically if they detect an MTU > mbuf size
- but it's awkward to enable on Tx, since you have to manually specify the
Tx offloads flags.

/Bruce

      reply	other threads:[~2025-09-16  7:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-12 16:02 Bruce Richardson
2025-09-15 17:53 ` Stephen Hemminger
2025-09-16  7:47   ` Bruce Richardson [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=aMkWKrJPlVFH45JE@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --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).