From: David Miller <davem@davemloft.net>
To: dwmw2@infradead.org
Cc: netdev@vger.kernel.org, uweber@astaro.com
Subject: Re: Routing over multiple interfaces
Date: Mon, 01 Nov 2010 14:16:38 -0700 (PDT) [thread overview]
Message-ID: <20101101.141638.116372747.davem@davemloft.net> (raw)
In-Reply-To: <1288645922.5977.41.camel@macbook.infradead.org>
From: David Woodhouse <dwmw2@infradead.org>
Date: Mon, 01 Nov 2010 17:12:02 -0400
> But when I do a large upload, I find that the kernel is only ever using
> a *single* link at a time, rather than both. How can I make it use
> *both* links? It's fine to confine each flow to a single link if it
> doesn't saturate that link... but once the queue is full, it should
> overflow onto the other device.
Once a TCP socket gets a routing cache entry, that's what it uses
for the rest of the life of the connection.
The multi-pathing decision happens at the time the routing
cache entry is created.
What you want is multi-path routing support in the routing cache.
We used to have that, but the guy who implemented it (after bugging
me to integrate it for 4 months straight, non-stop) just did a code
dump and then disappeared and fixed none of the serious fundamental
problems which existed in his code.
After a year of no action, I simply tore out all of his code.
More recently Ulrich Weber gave a presentation at netfilter workshop
on some uplink load balancing work he is doing, you might have
a look at his talk and get in contact with him:
http://people.astaro.com/uweber/uplink_balancing.pdf
next prev parent reply other threads:[~2010-11-01 21:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 21:12 Routing over multiple interfaces David Woodhouse
2010-11-01 21:16 ` David Miller [this message]
2010-11-01 21:35 ` Eric Dumazet
2010-11-01 22:15 ` David Woodhouse
2010-11-02 19:46 ` Pascal Hambourg
2010-11-02 20:04 ` Eric Dumazet
2010-11-02 22:56 ` Pascal Hambourg
2010-11-10 14:50 ` David Woodhouse
2010-11-10 15:08 ` Eric Dumazet
2010-11-10 15:51 ` David Woodhouse
2010-11-02 18:47 ` Bandan Das
2010-11-02 22:10 ` Arnd Hannemann
2010-11-04 12:51 ` Patrick Schaaf
2010-11-04 14:01 ` Eric Dumazet
2010-11-01 21:21 ` Benjamin LaHaise
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=20101101.141638.116372747.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--cc=netdev@vger.kernel.org \
--cc=uweber@astaro.com \
/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).