From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
To: Jay Vosburgh <jay.vosburgh@canonical.com>,
Nikolay Aleksandrov <razor@blackwall.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
Veaceslav Falico <vfalico@gmail.com>,
Andy Gospodarek <gospo@cumulusnetworks.com>
Subject: Re: [PATCH net-next] bonding: 3ad: apply ad_actor settings changes immediately
Date: Wed, 3 Feb 2016 20:16:37 +0100 [thread overview]
Message-ID: <56B25215.10204@cumulusnetworks.com> (raw)
In-Reply-To: <7907.1454526331@famine>
On 02/03/2016 08:05 PM, Jay Vosburgh wrote:
> Nikolay Aleksandrov <razor@blackwall.org> wrote:
>
>> From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
>>
>> Currently the bonding allows to set ad_actor_system and prio while the
>> bond device is down, but these are actually applied only if there aren't
>> any slaves yet (applied to bond device when first slave shows up, and to
>> slaves at 3ad bind time). After this patch changes are applied immediately
>> and the new values can be used/seen after the bond's upped so it's not
>> necessary anymore to release all and enslave again to see the changes.
>>
>> CC: Jay Vosburgh <j.vosburgh@gmail.com>
>> CC: Veaceslav Falico <vfalico@gmail.com>
>> CC: Andy Gospodarek <gospo@cumulusnetworks.com>
>> Signed-off-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
>
> Looks good to me.
>
> Signed-off-by: Jay Vosburgh <jay.vosburgh@canonical.com>
>
> -J
>
Thanks Jay. Do you think it makes sense to allow setting these while the
bond is up ? I don't see any serious problems.
next prev parent reply other threads:[~2016-02-03 19:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 12:17 [PATCH net-next] bonding: 3ad: apply ad_actor settings changes immediately Nikolay Aleksandrov
2016-02-03 19:05 ` Jay Vosburgh
2016-02-03 19:16 ` Nikolay Aleksandrov [this message]
2016-02-03 19:48 ` Jay Vosburgh
2016-02-03 19:55 ` Nikolay Aleksandrov
2016-02-09 9:46 ` David Miller
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=56B25215.10204@cumulusnetworks.com \
--to=nikolay@cumulusnetworks.com \
--cc=davem@davemloft.net \
--cc=gospo@cumulusnetworks.com \
--cc=jay.vosburgh@canonical.com \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
--cc=vfalico@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.