From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: wei.fang@nxp.com
Cc: claudiu.manoil@nxp.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.or, pabeni@redhat.com, ast@kernel.org,
daniel@iogearbox.net, hawk@kernel.org, john.fastabend@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 1/2] net: enetc: correct the statistics of rx bytes
Date: Fri, 2 Jun 2023 13:27:10 +0300 [thread overview]
Message-ID: <20230602102710.vnfh774wkpt7rclg@skbuf> (raw)
In-Reply-To: <20230602094659.965523-2-wei.fang@nxp.com>
Hi Wei,
On Fri, Jun 02, 2023 at 05:46:58PM +0800, wei.fang@nxp.com wrote:
> From: Wei Fang <wei.fang@nxp.com>
>
> The rx_bytes of struct net_device_stats should count the length of
> ethernet frames excluding the FCS. However, there are two problems
> with the rx_bytes statistics of the current enetc driver. one is
> that the length of VLAN header is not counted if the VLAN extraction
> feature is enabled. The other is that the length of L2 header is not
> counted, because eth_type_trans() is invoked before updating rx_bytes
> which will subtract the length of L2 header from skb->len.
Thanks for noticing the issue and for sending a patch.
> BTW, the rx_bytes statistics of XDP path also have similar problem,
> I will fix it in another patch.
>
> Fixes: a800abd3ecb9 ("net: enetc: move skb creation into enetc_build_skb")
> Signed-off-by: Wei Fang <wei.fang@nxp.com>
> ---
> drivers/net/ethernet/freescale/enetc/enetc.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/freescale/enetc/enetc.c b/drivers/net/ethernet/freescale/enetc/enetc.c
> index 3c4fa26f0f9b..d6c0f3f46c2a 100644
> --- a/drivers/net/ethernet/freescale/enetc/enetc.c
> +++ b/drivers/net/ethernet/freescale/enetc/enetc.c
> @@ -1229,7 +1229,13 @@ static int enetc_clean_rx_ring(struct enetc_bdr *rx_ring,
> if (!skb)
> break;
>
> - rx_byte_cnt += skb->len;
> + /* When set, the outer VLAN header is extracted and reported
> + * in the receive buffer descriptor. So rx_byte_cnt should
> + * add the length of the extracted VLAN header.
> + */
> + if (bd_status & ENETC_RXBD_FLAG_VLAN)
> + rx_byte_cnt += VLAN_HLEN;
> + rx_byte_cnt += skb->len + ETH_HLEN;
Hmm, to avoid the conditional, have you considered adding an "int *rx_byte_cnt"
argument to enetc_build_skb()? It can be updated with "(*rx_byte_cnt) += size"
from all places where we already have "(*cleaned_cnt)++".
> rx_frm_cnt++;
>
> napi_gro_receive(napi, skb);
> --
> 2.25.1
>
next prev parent reply other threads:[~2023-06-02 10:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 9:46 [PATCH net 0/2] net: enetc: correct the statistics of rx bytes wei.fang
2023-06-02 9:46 ` [PATCH net 1/2] " wei.fang
2023-06-02 10:27 ` Vladimir Oltean [this message]
2023-06-02 10:30 ` Vladimir Oltean
2023-06-02 10:31 ` Vladimir Oltean
2023-06-02 10:35 ` Wei Fang
2023-06-02 9:46 ` [PATCH net 2/2] net: enetc: correct rx_bytes statistics of XDP wei.fang
2023-06-02 10:32 ` Vladimir Oltean
2023-06-04 16:58 ` [PATCH net 0/2] net: enetc: correct the statistics of rx bytes 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=20230602102710.vnfh774wkpt7rclg@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=ast@kernel.org \
--cc=claudiu.manoil@nxp.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.or \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wei.fang@nxp.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