public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Gregory Etelson <getelson@nvidia.com>
Cc: <dev@dpdk.org>, <mkashani@nvidia.com>,
	"Claude Sonnet 4.5" <noreply@anthropic.com>,
	Aman Singh <aman.deep.singh@intel.com>
Subject: Re: [PATCH 2/2] app/testpmd: support selective Rx data
Date: Mon, 2 Feb 2026 09:37:07 -0800	[thread overview]
Message-ID: <20260202093707.2c699414@phoenix.local> (raw)
In-Reply-To: <20260202160903.254621-2-getelson@nvidia.com>

On Mon, 2 Feb 2026 18:09:03 +0200
Gregory Etelson <getelson@nvidia.com> wrote:

> diff --git a/doc/guides/testpmd_app_ug/run_app.rst b/doc/guides/testpmd_app_ug/run_app.rst
> index 97d6c75716..638c0b0eb3 100644
> --- a/doc/guides/testpmd_app_ug/run_app.rst
> +++ b/doc/guides/testpmd_app_ug/run_app.rst
> @@ -364,6 +364,11 @@ The command line options are:
>      feature is engaged. Affects only the queues configured
>      with split offloads (currently BUFFER_SPLIT is supported only).
>  
> +    When used with ``--rxpkts`` on PMDs supporting selective Rx data,
> +    enables receiving only specific packet segments and discarding the rest.
> +    Gaps between configured segments and any trailing data up to MTU are
> +    a

I don't see driver support for this. Seems like you are putting out
something that is not testable yet.

  reply	other threads:[~2026-02-02 17:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-02 16:09 [PATCH 1/2] ethdev: support selective Rx data Gregory Etelson
2026-02-02 16:09 ` [PATCH 2/2] app/testpmd: " Gregory Etelson
2026-02-02 17:37   ` Stephen Hemminger [this message]
2026-02-02 18:17 ` [PATCH 1/2] ethdev: " Stephen Hemminger

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=20260202093707.2c699414@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=aman.deep.singh@intel.com \
    --cc=dev@dpdk.org \
    --cc=getelson@nvidia.com \
    --cc=mkashani@nvidia.com \
    --cc=noreply@anthropic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox