All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chris Friesen" <cfriesen@nortel.com>
To: Andy Gospodarek <andy@greyhouse.net>
Cc: Jay Vosburgh <fubar@us.ibm.com>,
	netdev@vger.kernel.org, bonding-devel@lists.sourceforge.net
Subject: Re: [Bonding-devel] quick help with bonding?
Date: Thu, 29 Mar 2007 19:19:08 -0600	[thread overview]
Message-ID: <460C658C.7090803@nortel.com> (raw)
In-Reply-To: <20070330003630.GA18319@gospo.rdu.redhat.com>

Andy Gospodarek wrote:

> If you are looking for a decent source for patches you could consider
> downloading the latest source-rpm from RHEL4/CentOS4.  The bonding
> driver in those releases have been updated to much later code and I can
> tell you from personal experience they work pretty well.  You may need
> to do some backporting to get the latest arp-monitoring features, but
> let me know if you need a hand with that, I might have some laying
> around. ;)

I'm just about to load a kernel with a backport of bonding from 2.6.14. 
  I'll try it out and if it doesn't help I'll try the RHEL4 one.

> Does eth6 use the same hardware/driver as eth4/5?  (Sorry if I missed
> that in the thread, but didn't see if you indicated that it did.)

No, eth6 is an AMD-8111.

Chris

  reply	other threads:[~2007-03-30  1:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-29 16:14 quick help with bonding? Chris Friesen
2007-03-29 16:24 ` [Bonding-devel] " Jay Vosburgh
2007-03-29 18:16 ` Andy Gospodarek
2007-03-29 22:08   ` Chris Friesen
2007-03-29 22:30     ` Jay Vosburgh
2007-03-29 23:01       ` Mark Huth
2007-03-29 23:42       ` Chris Friesen
2007-03-30  0:13         ` Jay Vosburgh
2007-03-30  0:36         ` Andy Gospodarek
2007-03-30  1:19           ` Chris Friesen [this message]
2007-03-30  1:26             ` Chris Friesen
2007-03-30  2:48               ` Andy Gospodarek
2007-03-30  2:49               ` Chris Friesen
2007-04-02 22:28 ` Chris Friesen

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=460C658C.7090803@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=andy@greyhouse.net \
    --cc=bonding-devel@lists.sourceforge.net \
    --cc=fubar@us.ibm.com \
    --cc=netdev@vger.kernel.org \
    /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.