From: Laurent Deniel <laurent.deniel@free.fr>
To: shmulik.hen@intel.com
Cc: bonding-devel@lists.sourceforge.net, netdev@oss.sgi.com
Subject: Re: [Bonding-devel] [bonding][3/3] Synchronizing 2.4-2.6
Date: Thu, 28 Aug 2003 19:17:19 +0200 [thread overview]
Message-ID: <3F4E391F.6030403@free.fr> (raw)
In-Reply-To: 200308272008.20139.shmulik.hen@intel.com
Shmulik Hen wrote:
>
> patch 7 - eliminate the multicast_more module param and use the
> USES_PRIMARY macro instead.
Do you know that this breaks upward compatibility ? i.e. this now
assumes that for instance in active backup mode, only the active
slave registers the multicast addresses (i.e. multicast_mode = 1)
while the default from the very beginning was all NIC (multicast_mode = 0).
And this removes the possiblity of disabling multicast stuff.
But if everyone is OK ... (I'd be since I currently only use
multicast_mode = 1 ;-)
Laurent
prev parent reply other threads:[~2003-08-28 17:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 17:08 [bonding][3/3] Synchronizing 2.4-2.6 Shmulik Hen
2003-08-28 17:17 ` Laurent Deniel [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=3F4E391F.6030403@free.fr \
--to=laurent.deniel@free.fr \
--cc=bonding-devel@lists.sourceforge.net \
--cc=netdev@oss.sgi.com \
--cc=shmulik.hen@intel.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).