From: Carsten Aulbert <carsten.aulbert@aei.mpg.de>
To: Bill Fink <billfink@mindspring.com>
Cc: netdev@vger.kernel.org
Subject: Re: Channel bonding with e1000
Date: Sat, 06 Sep 2008 10:53:44 +0200 [thread overview]
Message-ID: <48C24518.2090500@aei.mpg.de> (raw)
In-Reply-To: <20080905213606.0b4e246a.billfink@mindspring.com>
Hi all,
Bill Fink wrote:
> 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.
I need to go back to Supermicro's manual for that one. The add-on ones
are definitely PCIe.
>
> Of course nothing beats some quick performance tests to determine
> which is the better performing combination.
>
Wisely put :)
Thanks for the input so far. We will start some testing sooner rather
than later to get more out of our file servers!
Cheers
Carsten
next prev parent reply other threads:[~2008-09-06 8:53 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
2008-09-06 8:53 ` Carsten Aulbert [this message]
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=48C24518.2090500@aei.mpg.de \
--to=carsten.aulbert@aei.mpg.de \
--cc=billfink@mindspring.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 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).