All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wojciech Drewek <wojciech.drewek@intel.com>
To: Michael Chan <michael.chan@broadcom.com>, <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <edumazet@google.com>,
	<kuba@kernel.org>, <pabeni@redhat.com>, <gospo@broadcom.com>,
	Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: Re: [PATCH net-next] bnxt_en: Fix 2 stray ethtool -S counters
Date: Thu, 26 Oct 2023 12:36:37 +0200	[thread overview]
Message-ID: <1014e04b-5e74-4f7e-b2a5-ed0f8d01629d@intel.com> (raw)
In-Reply-To: <20231026013231.53271-1-michael.chan@broadcom.com>

On 26.10.2023 03:32, Michael Chan wrote:
> The recent firmware interface change has added 2 counters in struct
> rx_port_stats_ext. This caused 2 stray ethtool counters to be
> displayed.
> 
> Since new counters are added from time to time, fix it so that the
> ethtool logic will only display up to the maximum known counters.
> These 2 counters are not used by production firmware yet.
> 
> Fixes: 754fbf604ff6 ("bnxt_en: Update firmware interface to 1.10.2.171")

If this is a fix than the target should be "net" not "net-next".

> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> Signed-off-by: Michael Chan <michael.chan@broadcom.com>
> ---
>  .../net/ethernet/broadcom/bnxt/bnxt_ethtool.c | 28 +++++++++++++++----
>  1 file changed, 22 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/net/ethernet/broadcom/bnxt/bnxt_ethtool.c b/drivers/net/ethernet/broadcom/bnxt/bnxt_ethtool.c
> index 53442aaabe5e..f3f384773ac0 100644
> --- a/drivers/net/ethernet/broadcom/bnxt/bnxt_ethtool.c
> +++ b/drivers/net/ethernet/broadcom/bnxt/bnxt_ethtool.c
> @@ -535,6 +535,7 @@ static int bnxt_get_num_ring_stats(struct bnxt *bp)
>  static int bnxt_get_num_stats(struct bnxt *bp)
>  {
>  	int num_stats = bnxt_get_num_ring_stats(bp);
> +	int len;
>  
>  	num_stats += BNXT_NUM_RING_ERR_STATS;
>  
> @@ -542,8 +543,12 @@ static int bnxt_get_num_stats(struct bnxt *bp)
>  		num_stats += BNXT_NUM_PORT_STATS;
>  
>  	if (bp->flags & BNXT_FLAG_PORT_STATS_EXT) {
> -		num_stats += bp->fw_rx_stats_ext_size +
> -			     bp->fw_tx_stats_ext_size;
> +		len = min_t(int, bp->fw_rx_stats_ext_size,
> +			    ARRAY_SIZE(bnxt_port_stats_ext_arr));

You don't need "len" var.
Why not just:
	num_stats += min_t(int, bp->fw_rx_stats_ext_size,
			   ARRAY_SIZE(bnxt_port_stats_ext_arr));

> +		num_stats += len;
> +		len = min_t(int, bp->fw_tx_stats_ext_size,
> +			    ARRAY_SIZE(bnxt_tx_port_stats_ext_arr));
> +		num_stats += len;
>  		if (bp->pri2cos_valid)
>  			num_stats += BNXT_NUM_STATS_PRI;
>  	}
> @@ -653,12 +658,17 @@ static void bnxt_get_ethtool_stats(struct net_device *dev,
>  	if (bp->flags & BNXT_FLAG_PORT_STATS_EXT) {
>  		u64 *rx_port_stats_ext = bp->rx_port_stats_ext.sw_stats;
>  		u64 *tx_port_stats_ext = bp->tx_port_stats_ext.sw_stats;
> +		u32 len;
>  
> -		for (i = 0; i < bp->fw_rx_stats_ext_size; i++, j++) {
> +		len = min_t(u32, bp->fw_rx_stats_ext_size,
> +			    ARRAY_SIZE(bnxt_port_stats_ext_arr));
> +		for (i = 0; i < len; i++, j++) {
>  			buf[j] = *(rx_port_stats_ext +
>  				   bnxt_port_stats_ext_arr[i].offset);
>  		}
> -		for (i = 0; i < bp->fw_tx_stats_ext_size; i++, j++) {
> +		len = min_t(u32, bp->fw_tx_stats_ext_size,
> +			    ARRAY_SIZE(bnxt_tx_port_stats_ext_arr));
> +		for (i = 0; i < len; i++, j++) {
>  			buf[j] = *(tx_port_stats_ext +
>  				   bnxt_tx_port_stats_ext_arr[i].offset);
>  		}
> @@ -757,11 +767,17 @@ static void bnxt_get_strings(struct net_device *dev, u32 stringset, u8 *buf)
>  			}
>  		}
>  		if (bp->flags & BNXT_FLAG_PORT_STATS_EXT) {
> -			for (i = 0; i < bp->fw_rx_stats_ext_size; i++) {
> +			u32 len;
> +
> +			len = min_t(u32, bp->fw_rx_stats_ext_size,
> +				    ARRAY_SIZE(bnxt_port_stats_ext_arr));
> +			for (i = 0; i < len; i++) {
>  				strcpy(buf, bnxt_port_stats_ext_arr[i].string);
>  				buf += ETH_GSTRING_LEN;
>  			}
> -			for (i = 0; i < bp->fw_tx_stats_ext_size; i++) {
> +			len = min_t(u32, bp->fw_tx_stats_ext_size,
> +				    ARRAY_SIZE(bnxt_tx_port_stats_ext_arr));
> +			for (i = 0; i < len; i++) {
>  				strcpy(buf,
>  				       bnxt_tx_port_stats_ext_arr[i].string);
>  				buf += ETH_GSTRING_LEN;

  reply	other threads:[~2023-10-26 10:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26  1:32 [PATCH net-next] bnxt_en: Fix 2 stray ethtool -S counters Michael Chan
2023-10-26 10:36 ` Wojciech Drewek [this message]
2023-10-26 14:28   ` Jakub Kicinski
2023-10-26 14:35     ` Wojciech Drewek
2023-10-27  3:10 ` patchwork-bot+netdevbpf

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=1014e04b-5e74-4f7e-b2a5-ed0f8d01629d@intel.com \
    --to=wojciech.drewek@intel.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gospo@broadcom.com \
    --cc=kuba@kernel.org \
    --cc=michael.chan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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.