Re: tcp over slow links broken?

From: Bakul Shah <bakul_at_bitblocks.com>
Date: Sun, 11 May 2008 00:07:08 -0700
On Sat, 10 May 2008 23:33:56 PDT Julian Elischer <julian_at_elischer.org>  wrote:
> Bakul Shah wrote:
> > 14:22:42.317406 IP B.55535 > C.ssh: . 4744:6204(1460) ack 2016 win 65535
> > 14:22:42.317489 IP B.55535 > C.ssh: . 6204:7664(1460) ack 2016 win 65535
> > 14:22:42.410739 IP C.ssh > B.55535: . ack 4744 win 64240
> > 14:22:42.411144 IP B.55535 > C.ssh: . 7664:9124(1460) ack 2016 win 65535
> > 14:22:42.411259 IP B.55535 > C.ssh: . 9124:10584(1460) ack 2016 win 65535
> > 14:22:42.468350 IP C.ssh > B.55535: . ack 4744 win 65535
> > 14:22:42.490556 IP C.ssh > B.55535: . ack 4744 win 65535
> 
> that is just plain  wierd...  B seems to have gone deaf.

Yup! As if the wrong segment is being queued up.

> have you made a kernel from each side of that commit and compared them?

That is next on my list.  I have been looking at the changes.
Most of the changes in that commit seem to be of the kind
    s/INP_LOCK/INP_WLOCK/
    s/INP_UNLOCK/INP_WUNLOCK/
so that is probably not it (I mentioned it mainly because I
found the comment amusing).
Received on Sun May 11 2008 - 05:07:10 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:30 UTC