From: David Miller <davem@davemloft.net>
To: yidren@microsoft.com, yidren@linuxonhyperv.com
Cc: kys@microsoft.com, haiyangz@microsoft.com,
sthemmin@microsoft.com, devel@linuxdriverproject.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
madhans@microsoft.com
Subject: Re: [PATCH v4 net-next] hv_netvsc: Add per-cpu ethtool stats for netvsc
Date: Mon, 30 Jul 2018 12:34:53 -0700 (PDT) [thread overview]
Message-ID: <20180730.123453.209203416033226519.davem@davemloft.net> (raw)
In-Reply-To: <20180730170945.20517-1-yidren@linuxonhyperv.com>
From: Yidong Ren <yidren@linuxonhyperv.com>
Date: Mon, 30 Jul 2018 17:09:45 +0000
> From: Yidong Ren <yidren@microsoft.com>
>
> This patch implements following ethtool stats fields for netvsc:
> cpu<n>_tx/rx_packets/bytes
> cpu<n>_vf_tx/rx_packets/bytes
>
> Corresponding per-cpu counters already exist in current code. Exposing
> these counters will help troubleshooting performance issues.
>
> for_each_present_cpu() was used instead of for_each_possible_cpu().
> for_each_possible_cpu() would create very long and useless output.
> It is still being used for internal buffer, but not for ethtool
> output.
>
> There could be an overflow if cpu was added between ethtool
> call netvsc_get_sset_count() and netvsc_get_ethtool_stats() and
> netvsc_get_strings(). (still safe if cpu was removed)
> ethtool makes these three function calls separately.
> As long as we use ethtool, I can't see any clean solution.
>
> Currently and in foreseeable short term, Hyper-V doesn't support
> cpu hot-plug. Plus, ethtool is for admin use. Unlikely the admin
> would perform such combo operations.
>
> Signed-off-by: Yidong Ren <yidren@microsoft.com>
Applied, thank you.
prev parent reply other threads:[~2018-07-30 19:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 19:36 [PATCH v2] hv_netvsc: Add per-cpu ethtool stats for netvsc Yidong Ren
2018-06-13 20:57 ` Eric Dumazet
2018-06-13 21:07 ` Yidong Ren
2018-06-13 21:48 ` Stephen Hemminger
2018-06-13 22:03 ` Yidong Ren
2018-06-13 22:18 ` Stephen Hemminger
2018-07-24 1:26 ` [PATCH v3] " Yidong Ren
2018-07-24 1:42 ` Yidong Ren
2018-07-24 11:00 ` Vitaly Kuznetsov
2018-07-25 22:54 ` Yidong Ren
2018-07-30 17:09 ` [PATCH v4 net-next] " Yidong Ren
2018-07-30 17:34 ` Stephen Hemminger
2018-07-30 19:34 ` David Miller [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=20180730.123453.209203416033226519.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=madhans@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=sthemmin@microsoft.com \
--cc=yidren@linuxonhyperv.com \
--cc=yidren@microsoft.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;
as well as URLs for NNTP newsgroup(s).