From: Bill Fink <billfink@mindspring.com>
To: Carsten Aulbert <carsten.aulbert@aei.mpg.de>
Cc: netdev@vger.kernel.org
Subject: Re: Channel bonding with e1000
Date: Fri, 5 Sep 2008 21:36:06 -0400 [thread overview]
Message-ID: <20080905213606.0b4e246a.billfink@mindspring.com> (raw)
In-Reply-To: <48C0EF8A.9070103@aei.mpg.de>
On Fri, 05 Sep 2008, Carsten Aulbert wrote:
> I have a brief problem and would ask for a little assistance:
>
> On a few data servers we intend to do channel bonding. The boxes have
> two NICs on the motherboard and two extra ones on an expansion card:
>
> 04:00.0 Ethernet controller: Intel Corporation 631xESB/632xESB DPT LAN
> Controller Copper (rev 01)
> 04:00.1 Ethernet controller: Intel Corporation 631xESB/632xESB DPT LAN
> Controller Copper (rev 01)
> 05:02.0 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet
> Controller (rev 03)
> 05:02.1 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet
> Controller (rev 03)
>
> My simple question would be: Does it matter which two ports I can use to
> channel together when using in a set-up with MTU=9000?
I don't know the specifics of your case, but sometimes the builtin
NICs on the motherboard may not have as much memory buffering as
the better addon NICs.
Also check the respective PCI buses of the onboard NICs versus the
addon NICs. If one is PCI versus PCI-X or PCI-E, or are different
speeds or bus widths, this can obviously significantly impact
performance, especially when doing bonding.
Of course nothing beats some quick performance tests to determine
which is the better performing combination.
-Bill
next prev parent reply other threads:[~2008-09-06 1:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 8:36 Channel bonding with e1000 Carsten Aulbert
2008-09-05 14:37 ` Jay Vosburgh
2008-09-06 1:36 ` Bill Fink [this message]
2008-09-06 8:53 ` Carsten Aulbert
2008-09-08 18:37 ` Brandeburg, Jesse
2008-09-09 6:21 ` Carsten Aulbert
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=20080905213606.0b4e246a.billfink@mindspring.com \
--to=billfink@mindspring.com \
--cc=carsten.aulbert@aei.mpg.de \
--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.