From: Bowers, AndrewX <andrewx.bowers@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next v2] i40e: implement VF stats NDO
Date: Fri, 1 Nov 2019 16:50:56 +0000 [thread overview]
Message-ID: <a99f8f7254764ad9836aa8df76930669@intel.com> (raw)
In-Reply-To: <20191029003707.45245-1-jesse.brandeburg@intel.com>
> -----Original Message-----
> From: Intel-wired-lan [mailto:intel-wired-lan-bounces at osuosl.org] On
> Behalf Of Jesse Brandeburg
> Sent: Monday, October 28, 2019 5:37 PM
> To: intel-wired-lan at lists.osuosl.org
> Subject: [Intel-wired-lan] [PATCH net-next v2] i40e: implement VF stats NDO
>
> Implement the VF stats gathering via the kernel via ndo_get_vf_stats().
> The driver will show per-VF stats in the output of the command:
> ip -s link show dev <PF>
>
> Testing Hints:
> ip -s link show dev eth0
> will return non-zero VF stats.
> ...
> vf 0 MAC 00:55:aa:00:55:aa, spoof checking on, link-state enable, trust off
> RX: bytes packets mcast bcast
> 128000 1000 104 104
> TX: bytes packets
> 128000 1000
>
> Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
>
> ---
>
> v2: remove transmit stats from multicast and broadcast based on feedback,
> add a little to commit message.
> ---
> drivers/net/ethernet/intel/i40e/i40e_main.c | 1 +
> .../ethernet/intel/i40e/i40e_virtchnl_pf.c | 48 +++++++++++++++++++
> .../ethernet/intel/i40e/i40e_virtchnl_pf.h | 2 +
> 3 files changed, 51 insertions(+)
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
prev parent reply other threads:[~2019-11-01 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 0:37 [Intel-wired-lan] [PATCH net-next v2] i40e: implement VF stats NDO Jesse Brandeburg
2019-11-01 16:50 ` Bowers, AndrewX [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=a99f8f7254764ad9836aa8df76930669@intel.com \
--to=andrewx.bowers@intel.com \
--cc=intel-wired-lan@osuosl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox