From owner-freebsd-current Fri Mar 31 0:51:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id CCBD237B637; Fri, 31 Mar 2000 00:51:45 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id KAA01801; Fri, 31 Mar 2000 10:50:12 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Bruce Evans , Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: SMP buildworld times / performance tests In-reply-to: Your message of "Thu, 30 Mar 2000 09:15:54 -0800." <200003301715.JAA73702@apollo.backplane.com> Date: Fri, 31 Mar 2000 10:50:12 +0200 Message-ID: <1799.954492612@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003301715.JAA73702@apollo.backplane.com>, Matthew Dillon writes: > The general problem with the timecounter is that not only is the hardware > indeterminant, but the timecounter structure itself is *NOT* MP safe, > at least not by my read of it. Well, read again then :-) I've had a paper in the works about timecounters for over a year now, I should really sit down and finish it. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message