From owner-freebsd-current@FreeBSD.ORG Sun May 11 07:07:10 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2CC3A1065676 for ; Sun, 11 May 2008 07:07:10 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from mail.bitblocks.com (mail.bitblocks.com [64.142.15.60]) by mx1.freebsd.org (Postfix) with ESMTP id F167A8FC1D for ; Sun, 11 May 2008 07:07:09 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (localhost.bitblocks.com [127.0.0.1]) by mail.bitblocks.com (Postfix) with ESMTP id A1AF05B4D; Sun, 11 May 2008 00:07:08 -0700 (PDT) To: Julian Elischer In-reply-to: Your message of "Sat, 10 May 2008 23:33:56 PDT." <48269354.80009@elischer.org> Date: Sun, 11 May 2008 00:07:08 -0700 From: Bakul Shah Message-Id: <20080511070708.A1AF05B4D@mail.bitblocks.com> Cc: freebsd-current@freebsd.org Subject: Re: tcp over slow links broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 May 2008 07:07:10 -0000 On Sat, 10 May 2008 23:33:56 PDT Julian Elischer 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).