From: Nikolay Aleksandrov <nikolay@cumulusnetworks•com>
To: Nikolay Aleksandrov <razor@blackwall•org>, netdev@vger•kernel.org
Cc: roopa@cumulusnetworks•com, stephen@networkplumber•org
Subject: Re: [PATCH iproute2 net-next] bridge: mdb: add user-space support for extended attributes
Date: Mon, 22 Feb 2016 15:09:06 +0100 [thread overview]
Message-ID: <56CB1682.2010006@cumulusnetworks.com> (raw)
In-Reply-To: <1456149621-27335-1-git-send-email-razor@blackwall.org>
On 02/22/2016 03:00 PM, Nikolay Aleksandrov wrote:
> From: Nikolay Aleksandrov <nikolay@cumulusnetworks•com>
>
> Recently support was added to the kernel to be able to add more per-mdb
> entry attributes via standard netlink attributes of type MDBA_MDB_EATTR_.
> This patch adds support to iproute2 to parse and output these
> attributes. The first exported attribute is the mdb "timer" value which
> is shown only when the "-d" iproute2 arg is used.
>
> Example:
> $ bridge -d mdb show
> dev br0 port eth1 grp 239.0.0.11 permanent 0.00
> dev br0 port eth2 grp 239.0.0.11 permanent 0.00
> dev br0 port eth1 grp 239.0.0.10 temp 244.38
> dev br0 port eth1 grp 239.0.0.1 temp 245.41
> dev br0 port eth1 grp 239.0.0.5 temp 246.43
> dev br0 port eth2 grp 239.0.0.5 temp 248.48
> dev br0 port eth1 grp 239.0.0.2 temp 245.41
>
> Signed-off-by: Nikolay Aleksandrov <nikolay@cumulusnetworks•com>
> ---
> note: this patch needs updated linux/if_bridge.h header to compile
>
Self-NAK. I'll use the "-s"/stats as that seems to be used for some time
values instead and will update the man page. v2 coming up.
Sorry about the noise,
Nik
next prev parent reply other threads:[~2016-02-22 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 14:00 [PATCH iproute2 net-next] bridge: mdb: add user-space support for extended attributes Nikolay Aleksandrov
2016-02-22 14:09 ` Nikolay Aleksandrov [this message]
2016-02-22 14:16 ` [PATCH iproute2 net-next v2] " Nikolay Aleksandrov
2016-03-02 17:23 ` [PATCH iproute2 net-next] " 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=56CB1682.2010006@cumulusnetworks.com \
--to=nikolay@cumulusnetworks$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=razor@blackwall$(echo .)org \
--cc=roopa@cumulusnetworks$(echo .)com \
--cc=stephen@networkplumber$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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