From owner-freebsd-current Thu Nov 2 13:10: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (fw2.aub.dk [195.24.1.195]) by hub.freebsd.org (Postfix) with ESMTP id B299037B4C5 for ; Thu, 2 Nov 2000 13:09:55 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.9.3) with ESMTP id eA2L9ch00296 for ; Thu, 2 Nov 2000 22:09:49 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: disabling tcp.newreno in 72 hours... From: Poul-Henning Kamp Date: Thu, 02 Nov 2000 22:09:38 +0100 Message-ID: <294.973199378@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We have several people who report that tcp.newreno seriously hurts their network performance and Yan doesn't seem to have time to fix it. Unless there are compelling reasons to not do so presented in the next 72 hours I will change the kernel default from newreno enabled to newreno disabled. Anybody interested in studying the problem can find two packet captures at: http://phk.freebsd.dk/newreno -- 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