netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Einar Lück" <lkml@einar-lueck.de>
To: linux-kernel@vger.kernel.org
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH 2/2] ipv4 routing: multipath with cache support, 2.6.10-rc3
Date: Wed, 09 Feb 2005 21:23:57 +0100	[thread overview]
Message-ID: <420A715D.7050106@einar-lueck.de> (raw)
In-Reply-To: <20050209120157.18dc75c1.davem@davemloft.net>

David S. Miller wrote:

> So essentially you want per-flow multipathing.  Except that you're implementation
> is over-optimizing it to the point where it's only per-flow for your specific
> case where the connections are short lived and high rate.
>
> This hurts long lasting connections.
>
> So I'm pretty much against this change.  Do it right by making it occur
> per-connection attempt, it's not my problem to figure out how to do that
> efficiently, it's your's :-)


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?

Regards,
Einar.

  reply	other threads:[~2005-02-09 20:23 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 [this message]
2005-02-09 20:30         ` David S. Miller
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=420A715D.7050106@einar-lueck.de \
    --to=lkml@einar-lueck.de \
    --cc=linux-kernel@vger.kernel.org \
    --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).