From: David Miller <davem@davemloft.net>
To: sfeldma@cumulusnetworks.com
Cc: vfalico@redhat.com, fubar@us.ibm.com, andy@greyhouse.net,
netdev@vger.kernel.org, roopa@cumulusnetworks.com,
shm@cumulusnetworks.com
Subject: Re: [PATCH net-next v2 0/8] bonding: add more netlink attributes
Date: Sat, 14 Dec 2013 01:08:36 -0500 (EST) [thread overview]
Message-ID: <20131214.010836.1667099923747304358.davem@davemloft.net> (raw)
In-Reply-To: <20131212214558.21629.92365.stgit@monster-03.cumulusnetworks.com>
From: Scott Feldman <sfeldma@cumulusnetworks.com>
Date: Thu, 12 Dec 2013 14:09:48 -0800
> v2:
>
> Addressed v1 review comments. In particular, Jay's concern about
> current sysfs ordering limitations carrying over to iproute. Netlink
> attributes are processed in a priority order in
> bond_netlink.c:bond_changelink(). Lower priority attributes can't undo
> higher priority attributes when attempting to set both with iproute
> command. For example, this command will fail:
>
> ip link add bond1 type bond mode active-backup miimon 10 arp_interval 10
>
> Because we're trying to create a new bond to use incompatible miimon
> and ARP interval attributes. However, if attributes are applied
> one-at-a-time, previously applied attributes can be overridden:
>
> ip link add bond1 type bond mode active-backup miimon 10
> ip link set dev bond1 type bond arp_interval 10
>
> These two commands succeed. The bond is first created to use miimon.
> Next, the bond is converted to use ARP interval, which undoes miimon.
>
> v1:
>
> Following Jiri Pirko's lead, add more bonding netlink attributes. Sending
> matching iproute2 patch separately. sysfs access to attributes is
> retained.
Series applied, thanks Scott.
prev parent reply other threads:[~2013-12-14 6:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 22:09 [PATCH net-next v2 0/8] bonding: add more netlink attributes Scott Feldman
2013-12-14 6:08 ` David Miller [this message]
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=20131214.010836.1667099923747304358.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--cc=fubar@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=sfeldma@cumulusnetworks.com \
--cc=shm@cumulusnetworks.com \
--cc=vfalico@redhat.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).