From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 8 07:10:22 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E59B16A420; Thu, 8 Dec 2005 07:10:22 +0000 (GMT) (envelope-from rwatso@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F2D643D5A; Thu, 8 Dec 2005 07:10:12 +0000 (GMT) (envelope-from rwatso@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 2C50B46B9C; Thu, 8 Dec 2005 02:10:12 -0500 (EST) Date: Thu, 8 Dec 2005 07:10:12 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Ganbold In-Reply-To: <7.0.0.16.0.20051208141829.035d73a8@micom.mng.net> Message-ID: <20051208070431.K89534@fledge.watson.org> References: <7.0.0.16.0.20051208141829.035d73a8@micom.mng.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: andre@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: tcp.sack and debug.mpsafenet in FreeBSD 6.0/AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 07:10:22 -0000 On Thu, 8 Dec 2005, Ganbold wrote: > I just upgraded FreeBSD 5.3-STABLE/AMD64 successfully to FreeBSD > 6.0-STABLE/AMD64. I was using debug.mpsafenet=0 and > net.inet.tcp.sack.enable=0 with 5.3/AMD64 due to TCP SACK/MPSAFENET bug. Is > it safe to enable these in 6.0 now? I can't speak to the specifics of your confiugration and situation, but can say that a number of significant bugs in the TCP and socket code have been fixed since 5.3-RELEASE. If any problems with networking do persiste for you in RELENG_6, please let me know. Robert N M Watson