netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: kaber@trash.net, netdev@oss.sgi.com
Subject: Re: IPsec xfrm resolution
Date: Thu, 17 Mar 2005 20:32:31 -0800	[thread overview]
Message-ID: <20050317203231.1b649f60.davem@davemloft.net> (raw)
In-Reply-To: <20050219092314.GA8153@gondor.apana.org.au>

On Sat, 19 Feb 2005 20:23:14 +1100
Herbert Xu <herbert@gondor.apana.org.au> wrote:

> 1) The application must be able to react to MTU changes anyway.

This would seem to be the case, but keep in mind that if
we're going through all this trouble to improve this
quality of implementation issue, we should really get this
right.

On a more practical side, let's use an example to drive home
a point.  Say you're using DNS-sec or something like that for
all outgoing connections, and you're using non-blocking sockets
for all of your stuff.

Every time I use TCP to talk to a unique host, we're going to
mis-estimate the MTU, get an entire send queue full of too-large
packets, then have to resegment the entire thing once the SA is
resolved.  We'll eat a retransmit every such connection as well.
And actually, we'll have to resend about 4 frames (depends upon
what the initial send cwnd is set to, it's usually 4 for ethernet
size MTUs).

Anyways, in truth I'm being very picky :-)  Is there any prototype
or beginnings of these ideas anywhere?

  parent reply	other threads:[~2005-03-18  4:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050209085251.GA9030@gondor.apana.org.au>
     [not found] ` <420B9DF1.3020704@trash.net>
     [not found]   ` <20050210202810.GA1609@gondor.apana.org.au>
     [not found]     ` <42144C3F.2060501@trash.net>
     [not found]       ` <20050217091137.GA9476@gondor.apana.org.au>
2005-02-17 23:26         ` IPsec xfrm resolution Patrick McHardy
2005-02-18 10:08           ` Herbert Xu
2005-02-19  6:03             ` Patrick McHardy
2005-02-19  9:23               ` Herbert Xu
2005-02-19 12:29                 ` Patrick McHardy
2005-02-19 18:32                   ` Herbert Xu
2005-02-19 18:47                     ` Patrick McHardy
2005-02-19 19:03                       ` Herbert Xu
2005-02-19 19:53                         ` Patrick McHardy
2005-02-19 20:26                           ` Patrick McHardy
2005-02-20  6:57                             ` Herbert Xu
2005-03-18  4:32                 ` David S. Miller [this message]
2005-03-18  6:24                   ` Herbert Xu
2005-03-20 15:51                   ` Patrick McHardy
2005-03-20 20:38                     ` Herbert Xu
2005-03-23  2:28                       ` Patrick McHardy

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=20050317203231.1b649f60.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=kaber@trash.net \
    --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).