From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] bandwidth aggregation between 2 hosts in the same subnet
Date: Mon, 30 Jul 2007 18:44:07 +0000 [thread overview]
Message-ID: <46AE3177.3030602@riverviewtech.net> (raw)
In-Reply-To: <20070730141010.GA27667@p15145560.pureserver.info>
On 07/30/07 09:10, Ralf Gross wrote:
> I'm trying to increase the bandwidth between two hosts (backup). Both
> hosts are in the same /24 subnet and each of them is connected to a
> Cisco switch by 2 GbE interfaces (intel e1000). The switches/host are
> located in different building which are connected by 3 x GbE.
Ok, this is simple enough.
> My goal is to increase the bandwidth for a single tcp session between
> the two hosts for a backup job (per packet round robin?), not for
> multiple connections between many hosts. I know that I won't get 2 x
> 115Mb/s because of packet reordering, but 20-30% more that a single
> connection would be ok.
*nod*
> Any ideas what I'm missing, or if it's possible at all?
You are barking up the wrong tree, or at least the wrong layer. If you
have any control of the switches in each building, or can have someone
make changes to them for you. Bond the two connections together to make
one logical larger connection. Cisco calls this "EtherChannel" and
Linux calls this "Bonding".
In the long run you will end up with two raw ethernet devices enslaved
in to one bond0 interface. These two bonded / etherchannel interfaces
will have very close to 2 Gbps worth of speed.
Do this on the lower OSI Layer 2 rather than trying (and failing) to do
it on the higher OSI Layer 3 where you are doing it presently.
Grant. . . .
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-07-30 18:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 14:10 [LARTC] bandwidth aggregation between 2 hosts in the same subnet Ralf Gross
2007-07-30 18:44 ` Grant Taylor [this message]
2007-07-30 18:46 ` Paul Zirnik
2007-07-30 20:12 ` Ralf Gross
2007-07-30 20:48 ` Ralf Gross
2007-07-30 21:19 ` Grant Taylor
2007-07-30 21:22 ` Grant Taylor
2007-07-31 7:52 ` Paul Zirnik
2007-07-31 8:05 ` Ralf Gross
2007-07-31 11:01 ` Ralf Gross
2007-07-31 15:25 ` Grant Taylor
2007-07-31 15:31 ` Ralf Gross
2007-07-31 16:31 ` Grant Taylor
2007-07-31 19:58 ` Jay Vosburgh
2007-07-31 21:00 ` Ralf Gross
2007-08-21 16:31 ` Ralf Gross
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=46AE3177.3030602@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--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.