From: Jonathan Toppins <jtoppins@cumulusnetworks.com>
To: Mahesh Bandewar <maheshb@google.com>
Cc: linux-netdev <netdev@vger.kernel.org>,
Jay Vosburgh <j.vosburgh@gmail.com>,
Veaceslav Falico <vfalico@gmail.com>,
Andy Gospodarek <gospo@cumulusnetworks.com>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH linux v1 net-next 4/4] bonding: add netlink support for sys prio, actor sys mac, and port key
Date: Mon, 04 May 2015 16:48:39 -0400 [thread overview]
Message-ID: <5547DB27.60608@cumulusnetworks.com> (raw)
In-Reply-To: <CAF2d9jjKmYd7pVVVnsXQkGoysQy09Ro4VFA7a8etFYYTzv9+Ag@mail.gmail.com>
On 5/1/15 7:15 PM, Mahesh Bandewar wrote:
>>
>> @@ -548,6 +585,19 @@ static int bond_fill_info(struct sk_buff *skb,
>> bond->params.ad_select))
>> goto nla_put_failure;
>>
>> + if (nla_put_u16(skb, IFLA_BOND_AD_ACTOR_SYS_PRIO,
>> + bond->params.ad_actor_sys_prio))
>> + goto nla_put_failure;
>> +
>> + if (nla_put_u16(skb, IFLA_BOND_AD_USER_PORT_KEY,
>> + bond->params.ad_user_port_key))
>> + goto nla_put_failure;
>> +
>> + if (nla_put(skb, IFLA_BOND_AD_ACTOR_SYSTEM,
>> + sizeof(bond->params.ad_actor_system),
>> + &bond->params.ad_actor_system))
>> + goto nla_put_failure;
>> +
> I think this does not make sense for MODE != 8023AD. Shouldn't this be
> inside next block which is for the 802.3ad mode?
>
>> if (BOND_MODE(bond) == BOND_MODE_8023AD) {
>> struct ad_info info;
>>
>> diff --git a/include/uapi/linux/if_link.h b/include/uapi/linux/if_link.h
>> index d9cd192..6d6e502 100644
>> --- a/include/uapi/linux/if_link.h
>> +++ b/include/uapi/linux/if_link.h
>> @@ -417,6 +417,9 @@ enum {
>> IFLA_BOND_AD_LACP_RATE,
>> IFLA_BOND_AD_SELECT,
>> IFLA_BOND_AD_INFO,
>> + IFLA_BOND_AD_ACTOR_SYS_PRIO,
>> + IFLA_BOND_AD_USER_PORT_KEY,
>> + IFLA_BOND_AD_ACTOR_SYSTEM,
> Even though this is available / stored in bond->param, I feel that
> these belong to IFLA_BOND_AD_INFO_, no?
Can see it fitting in there. Not sure of the history of the AD_INFO_*
object. Evaluating implementation, will respond tomorrow with conclusion.
>
>> __IFLA_BOND_MAX,
>> };
>>
>> --
>> 1.7.10.4
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe netdev" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-05-04 20:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 17:24 [PATCH linux v1 net-next 0/5] add netlink support for new lacp bonding parameters Jonathan Toppins
2015-05-01 17:24 ` [PATCH linux v1 net-next 1/4] bonding: Allow userspace to set actors' system_priority in AD system Jonathan Toppins
2015-05-01 17:24 ` [PATCH linux v1 net-next 2/4] bonding: Allow userspace to set actors' macaddr in an AD-system Jonathan Toppins
2015-05-01 17:24 ` [PATCH linux v1 net-next 3/4] bonding: Implement user key part of port_key in an AD system Jonathan Toppins
2015-05-01 17:24 ` [PATCH linux v1 net-next 4/4] bonding: add netlink support for sys prio, actor sys mac, and port key Jonathan Toppins
2015-05-01 23:15 ` Mahesh Bandewar
2015-05-04 20:48 ` Jonathan Toppins [this message]
2015-05-06 1:07 ` Jonathan Toppins
2015-05-06 7:07 ` Mahesh Bandewar
2015-05-01 17:24 ` [PATCH iproute2 v1 net-next] iplink_bond: add support for ad_actor and port_key options Jonathan Toppins
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=5547DB27.60608@cumulusnetworks.com \
--to=jtoppins@cumulusnetworks.com \
--cc=davem@davemloft.net \
--cc=gospo@cumulusnetworks.com \
--cc=j.vosburgh@gmail.com \
--cc=maheshb@google.com \
--cc=netdev@vger.kernel.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 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).