All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerry Creager N5JXS <n5jxs@tamu.edu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] 2 NICS. More Bandwidth?
Date: Tue, 28 May 2002 14:08:00 +0000	[thread overview]
Message-ID: <marc-lartc-102259492412874@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102258099201350@msgid-missing>

We're assuming 100 Mb/sec now, right?  The rules change a little with 
GBE NICs wrt who's got the better hardware...

Bonding has actually been available for some time; the beowulf clusters 
have taken advantage of it for years.  I believe it went into the kernel 
tree around 2.0.16, but it could have been after the release of the 
2.2.x set.

A couple of things have to be considered, including the quality of your 
NICs.  Some of th elow end ones will never provide good performance 
(RealTek comes to mind in our experience) while almost anything with the 
older DEC Tulip chipset will perform well, as will most of the Intel 
products.

Is your PCI bus speed up to the task of multiple NICs?  An older 
computer running a slow bus can bog down at times.

Also, if your server is busy, multiple interfaces and a round-robin DNS 
implementation may be a good answer without bonding.  Similarly, access 
via a switches, rather than shared, network interface is a performance 
enhancer.

gerry

Michael T. Babcock wrote:

>>I have a Fileserver on my local network.
>>Is there any way, or is it just possible increase the bandwidth to the
>>fileserver if it has 2NICS.
>>
> 
> Look up 'bonding' in newer kernels...
> 


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2002-05-28 14:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-28 10:14 [LARTC] 2 NICS. More Bandwidth? Svavar Örn Eysteinsson
2002-05-28 12:40 ` Michael T. Babcock
2002-05-28 14:08 ` Gerry Creager N5JXS [this message]
2002-06-01  1:53 ` Leonardo Balliache

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=marc-lartc-102259492412874@msgid-missing \
    --to=n5jxs@tamu.edu \
    --cc=lartc@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.