From owner-freebsd-net@FreeBSD.ORG Fri Jul 3 12:28:23 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A12610656B7; Fri, 3 Jul 2009 12:28:23 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lauren.room52.net (lauren.room52.net [210.50.193.198]) by mx1.freebsd.org (Postfix) with ESMTP id 72F2E8FC29; Fri, 3 Jul 2009 12:28:22 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lstewart-laptop.caia.swin.edu.au (host86-150-124-14.range86-150.btcentralplus.com [86.150.124.14]) (authenticated bits=0) by lauren.room52.net (8.14.3/8.14.3) with ESMTP id n63BpYFT090817 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Jul 2009 21:51:37 +1000 (EST) (envelope-from lstewart@freebsd.org) Message-ID: <4A4DF0BC.6090207@freebsd.org> Date: Fri, 03 Jul 2009 12:51:24 +0100 From: Lawrence Stewart User-Agent: Thunderbird 2.0.0.22 (X11/20090626) MIME-Version: 1.0 To: Qing Li References: <20090505160145.8C8F18FC15@mx1.freebsd.org> In-Reply-To: <20090505160145.8C8F18FC15@mx1.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.5 required=5.0 tests=AWL,BAYES_20,RCVD_IN_PBL, RDNS_DYNAMIC,SPF_SOFTFAIL autolearn=disabled version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on lauren.room52.net Cc: freebsd-net@freebsd.org, qingli@freebsd.org Subject: Re: Slow local TCP transfers on -CURRENT X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jul 2009 12:28:23 -0000 Hi Qing, Qing Li wrote: >> Qing (added to CC) is aware of the problem. Not sure how far >> off the fix is. >> > > I am resuming the work on it, hoping to get it verified and > finalized in a day or so. Sorry about the delay. Did this ever get fixed? I don't think I saw a follow up to this thread so just thought I'd check. Cheers, Lawrence