public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Ding Tianhong <dthxman@gmail•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 0/4] bonding: final set of netlink patches
Date: Sat, 28 Dec 2013 23:11:50 +0800	[thread overview]
Message-ID: <52BEEA36.7030204@gmail.com> (raw)
In-Reply-To: <20131228065712.6296.34291.stgit@monster-03.cumulusnetworks.com>

于 2013/12/28 15:15, Scott Feldman 写道:
> 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 (4):
>       bonding: add lacp_rate attribute netlink support
>       bonding: add ad_select attribute netlink support
>       bonding: add ad_info attribute netlink support
>       bonding: add active_slaves attribute
> 
> 
>  drivers/net/bonding/bond_netlink.c |  100 +++++++++++++++++++++++++++++++++
>  drivers/net/bonding/bond_options.c |   51 +++++++++++++++++
>  drivers/net/bonding/bond_sysfs.c   |  108 +++++++++++++++++++++---------------
>  drivers/net/bonding/bonding.h      |    2 +
>  include/uapi/linux/if_link.h       |   15 +++++
>  5 files changed, 229 insertions(+), 47 deletions(-)
> 

Reviewed-by: Ding Tianhong <dingtianhong@huawei•com>

      reply	other threads:[~2013-12-28 15:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-28  7:15 [PATCH net-next 0/4] bonding: final set of netlink patches Scott Feldman
2013-12-28 15:11 ` 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=52BEEA36.7030204@gmail.com \
    --to=dthxman@gmail$(echo .)com \
    --cc=andy@greyhouse$(echo .)net \
    --cc=fubar@us$(echo .)ibm.com \
    --cc=jiri@resnulli$(echo .)us \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=roopa@cumulusnetworks$(echo .)com \
    --cc=sfeldma@cumulusnetworks$(echo .)com \
    --cc=shm@cumulusnetworks$(echo .)com \
    --cc=vfalico@redhat$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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