netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Karl Svec <karlsvec@gmail.com>
Cc: netdev@vger.kernel.org, Bill Fink <billfink@mindspring.com>,
	Rick Jones <rick.jones2@hp.com>,
	linux1394-devel@lists.sourceforge.net,
	Roland Dreier <rdreier@cisco.com>
Subject: Re: Bonding support for eth1394?
Date: Tue, 19 Feb 2008 22:27:55 +0100	[thread overview]
Message-ID: <47BB49DB.3060204@s5r6.in-berlin.de> (raw)
In-Reply-To: <47139D28.9010303@hp.com>

Roland Dreier wrote on 2007-10-13:
>  > The bonding sources have a few occurrences of EOPNOTSUPP.  Unless I
>  > missed something, they are all related to setting the hardware address
>  > of the interface.  AFAICS this is impossible with IP over FireWire.  If
>  > it is crucial to bonding to be able to change the slaves' hardware
>  > addresses, then you are out of luck.
> 
> There are a few changes to the bonding driver pending that will add
> support for bonding IP-over-InfiniBand interfaces.  IPoIB also cannot
> change its HW address, so the patches address that issue.
> 
> Once those patches land, bonding eth1394 interfaces may "just work".

Bill Fink wrote on 2007-10-14:
> While that might allow multiple eth1394 interfaces to be bonded,
> I believe the user wanted to bond an eth1394 interface with a normal
> Ethernet interface, and I don't think that will work even with the
> IPoIB bonding changes, since bonding of different fundamental types
> of network interfaces still won't be supported, and I'm pretty sure
> eth1394 is not considered a standard Ethernet interface (different
> MAC address format for one thing).


Karl, you could try kernel 2.6.24(.2) which AFAIU features the mentioned 
changes.
-- 
Stefan Richter
-=====-==--- --=- =--==
http://arcgraph.de/sr/

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

      reply	other threads:[~2008-02-19 21:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <FFB081ED-646B-489D-8836-FBA619A57E3E@gmail.com>
2007-10-13  7:08 ` Bonding support for eth1394? Stefan Richter
2007-10-13 15:34   ` Roland Dreier
2007-10-13 18:03     ` Stefan Richter
2007-10-14  6:18       ` Bill Fink
2007-10-14 11:47         ` Stefan Richter
2007-10-15 17:02           ` Rick Jones
2008-02-19 21:27             ` Stefan Richter [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=47BB49DB.3060204@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=billfink@mindspring.com \
    --cc=karlsvec@gmail.com \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=netdev@vger.kernel.org \
    --cc=rdreier@cisco.com \
    --cc=rick.jones2@hp.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).