From owner-freebsd-current Thu Mar 30 3:55: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (wandering-wizard.cybercity.dk [212.242.43.150]) by hub.freebsd.org (Postfix) with ESMTP id E4FBC37B70B; Thu, 30 Mar 2000 03:55:05 -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 NAA01276; Thu, 30 Mar 2000 13:37:32 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bruce Evans Cc: Mike Smith , Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: SMP buildworld times / performance tests In-reply-to: Your message of "Thu, 30 Mar 2000 21:24:28 +1000." Date: Thu, 30 Mar 2000 13:37:32 +0200 Message-ID: <1274.954416252@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Bruce Ev ans writes: >On Wed, 29 Mar 2000, Mike Smith wrote: > >> Just following on from this, one thing that I can see immediately being >> very important to me at least is a spinlock in the timecounter structure. >> Calcru and various other things call microtime(), and we're going to want >> to lock out updates and parallel accesses to the timecounter. What >> should we be using for an interrupt-disabling spinlock? > >Nothing. Accesses to the timecounter struct are already MP safe and fast. >Only the i8254 timecounter hardware currently needs interrupt-disabling, >but it is hopefully never used on SMP machines. Worse. It is used by default on SMP machines which don't sport the PIIX timecounter. -- 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