On Sat, 19 Feb 2005 20:23:14 +1100
Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> 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?
|