From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
To: netdev@vger.kernel.org
Cc: roopa@cumulusnetworks.com, stephen@networkplumber.org,
Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Subject: [PATCH iproute2 net-next 0/3] iplink: add support for link xstats
Date: Wed, 15 Feb 2017 15:23:10 +0100 [thread overview]
Message-ID: <1487168593-31321-1-git-send-email-nikolay@cumulusnetworks.com> (raw)
Hi,
This set adds support for printing link xstats per link type. Currently
only the bridge and its ports support such call and it dumps the mcast
stats. This model makes it easy to use the same callback for both bridge
and bridge_slave link types. Patch 01 also updates the man page with the
new xstats link option and you can find an example in patch 02's commit
message.
Thanks,
Nik
Nikolay Aleksandrov (3):
iplink: add support for xstats subcommand
iplink: bridge: add support for displaying xstats
iplink: bridge_slave: add support for displaying xstats
ip/Makefile | 2 +-
ip/ip_common.h | 12 +++-
ip/iplink.c | 5 ++
ip/iplink_bridge.c | 153 +++++++++++++++++++++++++++++++++++++++++++++++
ip/iplink_bridge_slave.c | 2 +
ip/iplink_xstats.c | 81 +++++++++++++++++++++++++
man/man8/ip-link.8.in | 12 ++++
7 files changed, 264 insertions(+), 3 deletions(-)
create mode 100644 ip/iplink_xstats.c
--
2.1.4
next reply other threads:[~2017-02-15 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 14:23 Nikolay Aleksandrov [this message]
2017-02-15 14:23 ` [PATCH iproute2 net-next 1/3] iplink: add support for xstats subcommand Nikolay Aleksandrov
2017-02-15 14:23 ` [PATCH iproute2 net-next 2/3] iplink: bridge: add support for displaying xstats Nikolay Aleksandrov
2017-02-15 14:23 ` [PATCH iproute2 net-next 3/3] iplink: bridge_slave: " Nikolay Aleksandrov
2017-02-19 0:38 ` [PATCH iproute2 net-next 0/3] iplink: add support for link xstats Stephen Hemminger
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=1487168593-31321-1-git-send-email-nikolay@cumulusnetworks.com \
--to=nikolay@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).