From: "David S. Miller" <davem@davemloft.net>
To: "Einar Lück" <lkml@einar-lueck.de>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [PATCH 2/2] ipv4 routing: multipath with cache support, 2.6.10-rc3
Date: Wed, 9 Feb 2005 12:30:04 -0800 [thread overview]
Message-ID: <20050209123004.2d65e1cf.davem@davemloft.net> (raw)
In-Reply-To: <420A715D.7050106@einar-lueck.de>
On Wed, 09 Feb 2005 21:23:57 +0100
Einar Lück <lkml@einar-lueck.de> wrote:
> We do not want per-flow multipathing. We want per connection
> multipathing with fast route lookups (that's why we have all routes in
> the cache). That is exactly what we implemented. Our tests prove that
> a connection keeps its route as long as it lives (the dstentry remains
> associated with the socket). That's why I do not really understand why
> our approach hurts long lasting connections in any way. Can you
> explain your point more precisely?
This was brought up before. It's the case where the system is acting
as a router, you have to consider that case and not just the one where
the local system is where the connections are originating from.
Your trick only works because of how routes are cached per-socket.
Once you get into the realm of traffic going through the machine as
a router, the trick stops to work.
next prev parent reply other threads:[~2005-02-09 20:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 11:19 [PATCH 2/2] ipv4 routing: multipath with cache support, 2.6.10-rc3 Einar Lück
2004-12-20 15:10 ` Einar Lück
2005-02-03 1:23 ` David S. Miller
2005-02-09 13:28 ` Einar Lück
2005-02-09 20:01 ` David S. Miller
2005-02-09 20:23 ` Einar Lück
2005-02-09 20:30 ` David S. Miller [this message]
2005-02-09 20:42 ` Einar Lück
2005-02-09 21:17 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2004-12-20 11:15 Einar Lück
2004-12-20 11:13 Einar Lück
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=20050209123004.2d65e1cf.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@einar-lueck.de \
--cc=netdev@oss.sgi.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).