From: Shmulik Hen <shmulik.hen@intel.com>
To: "David S. Miller" <davem@redhat.com>,
"Jeff Garzik" <jgarzik@pobox.com>, <chad@tindel.net>,
"Jay Vosburgh" <fubar@us.ibm.com>
Cc: bonding-devel@lists.sourceforge.net, netdev@oss.sgi.com
Subject: Re: [bonding] compatibilty issues
Date: Tue, 30 Sep 2003 14:42:31 +0300 [thread overview]
Message-ID: <200309301442.31991.shmulik.hen@intel.com> (raw)
In-Reply-To: <E791C176A6139242A988ABA8B3D9B38A02A464F1@hasmsx403.iil.intel.com>
Guys,
I'm going to need a ruling here :)
Re-creating those 19 trees each time is killing me and I would like to
reduce the number of iterations to a minimum.
I'm currently working on putting back all compatibility stuff for 2.4.
I would like to also get any input/reservations about other issues
(besides compatibility and the multicast param) so I may get a chance
to get them all in at once.
Once we get that settled, I can start working on a 2.6 version that
also handles any compatibility issues (preferrably as the last patch
of the series). I'm working in the assumption that 2.4-2.6 similarity
is no longer an option for bonding.
--
| Shmulik Hen Advanced Network Services |
| Israel Design Center, Jerusalem |
| LAN Access Division, Platform Networking |
| Intel Communications Group, Intel corp. |
next parent reply other threads:[~2003-09-30 11:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E791C176A6139242A988ABA8B3D9B38A02A464F1@hasmsx403.iil.intel.com>
2003-09-30 11:42 ` Shmulik Hen [this message]
2003-09-30 16:39 ` [Bonding-devel] Re: [bonding] compatibilty issues Jay Vosburgh
2003-09-30 21:36 ` Chad N. Tindel
2003-10-01 7:05 ` David S. Miller
2003-09-29 23:25 Chad N. Tindel
2003-09-29 23:38 ` Jeff Garzik
2003-09-30 0:23 ` Chad N. Tindel
2003-09-30 5:54 ` David S. Miller
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=200309301442.31991.shmulik.hen@intel.com \
--to=shmulik.hen@intel.com \
--cc=bonding-devel@lists.sourceforge.net \
--cc=chad@tindel.net \
--cc=davem@redhat.com \
--cc=fubar@us.ibm.com \
--cc=jgarzik@pobox.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.