From: Bill Fink <billfink@mindspring.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: netdev@vger.kernel.org, Roland Dreier <rdreier@cisco.com>,
linux1394-devel@lists.sourceforge.net
Subject: Re: Bonding support for eth1394?
Date: Sun, 14 Oct 2007 02:18:50 -0400 [thread overview]
Message-ID: <20071014021850.9bd7c9ad.billfink@mindspring.com> (raw)
In-Reply-To: <4711087E.1050005@s5r6.in-berlin.de>
On Sat, 13 Oct 2007, Stefan Richter wrote:
> Roland Dreier wrote:
> > 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".
>
> Sounds promising. I will keep an eye on it.
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).
-Bill
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-10-14 6:18 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 [this message]
2007-10-14 11:47 ` Stefan Richter
2007-10-15 17:02 ` Rick Jones
2008-02-19 21:27 ` Stefan Richter
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=20071014021850.9bd7c9ad.billfink@mindspring.com \
--to=billfink@mindspring.com \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=rdreier@cisco.com \
--cc=stefanr@s5r6.in-berlin.de \
/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).