From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 8 06:27:35 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 3ED7416A41F; Thu, 8 Dec 2005 06:27:35 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D48343D83; Thu, 8 Dec 2005 06:27:30 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=ganbold.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.53 (FreeBSD)) id 1EkFLK-000DKK-6K; Thu, 08 Dec 2005 14:33:26 +0800 Message-Id: <7.0.0.16.0.20051208141829.035d73a8@micom.mng.net> X-Mailer: QUALCOMM Windows Eudora Version 7.0.0.16 Date: Thu, 08 Dec 2005 14:27:18 +0800 To: freebsd-amd64@freebsd.org From: Ganbold Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: andre@freebsd.org, rwatson@FreeBSD.org Subject: 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 06:27:35 -0000 Hi, 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? thanks, Ganbold I didn't put yet additional 4GB RAM. I will try it later.