netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, roopa@cumulusnetworks.com
Subject: Re: [PATCH iproute2 net-next] bridge: vlan: add support to display per-vlan statistics
Date: Fri, 1 Jul 2016 11:24:16 +0200	[thread overview]
Message-ID: <577636C0.7080403@cumulusnetworks.com> (raw)
In-Reply-To: <20160630170659.07f46c3c@xeon-e3>

On 01/07/16 02:06, Stephen Hemminger wrote:
> On Tue, 21 Jun 2016 18:11:59 +0200
> Nikolay Aleksandrov <nikolay@cumulusnetworks.com> wrote:
> 
>>>> Thanks, this is a useful tool, but I think the formatting of output may need to be
>>>> reworked.  The bridge tool works similar to ip command. And in the ip command the
>>>> -s flag causes additional lines, but does not change the output format.  
>>>
>>> Indeed, I agree that it needs refinement.
>>>   
>>
>> Or alternatively I can make it:
>> $ bridge vlan stats
>> a subcommand instead of using the "-s" argument in order to be consistent.
>> So it can have its own format.
> 
> Why not:
> 
> $ bridge -s vlan show
> 
> to be consistent with:
> 
> $ ip -s li show
> 

The problem is that currently it cannot be formated the same as "bridge vlan show"
because it cannot contain the flags since all vlan stats are fetched from the
bridge device even though some vlans might exist only on the ports (or have different
flags on the ports).
That might change soon though, if my IGMP stats patches are accepted we'll be able
to fetch the vlan stats per port as well and thus print the flags and make the
output consistent with "bridge vlan show". Thus my first version of this patch that
just printed the stats will work in that case, we'll just add the flags and port
output later. If you'd like to go down this road please let me know.

Me and Roopa have been discussing an alternative way to fetch the stats via a new
command, something like:
$ bridge stats { <igmp> | <vlan> } [ dev DEV ] [ vid VID ]
because of the IGMP/MLD stats which don't fit any of the other commands for a "-s"
flag.

What do you think ?

Cheers,
 Nik

  reply	other threads:[~2016-07-01  9:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-20 10:13 [PATCH iproute2 net-next] bridge: vlan: add support to display per-vlan statistics Nikolay Aleksandrov
2016-06-21 16:01 ` Stephen Hemminger
2016-06-21 16:10   ` Nikolay Aleksandrov
2016-06-21 16:11     ` Nikolay Aleksandrov
2016-07-01  0:06       ` Stephen Hemminger
2016-07-01  9:24         ` Nikolay Aleksandrov [this message]
2016-06-21 18:07 ` [PATCH iproute2 net-next v2] " Nikolay Aleksandrov
2016-06-21 18:08   ` Nikolay Aleksandrov

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=577636C0.7080403@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).