DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Sunyang Wu <sunyang.wu@jaguarmicro.com>
Cc: dev@dpdk.org, thomas@monjalon.net, ferruh.yigit@amd.com,
	andrew.rybchenko@oktetlabs.ru,
	"Morten Brørup" <mb@smartsharesystems.com>
Subject: Re: [PATCH v2] ethdev: optimize how the values of the flag variables are assigned
Date: Wed, 21 May 2025 06:57:37 -0700	[thread overview]
Message-ID: <20250521065737.45cef281@hermes.local> (raw)
In-Reply-To: <20250521101531.34240-1-sunyang.wu@jaguarmicro.com>

On Wed, 21 May 2025 18:15:31 +0800
Sunyang Wu <sunyang.wu@jaguarmicro.com> wrote:

> Set the values of the promiscuous and all_multicast variables
> according to the return value.
> 
> Signed-off-by: Morten Brørup <mb@smartsharesystems.com>
> Signed-off-by: Sunyang Wu <sunyang.wu@jaguarmicro.com>
> ---
>  lib/ethdev/rte_ethdev.c | 11 +++++------
>  1 file changed, 5 insertions(+), 6 deletions(-)
> 
> diff --git a/lib/ethdev/rte_ethdev.c b/lib/ethdev/rte_ethdev.c
> index d4197322a0..c27d3e5041 100644
> --- a/lib/ethdev/rte_ethdev.c
> +++ b/lib/ethdev/rte_ethdev.c
> @@ -3044,10 +3044,9 @@ rte_eth_promiscuous_disable(uint16_t port_id)
>  	if (dev->dev_ops->promiscuous_disable == NULL)
>  		return -ENOTSUP;
>  
> -	dev->data->promiscuous = 0;
>  	diag = dev->dev_ops->promiscuous_disable(dev);
> -	if (diag != 0)
> -		dev->data->promiscuous = 1;
> +	if (!diag)
> +		dev->data->promiscuous = 0;
>  
>  	diag = eth_err(port_id, diag);
>  
> @@ -3112,10 +3111,10 @@ rte_eth_allmulticast_disable(uint16_t port_id)
>  
>  	if (dev->dev_ops->allmulticast_disable == NULL)
>  		return -ENOTSUP;
> -	dev->data->all_multicast = 0;
> +
>  	diag = dev->dev_ops->allmulticast_disable(dev);
> -	if (diag != 0)
> -		dev->data->all_multicast = 1;
> +	if (!diag)
> +		dev->data->all_multicast = 0;
>  
>  	diag = eth_err(port_id, diag);
>  

Code is fine, but the commit description is misleading.
It is not an optimization, it is a bug fix so that flags
are not set if device callback returns an error.

An optimization is something that is faster but has the
same effect.

      reply	other threads:[~2025-05-21 13:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-21 10:15 Sunyang Wu
2025-05-21 13:57 ` Stephen Hemminger [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=20250521065737.45cef281@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=mb@smartsharesystems.com \
    --cc=sunyang.wu@jaguarmicro.com \
    --cc=thomas@monjalon.net \
    /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).