From: David Miller <davem@davemloft.net>
To: Jianhua.Xie@freescale.com
Cc: netdev@vger.kernel.org, edumazet@google.com,
j.vosburgh@gmail.com, vfalico@gmail.com, andy@greyhouse.net
Subject: Re: [PATCH v2 net-next 0/2] bonding: Introduce 4 AD link speed
Date: Fri, 21 Nov 2014 17:16:13 -0500 (EST) [thread overview]
Message-ID: <20141121.171613.504119260083729947.davem@davemloft.net> (raw)
In-Reply-To: <1416386939-24591-1-git-send-email-Jianhua.Xie@freescale.com>
From: Xie Jianhua <Jianhua.Xie@freescale.com>
Date: Wed, 19 Nov 2014 16:48:57 +0800
> From: Jianhua Xie <Jianhua.Xie@freescale.com>
>
> The speed field of AD Port Key was based on bitmask, it supported 5
> kinds of link speed at most, as there were only 5 bits in the speed
> field of the AD Port Key. This patches series change the speed type
> (AD_LINK_SPEED_BITMASK) from bitmask to enum type in order to enhance
> speed type from 5 to 32, and then introduce 4 AD link speed to fix
> agg_bandwidth.
>
> Jianhua Xie (2):
> bonding: change AD_LINK_SPEED_BITMASK to enum to suport more speed
> bonding: Introduce 4 AD link speed to fix agg_bandwidth
>
> drivers/net/bonding/bond_3ad.c | 102 ++++++++++++++++++++++++++++-------------
> 1 file changed, 70 insertions(+), 32 deletions(-)
>
> --
> v2:
> * Use an enum type to instead of the bitmask, not expand speed field,
>
> v1:
> * Compress RFC patches #2 to #5 into one single patch.
> * Fix inexact commit information.
Series applied, thanks.
prev parent reply other threads:[~2014-11-21 22:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 8:48 [PATCH v2 net-next 0/2] bonding: Introduce 4 AD link speed Xie Jianhua
2014-11-19 8:48 ` [PATCH 1/2] bonding: change AD_LINK_SPEED_BITMASK to enum to suport more speed Xie Jianhua
2014-11-19 8:48 ` [PATCH 2/2] bonding: Introduce 4 AD link speed to fix agg_bandwidth Xie Jianhua
2014-11-20 0:10 ` [PATCH v2 net-next 0/2] bonding: Introduce 4 AD link speed David Miller
2014-11-21 22:16 ` 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=20141121.171613.504119260083729947.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Jianhua.Xie@freescale.com \
--cc=andy@greyhouse.net \
--cc=edumazet@google.com \
--cc=j.vosburgh@gmail.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