From owner-freebsd-current@FreeBSD.ORG Sat Sep 4 09:50:01 2004 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 E562C16A4CF; Sat, 4 Sep 2004 09:50:01 +0000 (GMT) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [210.226.20.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 414CE43D53; Sat, 4 Sep 2004 09:50:01 +0000 (GMT) (envelope-from kuriyama@imgsrc.co.jp) Received: from localhost (localhost [127.0.0.1]) by black.imgsrc.co.jp (Postfix) with ESMTP id 5111B50B9A; Sat, 4 Sep 2004 18:49:59 +0900 (JST) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [IPv6:2001:218:422:2::9999]) by black.imgsrc.co.jp (Postfix) with ESMTP id B772050B95; Sat, 4 Sep 2004 18:49:57 +0900 (JST) Date: Sat, 04 Sep 2004 18:49:57 +0900 Message-ID: <7mbrgmwegq.wl@black.imgsrc.co.jp> From: Jun Kuriyama To: Robert Watson In-Reply-To: References: <20040903104015.GA1889@nemesis.md.0xfce3.net> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.6 (Maruoka) FLIM/1.14.6 (Marutamachi) APEL/10.6 Emacs/21.3 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd 0.1 cc: freebsd-current@freebsd.org Subject: Re: cvs commit: src/sys/conf options src/sys/sys kernel.h src/sys/net netisr.c 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: Sat, 04 Sep 2004 09:50:02 -0000 At Fri, 3 Sep 2004 07:31:23 -0400 (EDT), Robert Watson wrote: > Regarding IPv6: significant parts of IPv6 are safe in an MPSAFE > environment, but not very well tested -- I've had about three or four > minor but significant (fail stop) bugs to correct in the last two weeks. > I don't doubt more are waiting. Areas that still require substantial > attention in locking include the IPv6 forwarding path, ip6fw, and > multicast discovery/routing. If you're using IPv6 on a local system > largely for services like TCP consumption and serving, you are probably > OK, but might encounter fail stop (assertion failure) scenarios that > require some debugging. So far, these problems have generally been > resolved within 48 hours of the problem being reported. > > So if you're willing to do a bit of testing, MPSAFE operation is probably > ready for you, and additional IPv6 testing is something I'd like to see > more of, as I don't have easy access to a rich IPv6 environment. Nice to hear. I'll start testing with mpsafenet=1 with usual workload from Monday (sitting at console). # I don't care if my box panics. :-) -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project