From: Stephen Hemminger <stephen@networkplumber.org>
To: sfeldma@gmail.com
Cc: netdev@vger.kernel.org, jiri@resnulli.us, roopa@cumulusnetworks.com
Subject: Re: [PATCH iproute2 v2] bridge/link: add learning_sync policy flag
Date: Thu, 1 Jan 2015 10:03:54 -0800 [thread overview]
Message-ID: <20150101100354.28519a6f@urahara> (raw)
In-Reply-To: <1419884407-21998-1-git-send-email-sfeldma@gmail.com>
On Mon, 29 Dec 2014 12:20:07 -0800
sfeldma@gmail.com wrote:
> From: Scott Feldman <sfeldma@gmail.com>
>
> v2:
>
> Resending now that the dust has cleared in 3.18 on "self" vs. hwmode debate for
> brport settings. learning_sync is now set/cleared using "self" qualifier on
> brport.
>
> v1:
>
> Add 'learned_sync' flag to turn on/off syncing of learned MAC addresses from
> offload device to bridge's FDB. Flag is be set/cleared on offload device port
> using "self" qualifier:
>
> $ sudo bridge link set dev swp1 learning_sync on self
>
> $ bridge -d link show dev swp1
> 2: swp1 state UNKNOWN : <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master br0 state forwarding priority 32 cost 2
> hairpin off guard off root_block off fastleave off learning off flood off
> 2: swp1 state UNKNOWN : <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master br0
> learning on learning_sync on
>
> Adds new IFLA_BRPORT_LEARNED_SYNCED attribute for IFLA_PROTINFO on the SELF
> brport.
>
> Signed-off-by: Scott Feldman <sfeldma@gmail.com>
Applied
next prev parent reply other threads:[~2015-01-01 18:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 20:20 [PATCH iproute2 v2] bridge/link: add learning_sync policy flag sfeldma
2015-01-01 18:03 ` Stephen Hemminger [this message]
2015-01-02 17:14 ` Siva Mannem
2015-01-02 17:57 ` Scott Feldman
2015-01-03 1:23 ` Siva Mannem
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=20150101100354.28519a6f@urahara \
--to=stephen@networkplumber.org \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=sfeldma@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 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).