netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shmulik Hen <shmulik.hen@intel.com>
To: "Jay Vosburgh" <fubar@us.ibm.com>,
	"David S. Miller" <davem@redhat.com>,
	"Chad N. Tindel" <chad@tindel.net>, <jgarzik@pobox.com>,
	<bonding-devel@lists.sourceforge.net>, <netdev@oss.sgi.com>
Subject: Re: [Bonding-devel] Re: [bonding] compatibilty issues
Date: Thu, 2 Oct 2003 09:37:51 +0300	[thread overview]
Message-ID: <200310020937.51781.shmulik.hen@intel.com> (raw)
In-Reply-To: <E791C176A6139242A988ABA8B3D9B38A02A464F9@hasmsx403.iil.intel.com>

On Wednesday 01 October 2003 10:25 pm, Jay Vosburgh wrote:
> 	Same here, but I'd like to have a list somewhere of what each
> of the ABI versions is for and how they're supposed to behave. 
> It's starting to look like we're going to be adding these on a
> semi-regular basis, so we need to keep track of what each one does
> and why.
>

Where should such a list go ?
Currently, 0 or none is for doing everything the old way.
1 is for not setting slaves HW addr via ifenslave and leaving them in 
down state so the driver gets them with their unique address, sets 
them according to the mode and brings them up. The driver also 
restores the original address upon release. This is all done for 
supporting the 802.3ad, TLB, ALB modes.
2 will be for ifenslave lite that doesn't propagate the bond's IP 
settings to the slaves.
I'm guessing that 3 will be used to designate the new support for hot 
operations that Amir is working on.

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

       reply	other threads:[~2003-10-02  6:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E791C176A6139242A988ABA8B3D9B38A02A464F9@hasmsx403.iil.intel.com>
2003-10-02  6:37 ` Shmulik Hen [this message]
2003-10-03 19:57   ` [Bonding-devel] Re: [bonding] compatibilty issues Jay Vosburgh
2003-10-02  7:57 ` Shmulik Hen
     [not found] <E791C176A6139242A988ABA8B3D9B38A02A464F2@hasmsx403.iil.intel.com>
2003-10-01  8:49 ` Shmulik Hen
2003-10-01 18:26   ` Chad N. Tindel
2003-10-01 19:25     ` Jay Vosburgh
2003-09-30 11:42 Shmulik Hen
2003-09-30 16:39 ` [Bonding-devel] " Jay Vosburgh
2003-09-30 21:36   ` Chad N. Tindel
2003-10-01  7:05     ` 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=200310020937.51781.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 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).