From: "Etelson, Gregory" <getelson@nvidia.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Gregory Etelson <getelson@nvidia.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: Tue, 6 Jan 2026 18:52:02 +0200 (IST) [thread overview]
Message-ID: <7cb28bdc-d6d2-0045-5fe3-a0a8987772c9@nvidia.com> (raw)
In-Reply-To: <20260106083336.07408e78@phoenix.local>
Hello Stephen,
>
>> In some cases application does not need to receive entire packet
>> from port hardware.
>> If application could receive required Rx data only and safely discard
>> the rest of Rx packet data, that could improve port performance by
>> reducing PCI bandwidth and application memory consumption.
>>
[ snip ]
>
> Will need testpmd extension and a driver (ideally multiple) that support it.
>
Ethdev library, MLX5 PMD and testpmd patches with the selective Rx data read
implemetnation will be proveded after the RFC acceptence.
Additional PMD implementations depend on HW support to safely discard Rx data.
Regards,
Gregory
prev parent reply other threads:[~2026-01-06 16:52 UTC|newest]
Thread overview: 7+ 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 [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=7cb28bdc-d6d2-0045-5fe3-a0a8987772c9@nvidia.com \
--to=getelson@nvidia.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=mkashani@nvidia.com \
--cc=stephen@networkplumber.org \
--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 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).