From: Ding Tianhong <dingtianhong@huawei.com>
To: Scott Feldman <sfeldma@cumulusnetworks.com>, <vfalico@redhat.com>,
<fubar@us.ibm.com>, <andy@greyhouse.net>
Cc: <netdev@vger.kernel.org>, <roopa@cumulusnetworks.com>,
<shm@cumulusnetworks.com>, <jiri@resnulli.us>
Subject: Re: [PATCH net-next v2 0/5] bonding: final set of netlink patches
Date: Mon, 6 Jan 2014 10:28:26 +0800 [thread overview]
Message-ID: <52CA14CA.9090901@huawei.com> (raw)
In-Reply-To: <20140103220806.1659.25199.stgit@monster-03.cumulusnetworks.com>
On 2014/1/4 6:18, Scott Feldman wrote:
> v2:
> ====
>
> - per Jiri's comment, fix ad_select checking against parm table by
> spliting bond_parse_parm() into several funcs. Go ahead and apply
> same technique to all parameters using parm table.
>
> - fix netlink msg size to including missing nest attr
>
> - drop the last patch for active_slaves. This patch needs to be
> reworked per Jiri's comments and shouldn't hold up finalizing
> the conversion of the existing parameter to netlink attributes.
>
> Ding, assuming this patch set goes in, you should have all you
> need to start converting module parameter setting/checking over to
> funcs in *_options.c.
>
Hi scott:
I have reviewed the bond_options.c and the function bond_option_xxx_set(), I
found I miss something that the operand bond is not exist when bond_param_check(),
so I could not use the existed bond_option_xxx_set(), if I want to convert the
module paramter setting/checking, I need to modify the bond_option_xxx_set() or
add new funcs.
Regards
Ding
> I'll send iproute2 patch for bonding netlink support once this patch
> set is accepted.
>
> v1:
> =====
>
> The following series implements the last set of bonding netlink attributes
> for 802.3ad mode:
>
> lacp_rate
> ad_select
> ad_info, nest of:
> ad_aggregator
> ad_num_ports
> ad_actor_key
> ad_partner_key
> ad_partner_mac
>
> The last patch adds an additional netlink attribute, active_slaves, which
> is a nested list of ifindices for current active slaves. We're using this
> list to enable/disable hashing of ports in a hardware LAG implementation.
> In the same way bonding driver includes/excludes ports for 802.3ad egress
> hashing, hardware ports are included/excluded from egress hashing by
> hardware based on port active status. Yes, data path offloaded to
> hardware, control path remains in kernel via bonding driver.
>
> ---
>
> Scott Feldman (5):
> bonding: add lacp_rate attribute netlink support
> bonding: add ad_select attribute netlink support
> bonding: add ad_info attribute netlink support
> bonding: fix netlink msg size
> bonding: add bounds checking for tbl params
>
>
> drivers/net/bonding/bond_main.c | 45 +++++++++++------
> drivers/net/bonding/bond_netlink.c | 67 +++++++++++++++++++++++++
> drivers/net/bonding/bond_options.c | 96 ++++++++++++++++++++++++++++++++----
> drivers/net/bonding/bond_sysfs.c | 69 +++++++++-----------------
> drivers/net/bonding/bonding.h | 3 +
> include/uapi/linux/if_link.h | 14 +++++
> 6 files changed, 221 insertions(+), 73 deletions(-)
>
prev parent reply other threads:[~2014-01-06 2:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 22:18 [PATCH net-next v2 0/5] bonding: final set of netlink patches Scott Feldman
2014-01-04 2:03 ` David Miller
2014-01-04 10:39 ` Jiri Pirko
2014-01-06 0:52 ` Ding Tianhong
2014-01-06 2:28 ` Ding Tianhong [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=52CA14CA.9090901@huawei.com \
--to=dingtianhong@huawei.com \
--cc=andy@greyhouse.net \
--cc=fubar@us.ibm.com \
--cc=jiri@resnulli.us \
--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 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.