From: Shmulik Hen <shmulik.hen@intel.com>
To: Jay Vosburgh <fubar@us.ibm.com>
Cc: "Chad N. Tindel" <chad@tindel.net>,
bonding-devel@lists.sourceforge.net, netdev@oss.sgi.com,
linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
Jeff Garzik <jgarzik@pobox.com>,
"Noam, Amir" <amir.noam@intel.com>,
"Mendelson, Tsippy" <tsippy.mendelson@intel.com>,
"Noam, Marom" <noam.marom@intel.com>
Subject: Re: [Bonding-announce] [PATCH SET][bonding] cleanup
Date: Thu, 25 Sep 2003 20:43:40 +0300 [thread overview]
Message-ID: <200309252043.40608.shmulik.hen@intel.com> (raw)
In-Reply-To: <200309251733.h8PHXWpV013559@death.ibm.com>
On Thursday 25 September 2003 08:33 pm, Jay Vosburgh wrote:
>
> Separately, recent ifenslaves have compatibility code within
> them to cover the great "ifenslave calling sequence change" from
> April or so. As much as I love the sleek new slimmed down
> ifenslave, I'm not absolutely sure we can nuke that compatibility
> stuff within ifenslave. I really, really wanna, but I'm not sure
> if it will cause problems for end users. This is the upgrade
> scenario that prompted the creation of the whole "ABI version" and
> compat stuff in the first place; if we don't have to worry about
> that, then the simpler ifenslave can be used, and I think the
> ethtool ABI version hack can go away (since we wouldn't need an ABI
> version if there's only one).
>
> Comments?
>
I think I better leave this for Amir to answer. He's our ABI expert
and this needs carefull consideration, especially now that he's
working on enhancing ifenslave's capabilities for the hot operation
stuff. However, he won't be able to do that before Monday since we're
going out on a long weekend - it's holiday season over here.
--
| Shmulik Hen Advanced Network Services |
| Israel Design Center, Jerusalem |
| LAN Access Division, Platform Networking |
| Intel Communications Group, Intel corp. |
next prev parent reply other threads:[~2003-09-25 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-25 12:49 [PATCH SET][bonding] cleanup Shmulik Hen
2003-09-25 16:22 ` Jay Vosburgh
2003-09-25 16:47 ` [Bonding-announce] " Chad N. Tindel
2003-09-25 17:11 ` Shmulik Hen
2003-09-25 17:33 ` Jay Vosburgh
2003-09-25 17:43 ` Shmulik Hen [this message]
2003-09-25 21:13 ` Chad N. Tindel
2003-10-05 22:28 ` Willy TARREAU
2003-10-12 15:48 ` [PATCH SET][bonding 2.4] cleanup - take 3 Shmulik Hen
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=200309252043.40608.shmulik.hen@intel.com \
--to=shmulik.hen@intel.com \
--cc=amir.noam@intel.com \
--cc=bonding-devel@lists.sourceforge.net \
--cc=chad@tindel.net \
--cc=fubar@us.ibm.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=noam.marom@intel.com \
--cc=tsippy.mendelson@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).