From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 12:24:41 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C155637B401 for ; Thu, 3 Jul 2003 12:24:41 -0700 (PDT) Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.86.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEDBC44035 for ; Thu, 3 Jul 2003 12:24:40 -0700 (PDT) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (port757.uc1-esp.isdn-lan.cybercity.dk [212.242.98.245]) by phk.freebsd.dk (8.12.8/8.12.8) with ESMTP id h63JObV3027300 for ; Thu, 3 Jul 2003 19:24:38 GMT (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h63JOblC006476 for ; Thu, 3 Jul 2003 21:24:37 +0200 (CEST) (envelope-from phk@phk.freebsd.dk) To: current@freebsd.org From: Poul-Henning Kamp Date: Thu, 03 Jul 2003 21:24:36 +0200 Message-ID: <6475.1057260276@critter.freebsd.dk> Subject: Does newreno work as designed ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Thu, 03 Jul 2003 19:24:42 -0000 I'm sitting on a ISDN line right now, and I thought the newreno issues had been solved, but by disabling newreno I get a distinctly better web-surfing experience. Is newreno working as designed right now, and if not, who is fixing it ? -- 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.