From: Stephen Hemminger <stephen@networkplumber.org>
To: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Cc: netdev@vger.kernel.org, roopa@cumulusnetworks.com
Subject: Re: [PATCH iproute2 net-next v3] bridge: vlan: add support to display per-vlan statistics
Date: Mon, 29 Aug 2016 10:59:58 -0700 [thread overview]
Message-ID: <20160829105958.66183ce3@xeon-e3> (raw)
In-Reply-To: <1472128135-17318-1-git-send-email-nikolay@cumulusnetworks.com>
On Thu, 25 Aug 2016 14:28:55 +0200
Nikolay Aleksandrov <nikolay@cumulusnetworks.com> wrote:
> This patch adds support for the stats argument to the bridge
> vlan command which will display the per-vlan statistics and the device
> each vlan belongs to with its flags. The supported command filtering
> options are dev and vid. Also the man page is updated to explain the new
> option.
> The patch uses the new RTM_GETSTATS interface with a filter_mask to dump
> all bridges and ports vlans. Later we can add support for using the
> per-device dump and filter it in the kernel instead.
>
> Example:
> $ bridge -s vlan show
> port vlan id
> br0 1 Egress Untagged
> RX: 2536 bytes 20 packets
> TX: 2536 bytes 20 packets
> 101
> RX: 43158 bytes 50 packets
> TX: 43158 bytes 50 packets
> eth1 1 Egress Untagged
> RX: 2536 bytes 20 packets
> TX: 2536 bytes 20 packets
> 100
> RX: 0 bytes 0 packets
> TX: 0 bytes 0 packets
> 101
> RX: 43158 bytes 50 packets
> TX: 43158 bytes 50 packets
> 102
> RX: 16897 bytes 93 packets
> TX: 0 bytes 0 packets
>
> The format is the same as bridge vlan show but with stats, even though
> under the hood the calls done to the kernel are different.
>
> Signed-off-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
> ---
Applied to net-next branch
prev parent reply other threads:[~2016-08-29 17:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 12:28 [PATCH iproute2 net-next v3] bridge: vlan: add support to display per-vlan statistics Nikolay Aleksandrov
2016-08-29 17:59 ` Stephen Hemminger [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=20160829105958.66183ce3@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.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).