From: Shmulik Hen <shmulik.hen@intel.com>
To: bonding-devel@lists.sourceforge.net, netdev@oss.sgi.com
Subject: [bonding][2/3] Synchronizing 2.4-2.6
Date: Wed, 27 Aug 2003 20:03:09 +0300 [thread overview]
Message-ID: <200308272003.09957.shmulik.hen@intel.com> (raw)
This is set 2 that merges parts of Jay Vosburgh's experimental
propagation stuff from 5/22 with all the fixes/enhancements
we've developed according to the RFC published on bond-devel
list on 6/2.
Applies on 2.4.22. Assumes patch set 1 was already applied.
patch set can be downloaded from:
http://osdn.dl.sourceforge.net/sourceforge/bonding/patch_set_2_propagation.tar.bz2
This will update the following files:
drivers/net/bonding/bond_alb.c
drivers/net/bonding/bond_alb.h
drivers/net/bonding/bonding.h
drivers/net/bonding/bond_main.c
Description:
patch 1 - Distinguish between modes that use a primary slave from
those that don't, and propagate settings accordingly; Consolidate
change_active opeartions and add reselect_active and find_best
opeartions.
patch 2 - Change monitoring function use the above functionality.
patch 3 - Modes that don't use primary don't use the above
functionality.
patch 4 - Decouple promiscuous handling from the multicast mode
setting.
patch 5 - Add support for changing HW address and MTU with proper
unwind in old modes.
patch 6 - Same thing for ALB/TLB modes.
patch 7 - Consolidate /proc code, add CHANGENAME handler
patch 8 - Enhance netdev notification handling.
Add comment block and bump version.
--
| Shmulik Hen Advanced Network Services |
| Israel Design Center, Jerusalem |
| LAN Access Division, Platform Networking |
| Intel Communications Group, Intel corp. |
next reply other threads:[~2003-08-27 17:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 17:03 Shmulik Hen [this message]
2003-08-27 21:51 ` [bonding][2/3] Synchronizing 2.4-2.6 Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2003-08-28 7:26 Hen, Shmulik
2003-08-28 16:02 ` Jeff Garzik
2003-08-31 12:19 Hen, Shmulik
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=200308272003.09957.shmulik.hen@intel.com \
--to=shmulik.hen@intel.com \
--cc=bonding-devel@lists.sourceforge.net \
--cc=netdev@oss.sgi.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).