From: Stephen Hemminger <stephen@networkplumber.org>
To: Vivien Didelot <vivien.didelot@gmail.com>
Cc: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>,
netdev@vger.kernel.org, Roopa Prabhu <roopa@cumulusnetworks.com>,
bridge@lists.linux-foundation.org,
David Ahern <dsahern@gmail.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [Bridge] [PATCH iproute2 v4] iplink: add support for STP xstats
Date: Mon, 16 Dec 2019 20:45:41 -0800 [thread overview]
Message-ID: <20191216204541.0540deb2@hermes.lan> (raw)
In-Reply-To: <20191212010711.1664000-2-vivien.didelot@gmail.com>
On Wed, 11 Dec 2019 20:07:11 -0500
Vivien Didelot <vivien.didelot@gmail.com> wrote:
> Add support for the BRIDGE_XSTATS_STP xstats, as follow:
>
> # ip link xstats type bridge_slave dev lan4 stp
> lan4
> STP BPDU: RX: 0 TX: 61
> STP TCN: RX: 0 TX: 0
> STP Transitions: Blocked: 2 Forwarding: 1
>
> Or below as JSON:
>
> # ip -j -p link xstats type bridge_slave dev lan0 stp
> [ {
> "ifname": "lan0",
> "stp": {
> "rx_bpdu": 0,
> "tx_bpdu": 500,
> "rx_tcn": 0,
> "tx_tcn": 0,
> "transition_blk": 0,
> "transition_fwd": 0
> }
> } ]
>
> Signed-off-by: Vivien Didelot <vivien.didelot@gmail.com>
This patch depends on new kernel features, should be to iproute2-next
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Hemminger <stephen@networkplumber.org>
To: Vivien Didelot <vivien.didelot@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Roopa Prabhu <roopa@cumulusnetworks.com>,
Nikolay Aleksandrov <nikolay@cumulusnetworks.com>,
netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH iproute2 v4] iplink: add support for STP xstats
Date: Mon, 16 Dec 2019 20:45:41 -0800 [thread overview]
Message-ID: <20191216204541.0540deb2@hermes.lan> (raw)
In-Reply-To: <20191212010711.1664000-2-vivien.didelot@gmail.com>
On Wed, 11 Dec 2019 20:07:11 -0500
Vivien Didelot <vivien.didelot@gmail.com> wrote:
> Add support for the BRIDGE_XSTATS_STP xstats, as follow:
>
> # ip link xstats type bridge_slave dev lan4 stp
> lan4
> STP BPDU: RX: 0 TX: 61
> STP TCN: RX: 0 TX: 0
> STP Transitions: Blocked: 2 Forwarding: 1
>
> Or below as JSON:
>
> # ip -j -p link xstats type bridge_slave dev lan0 stp
> [ {
> "ifname": "lan0",
> "stp": {
> "rx_bpdu": 0,
> "tx_bpdu": 500,
> "rx_tcn": 0,
> "tx_tcn": 0,
> "transition_blk": 0,
> "transition_fwd": 0
> }
> } ]
>
> Signed-off-by: Vivien Didelot <vivien.didelot@gmail.com>
This patch depends on new kernel features, should be to iproute2-next
next prev parent reply other threads:[~2019-12-17 4:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 1:07 [Bridge] [PATCH net-next v3] net: bridge: add STP xstats Vivien Didelot
2019-12-12 1:07 ` Vivien Didelot
2019-12-12 1:07 ` [Bridge] [PATCH iproute2 v4] iplink: add support for " Vivien Didelot
2019-12-12 1:07 ` Vivien Didelot
2019-12-17 4:45 ` Stephen Hemminger [this message]
2019-12-17 4:45 ` Stephen Hemminger
2019-12-17 16:35 ` [Bridge] " David Ahern
2019-12-17 16:35 ` David Ahern
2019-12-12 6:55 ` [Bridge] [PATCH net-next v3] net: bridge: add " Nikolay Aleksandrov
2019-12-12 6:55 ` Nikolay Aleksandrov
2019-12-15 4:03 ` [Bridge] " Jakub Kicinski
2019-12-15 4:03 ` Jakub Kicinski
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=20191216204541.0540deb2@hermes.lan \
--to=stephen@networkplumber.org \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.com \
--cc=vivien.didelot@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.