From: David Miller <davem@davemloft.net>
To: andy@greyhouse.net
Cc: netdev@vger.kernel.org, fubar@us.ibm.com, nhorman@tuxdriver.com
Subject: Re: [PATCH net-next-2.6 1/2][v2] bonding: add all_slaves_active parameter
Date: Sat, 05 Jun 2010 02:54:40 -0700 (PDT) [thread overview]
Message-ID: <20100605.025440.233678822.davem@davemloft.net> (raw)
In-Reply-To: <20100602183921.GK7497@gospo.rdu.redhat.com>
From: Andy Gospodarek <andy@greyhouse.net>
Date: Wed, 2 Jun 2010 14:39:21 -0400
>
> v2: changed parameter name from 'keep_all' to 'all_slaves_active' and
> skipped setting slaves to inactive rather than creating a new flag at
> Jay's suggestion.
>
> In an effort to suppress duplicate frames on certain bonding modes
> (specifically the modes that do not require additional configuration on
> the switch or switches connected to the host), code was added in the
> generic receive patch in 2.6.16. The current behavior works quite well
> for most users, but there are some times it would be nice to restore old
> functionality and allow all frames to make their way up the stack.
>
> This patch adds support for a new module option and sysfs file called
> 'all_slaves_active' that will restore pre-2.6.16 functionality if the
> user desires. The default value is '0' and retains existing behavior,
> but the user can set it to '1' and allow all frames up if desired.
>
> Signed-off-by: Andy Gospodarek <andy@greyhouse.net>
> Signed-off-by: Jay Vosburgh <fubar@us.ibm.com>
> Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
Applied.
prev parent reply other threads:[~2010-06-05 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 18:39 [PATCH net-next-2.6 1/2][v2] bonding: add all_slaves_active parameter Andy Gospodarek
2010-06-05 9:54 ` 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=20100605.025440.233678822.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--cc=fubar@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.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