From: Florian Fainelli <f.fainelli@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>,
Petri Gynther <pgynther@google.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
jaedon.shin@gmail.com, edumazet@google.com
Subject: Re: [PATCH net 1/2] net: bcmgenet: fix dev->stats.tx_bytes accounting
Date: Wed, 23 Mar 2016 14:47:45 -0700 [thread overview]
Message-ID: <C2A46484-4AE6-418C-A4F4-760C3A4DC368@gmail.com> (raw)
In-Reply-To: <1458768237.10868.46.camel@edumazet-glaptop3.roam.corp.google.com>
On March 23, 2016 2:23:57 PM PDT, Eric Dumazet <eric.dumazet@gmail.com> wrote:
>On Wed, 2016-03-23 at 13:01 -0700, Petri Gynther wrote:
>> 1. Add bytes_compl local variable to collect transmitted bytes
>> - dev->stats updates can then be moved outside the while-loop
>> - bytes_compl is also needed for future BQL support
>> 2. When bcmgenet device uses Tx checksum offload, each transmitted
>> skb has an extra 64-byte header prepended to it. This needs to
>> be deducted when counting transmitted bytes.
>> 3. skb->len covers the entire length of skb, whether it is linear or
>> fragmented. Thus, when we clean the fragments, do not increase
>> transmitted bytes.
>>
>> Signed-off-by: Petri Gynther <pgynther@google.com>
>> ---
>> drivers/net/ethernet/broadcom/genet/bcmgenet.c | 10 ++++++----
>> 1 file changed, 6 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/net/ethernet/broadcom/genet/bcmgenet.c
>b/drivers/net/ethernet/broadcom/genet/bcmgenet.c
>> index 6746fd0..9990582 100644
>> --- a/drivers/net/ethernet/broadcom/genet/bcmgenet.c
>> +++ b/drivers/net/ethernet/broadcom/genet/bcmgenet.c
>> @@ -1171,6 +1171,7 @@ static unsigned int
>__bcmgenet_tx_reclaim(struct net_device *dev,
>> struct enet_cb *tx_cb_ptr;
>> struct netdev_queue *txq;
>> unsigned int pkts_compl = 0;
>> + unsigned int bytes_compl = 0;
>> unsigned int c_index;
>> unsigned int txbds_ready;
>> unsigned int txbds_processed = 0;
>> @@ -1193,16 +1194,14 @@ static unsigned int
>__bcmgenet_tx_reclaim(struct net_device *dev,
>> tx_cb_ptr = &priv->tx_cbs[ring->clean_ptr];
>> if (tx_cb_ptr->skb) {
>> pkts_compl++;
>> - dev->stats.tx_packets++;
>> - dev->stats.tx_bytes += tx_cb_ptr->skb->len;
>> + bytes_compl += tx_cb_ptr->skb->len -
>> + (priv->desc_64b_en ? 64 : 0);
>
>Please do not use this 64 scalar, prefer sizeof(struct status_64)
>
>I know this driver uses skb_pull(skb, 64); len -= 64; in
>bcmgenet_desc_rx(), but I would prefer not adding magic values.
Agreed, and just so we are more robust and ready to add BQL in the features please store this information in skb->cb, in the same spirit as what this does:
https://github.com/ffainelli/linux/commits/genet-bql
Thanks.
--
Florian
next prev parent reply other threads:[~2016-03-23 21:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 20:01 [PATCH net 1/2] net: bcmgenet: fix dev->stats.tx_bytes accounting Petri Gynther
2016-03-23 20:01 ` [PATCH net 2/2] net: bcmgenet: fix skb_len in bcmgenet_xmit_single() Petri Gynther
2016-03-23 21:24 ` Eric Dumazet
2016-03-23 21:23 ` [PATCH net 1/2] net: bcmgenet: fix dev->stats.tx_bytes accounting Eric Dumazet
2016-03-23 21:47 ` Florian Fainelli [this message]
2016-03-23 22:02 ` Florian Fainelli
2016-03-23 22:09 ` Florian Fainelli
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=C2A46484-4AE6-418C-A4F4-760C3A4DC368@gmail.com \
--to=f.fainelli@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=jaedon.shin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pgynther@google.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