From: roopa <roopa@cumulusnetworks.com>
To: "Linus Lüssing" <linus.luessing@c0d3.blue>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
linux-kernel@vger.kernel.org,
Wilson Kok <wkok@cumulusnetworks.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [Bridge] [PATCH net-next] bridge: allow setting hash_max + multicast_router if interface is down
Date: Thu, 21 May 2015 18:56:41 -0700 [thread overview]
Message-ID: <555E8CD9.9030004@cumulusnetworks.com> (raw)
In-Reply-To: <1432256161-4425-1-git-send-email-linus.luessing@c0d3.blue>
On 5/21/15, 5:56 PM, Linus Lüssing wrote:
> Network managers like netifd (used in OpenWRT for instance) try to
> configure interface options after creation but before setting the
> interface up.
>
> Unfortunately the sysfs / bridge currently only allows to configure the
> hash_max and multicast_router options when the bridge interface is up.
> But since br_multicast_init() doesn't start any timers and only sets
> default values and initializes timers it should be save to reconfigure
> the default values after that, before things actually get active after
> the bridge is set up.
>
> With this patch hash_max and multicast_router attributes can be
> changed even if the according bridge (port) is down, just like other
> other bridge (port) attributes allow too.
>
> Signed-off-by: Linus Lüssing <linus.luessing@c0d3.blue>
> ---
> Changelog:
> * [RFC PATCH net-next] -> [PATCH net-next]
Acked-by: Roopa Prabhu <roopa@cumulusnetworks.com>
we have a similar patch in-house waiting to be up-streamed.
thanks.
WARNING: multiple messages have this Message-ID (diff)
From: roopa <roopa@cumulusnetworks.com>
To: "Linus Lüssing" <linus.luessing@c0d3.blue>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
linux-kernel@vger.kernel.org,
Stephen Hemminger <stephen@networkplumber.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Satish Ashok <sashok@cumulusnetworks.com>,
Wilson Kok <wkok@cumulusnetworks.com>
Subject: Re: [PATCH net-next] bridge: allow setting hash_max + multicast_router if interface is down
Date: Thu, 21 May 2015 18:56:41 -0700 [thread overview]
Message-ID: <555E8CD9.9030004@cumulusnetworks.com> (raw)
In-Reply-To: <1432256161-4425-1-git-send-email-linus.luessing@c0d3.blue>
On 5/21/15, 5:56 PM, Linus Lüssing wrote:
> Network managers like netifd (used in OpenWRT for instance) try to
> configure interface options after creation but before setting the
> interface up.
>
> Unfortunately the sysfs / bridge currently only allows to configure the
> hash_max and multicast_router options when the bridge interface is up.
> But since br_multicast_init() doesn't start any timers and only sets
> default values and initializes timers it should be save to reconfigure
> the default values after that, before things actually get active after
> the bridge is set up.
>
> With this patch hash_max and multicast_router attributes can be
> changed even if the according bridge (port) is down, just like other
> other bridge (port) attributes allow too.
>
> Signed-off-by: Linus Lüssing <linus.luessing@c0d3.blue>
> ---
> Changelog:
> * [RFC PATCH net-next] -> [PATCH net-next]
Acked-by: Roopa Prabhu <roopa@cumulusnetworks.com>
we have a similar patch in-house waiting to be up-streamed.
thanks.
next prev parent reply other threads:[~2015-05-22 1:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 0:56 [Bridge] [PATCH net-next] bridge: allow setting hash_max + multicast_router if interface is down Linus Lüssing
2015-05-22 0:56 ` Linus Lüssing
2015-05-22 1:56 ` roopa [this message]
2015-05-22 1:56 ` roopa
2015-05-22 3:11 ` [Bridge] " Cong Wang
2015-05-22 3:11 ` Cong Wang
2015-05-22 3:17 ` [Bridge] " Herbert Xu
2015-05-22 3:17 ` Herbert Xu
2015-05-22 3:27 ` [Bridge] " Cong Wang
2015-05-22 3:27 ` Cong Wang
2015-05-22 3:27 ` Cong Wang
2015-05-22 3:12 ` [Bridge] " Herbert Xu
2015-05-22 3:12 ` Herbert Xu
2015-05-22 3:12 ` Herbert Xu
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=555E8CD9.9030004@cumulusnetworks.com \
--to=roopa@cumulusnetworks.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linus.luessing@c0d3.blue \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wkok@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 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.