Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264280AbTKZSkO (ORCPT ); Wed, 26 Nov 2003 13:40:14 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264281AbTKZSkO (ORCPT ); Wed, 26 Nov 2003 13:40:14 -0500 Received: from mailer2.psc.edu ([128.182.66.106]:55272 "EHLO mailer2.psc.edu") by vger.kernel.org with ESMTP id S264280AbTKZSkJ (ORCPT ); Wed, 26 Nov 2003 13:40:09 -0500 Date: Wed, 26 Nov 2003 13:39:54 -0500 (EST) From: John Heffner To: Yogesh Swami cc: Subject: Re: Linux TCP state machine is broken? In-Reply-To: <20031126175304.42296.qmail@web80502.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1086 Lines: 29 On Wed, 26 Nov 2003, Yogesh Swami wrote: > I think the reason the sender is always in TCP_CA_CWR > and not in TCP_CA_Open is because in the function > "tcp_transmit_skb" (tcp_out.c:190), after sending the > packet to IP-layer, the sender call tcp_enter_cwr() if > the IP layer did not return any non congestion error. > I have put the code fragement at the end of the > e-mail. > > I am not clear why a successfuly transmission should > cause the sender to enter CWR (the only other places > when tcp_enter_cwr is called are when there is a ICMP > source quench or when there is ECE bit set for ECN). > > If someone could explain this to me, that would be > great. It reaches this point if there *is* congestion explicitly reported by the interface. It will be in CWR a lot of the time if your local interface is the bottleneck. -John - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/