From: Stephen Hemminger <stephen@networkplumber.org>
To: "Etelson, Gregory" <getelson@nvidia.com>
Cc: fengchengwen <fengchengwen@huawei.com>,
andrew.rybchenko@oktetlabs.ru, dev@dpdk.org, mkashani@nvidia.com,
thomas@monjalon.net, viacheslavo@nvidia.com, matan@nvidia.com
Subject: Re: [RFC PATCH v3] ethdev: support selective Rx data
Date: Mon, 19 Jan 2026 08:37:00 -0800 [thread overview]
Message-ID: <20260119083700.541fabfc@phoenix.local> (raw)
In-Reply-To: <03a55b2d-2957-c8ab-3c3e-dc9d207fc273@nvidia.com>
On Mon, 19 Jan 2026 13:23:02 +0200 (IST)
"Etelson, Gregory" <getelson@nvidia.com> wrote:
> Hello,
>
> >> In some cases application does not need to receive entire packet
> >> from port hardware.
> >
> > Which scenarios need to be used?
>
> A typical use case for the selective Rx data read can be the SAMPLE flow action.
> In that scenario, Rx queue that receives sampled packet copy can be configured
> to deliver to application partial packet data.
>
> > What is the behavior when
> > LRO(TCP packet aggregation is performed by hardware) is enabled?
> >
>
> The selective Rx data read is applied to MBUF layout that will be delivered to
> an application.
> That functionality comes after all HW Rx offloads.
What is the intended behavior in the selective case. Is there any mechanism for
application to see original length?
next prev parent reply other threads:[~2026-01-19 16:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-04 13:13 [RFC PATCH] ethdev: support Rx data discard Gregory Etelson
2026-01-04 18:04 ` Stephen Hemminger
2026-01-05 16:51 ` [RFC PATCH v2] ethdev: support selective Rx data Gregory Etelson
2026-01-06 15:04 ` Thomas Monjalon
2026-01-06 15:45 ` [RFC PATCH v3] " Gregory Etelson
2026-01-06 16:33 ` Stephen Hemminger
2026-01-06 16:52 ` Etelson, Gregory
2026-01-19 1:04 ` fengchengwen
2026-01-19 11:23 ` Etelson, Gregory
2026-01-19 16:37 ` Stephen Hemminger [this message]
2026-01-20 17:08 ` Etelson, Gregory
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=20260119083700.541fabfc@phoenix.local \
--to=stephen@networkplumber.org \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=getelson@nvidia.com \
--cc=matan@nvidia.com \
--cc=mkashani@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.