From owner-freebsd-current Tue Jun 25 8:54:15 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 2678637B401 for ; Tue, 25 Jun 2002 08:54:11 -0700 (PDT) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.3/8.12.2) with ESMTP id g5PFqDCn001505 for ; Tue, 25 Jun 2002 17:52:13 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: is newreno still sick ? From: Poul-Henning Kamp Date: Tue, 25 Jun 2002 17:52:13 +0200 Message-ID: <1503.1025020333@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On my -current laptop, and my other -current and -stable machines, TCP seems to work a lot better if I disable net.inet.tcp.newreno. Has anybody else seen similar behaviour ? Who owns this problem ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message