All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: hadi@cyberus.ca
Cc: lkml@einar-lueck.de, linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [RFC][PATCH 2/2] ip multipath, bk head (EXPERIMENTAL)
Date: Mon, 13 Sep 2004 22:42:32 -0700	[thread overview]
Message-ID: <20040913224232.4b979c7d.davem@davemloft.net> (raw)
In-Reply-To: <1095129624.1060.45.camel@jzny.localdomain>

On 13 Sep 2004 22:40:24 -0400
jamal <hadi@cyberus.ca> wrote:

> As long as whatever arrangement ensures that no packet reordering
> happens, should be sane. Yes, current scheme is broken in some ways (but
> guarantees packet ordering within a flow).

I think his changes ensure this as well, at least for local system
sockets.  You'll only get a new hop each time a route lookup is
performed, which is only done once per socket unless the path
becomes "sick" and TCP decides to try and do a relookup of the
destination.

I'm kind of ambivalent about these changes.  I definitely like the
first patch which cleans up those huge functions in route.c :-)
But there are things I like about the current behavior, although I
understand why people want things to work the way Einar is changing
it to.

  reply	other threads:[~2004-09-14  5:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-13 10:36 [RFC][PATCH 2/2] ip multipath, bk head (EXPERIMENTAL) Einar Lueck
2004-09-14  2:40 ` jamal
2004-09-14  5:42   ` David S. Miller [this message]
2004-09-14 12:14     ` jamal
2004-09-14 12:38     ` Einar Lueck
2004-09-14 15:08       ` Phil Oester

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=20040913224232.4b979c7d.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=hadi@cyberus.ca \
    --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 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.