From owner-cvs-all Tue Jan 2 0:31:51 2001 From owner-cvs-all@FreeBSD.ORG Tue Jan 2 00:31:48 2001 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from warning.follo.net (warning.follo.net [195.204.136.30]) by hub.freebsd.org (Postfix) with ESMTP id 1392437B400; Tue, 2 Jan 2001 00:31:47 -0800 (PST) Received: (from eivind@localhost) by warning.follo.net (8.9.3/8.9.3) id JAA55248; Tue, 2 Jan 2001 09:29:42 +0100 (CET) Date: Tue, 2 Jan 2001 09:29:41 +0100 From: Eivind Eklund To: Mark Murray Cc: John Baldwin , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/alpha/alpha sys_machdep.c vm_machdep.c s Message-ID: <20010102092941.A55120@warning.follo.net> References: <200012251608.eBPG80F06877@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200012251608.eBPG80F06877@gratis.grondar.za>; from mark@grondar.za on Mon, Dec 25, 2000 at 06:07:49PM +0200 Sender: eivind@warning.follo.net Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 25, 2000 at 06:07:49PM +0200, Mark Murray wrote: > > > Cool! How many of these data structures are there needing lockdown? > > > > Every data structure in the kernel needs some kind of lock. Now, a > > lock can protect several related structures, or you might use one lock > > to protect all data structures of a given type (rather than one lock > > for each struct), but they all have to be locked by something. So the > > answer is "the number of data structures in the kernel." Finding this > > is left as an exercise to the reader. > > :) > > Ouch! > > > I have no idea. I would have to have all of hte kernel memorized to know all > > of its data structures. :) > > > Hmm. Then surely some kind of formalised process would be necessary to > ascertain which structures are local and which are needed elsewhere? > (The intent being to discover how far reaching each lock should be). > > > Like if someone (I would not be adverse) were to go through the kernel > and staticise-where-possible? > > Apart from localising those data structures that need to be locked, it > would also reduce namespace suggestion. > > I've got access to (commercial) tools to do this, and have done a run before - I'll try to get around to doing another one. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message