netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shmulik Hen <shmulik.hen@intel.com>
To: bonding-devel@lists.sourceforge.net, netdev@oss.sgi.com
Subject: [SET 2][PATCH 0/8][bonding] Propagating master's settings to slaves
Date: Fri, 8 Aug 2003 17:44:50 +0300	[thread overview]
Message-ID: <200308081744.50160.shmulik.hen@intel.com> (raw)

Hi,

	This set 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. Our set was already sent to the bond-devel list
on 6/7 and since we didn't get any negative feedback, we would
like to make it public.

Applies on 2.4.22-rc1. Assumes patch set 1 was already accepted.

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.
2 - Change monitoring function use the above functionality.
3 - Modes that don't use primary don't use the above functionality.
4 - Decouple promiscuous handling from the multicast mode setting.
5 - Add support for changing HW address and MTU with proper unwind.
6 - Same thing for ALB/TLB modes.
7 - Consolidate procfs code, add CHANGENAME handler
8 - Enhance netdev notification handling. Add comment block
    and bump version.

The things that didn't go in are Jay's IP settings and flags
propagation since later dicussions on bond-devel list proved
them to be unnecessary.

-- 
| Shmulik Hen   Advanced Network Services  |
| Israel Design Center, Jerusalem          |
| LAN Access Division, Platform Networking |
| Intel Communications Group, Intel corp.  |

                 reply	other threads:[~2003-08-08 14:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200308081744.50160.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).