From owner-freebsd-current Thu Mar 30 3:25: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 2416F37C0D4; Thu, 30 Mar 2000 03:24:53 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id VAA09454; Thu, 30 Mar 2000 21:30:04 +1000 Date: Thu, 30 Mar 2000 21:24:28 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Mike Smith Cc: Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: SMP buildworld times / performance tests In-Reply-To: <200003300038.QAA08006@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message