From: Alexander Duyck <alexander.duyck@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>,
Alexander Duyck <alexander.h.duyck@redhat.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [net-next PATCH] ip_tunnel: Report Rx dropped in ip_tunnel_get_stats64
Date: Thu, 14 May 2015 14:21:07 -0700 [thread overview]
Message-ID: <555511C3.5080107@gmail.com> (raw)
In-Reply-To: <1431637287.27831.65.camel@edumazet-glaptop2.roam.corp.google.com>
On 05/14/2015 02:01 PM, Eric Dumazet wrote:
> On Thu, 2015-05-14 at 13:56 -0700, Eric Dumazet wrote:
>
>> Or use netdev_stats_to_stats64() to remove all these copies, as we
>> obviously can miss some of them.
> Something like following untested patch :
>
> diff --git a/net/ipv4/ip_tunnel_core.c b/net/ipv4/ip_tunnel_core.c
> index 3998b1822d8521ad391ac26db1e694a3cd7ad011..3f298193d19ffc3a9e57fac4654c59bbe65545e1 100644
> --- a/net/ipv4/ip_tunnel_core.c
> +++ b/net/ipv4/ip_tunnel_core.c
> @@ -165,6 +165,7 @@ struct rtnl_link_stats64 *ip_tunnel_get_stats64(struct net_device *dev,
> {
> int i;
>
> + netdev_stats_to_stats64(tot, &dev->stats);
> for_each_possible_cpu(i) {
> const struct pcpu_sw_netstats *tstats =
> per_cpu_ptr(dev->tstats, i);
> @@ -184,23 +185,6 @@ struct rtnl_link_stats64 *ip_tunnel_get_stats64(struct net_device *dev,
> tot->rx_bytes += rx_bytes;
> tot->tx_bytes += tx_bytes;
> }
> -
> - tot->multicast = dev->stats.multicast;
> -
> - tot->rx_crc_errors = dev->stats.rx_crc_errors;
> - tot->rx_fifo_errors = dev->stats.rx_fifo_errors;
> - tot->rx_length_errors = dev->stats.rx_length_errors;
> - tot->rx_frame_errors = dev->stats.rx_frame_errors;
> - tot->rx_errors = dev->stats.rx_errors;
> -
> - tot->tx_fifo_errors = dev->stats.tx_fifo_errors;
> - tot->tx_carrier_errors = dev->stats.tx_carrier_errors;
> - tot->tx_dropped = dev->stats.tx_dropped;
> - tot->tx_aborted_errors = dev->stats.tx_aborted_errors;
> - tot->tx_errors = dev->stats.tx_errors;
> -
> - tot->collisions = dev->stats.collisions;
> -
> return tot;
> }
> EXPORT_SYMBOL_GPL(ip_tunnel_get_stats64);
>
Yeah, I just submitted v2 and realized I needed to have the call before
looping through the percpu stats. I will have v3 ready shortly based on
your suggestion.
- Alex
next prev parent reply other threads:[~2015-05-14 21:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 20:04 [net-next PATCH] ip_tunnel: Report Rx dropped in ip_tunnel_get_stats64 Alexander Duyck
2015-05-14 20:56 ` Eric Dumazet
2015-05-14 21:01 ` Eric Dumazet
2015-05-14 21:21 ` Alexander Duyck [this message]
2015-05-14 21:07 ` Alexander Duyck
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=555511C3.5080107@gmail.com \
--to=alexander.duyck@gmail.com \
--cc=alexander.h.duyck@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
/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.