DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Gregory Etelson <getelson@nvidia.com>
Cc: dev@dpdk.org,   <mkashani@nvidia.com>,
	viacheslavo@nvidia.com, "Thomas Monjalon" <thomas@monjalon.net>,
	"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>
Subject: Re: [RFC PATCH] ethdev: support Rx data discard
Date: Sun, 4 Jan 2026 10:04:28 -0800	[thread overview]
Message-ID: <20260104100428.671ac8c6@phoenix.local> (raw)
In-Reply-To: <20260104131301.196350-1-getelson@nvidia.com>

On Sun, 4 Jan 2026 15:13:01 +0200
Gregory Etelson <getelson@nvidia.com> wrote:

> In some cases application does not need to receive entire packet
> from port hardware.
> If application could fetch required data only and safely discard the
> rest of Rx packet data, that could improve port performance by
> reducing PCI bandwidth.
> 
> The RTE_ETH_DEV_DISCARD_RX_DATA device capability flag notifies that
> a port hardware supports Rx data discard.
> 
> Signed-off-by: Gregory Etelson <getelson@nvidia.com>
> ---
>  lib/ethdev/rte_ethdev.h | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/lib/ethdev/rte_ethdev.h b/lib/ethdev/rte_ethdev.h
> index a66c2abbdb..10938ddad3 100644
> --- a/lib/ethdev/rte_ethdev.h
> +++ b/lib/ethdev/rte_ethdev.h
> @@ -2170,6 +2170,8 @@ struct rte_eth_dev_owner {
>   * PMDs filling the queue xstats themselves should not set this flag
>   */
>  #define RTE_ETH_DEV_AUTOFILL_QUEUE_XSTATS RTE_BIT32(6)
> +/** Device supports Rx data discard */
> +#define RTE_ETH_DEV_DISCARD_RX_DATA RTE_BIT32(7)
>  /**@}*/
>  
>  /**

Just because HW can do a feature doesn't mean that DPDK has to support it.
There needs to be more justification.

Why not use a flow rule?


  reply	other threads:[~2026-01-04 18:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-04 13:13 Gregory Etelson
2026-01-04 18:04 ` Stephen Hemminger [this message]
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

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=20260104100428.671ac8c6@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=getelson@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 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).