From owner-freebsd-current Mon Jun 19 18: 1:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id 89D0637B76C for ; Mon, 19 Jun 2000 18:01:34 -0700 (PDT) (envelope-from jasone@magnesium.net) Received: (qmail 46460 invoked by uid 1142); 20 Jun 2000 01:01:33 -0000 Date: 19 Jun 2000 18:01:33 -0700 Date: Mon, 19 Jun 2000 18:01:14 -0700 From: Jason Evans To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: SMP locking primities (was Re: HEADS UP: Destabilization due to SMP development) Message-ID: <20000619180113.G79318@blitz.canonware.com> References: <20000619115330.D79318@blitz.canonware.com> <200006200034.RAA81825@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200006200034.RAA81825@apollo.backplane.com>; from dillon@apollo.backplane.com on Mon, Jun 19, 2000 at 05:34:47PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jun 19, 2000 at 05:34:47PM -0700, Matthew Dillon wrote: > Ok, I have put up a web page that will track my efforts. > > http://apollo.backplane.com/FreeBSDSmp/ On this page, you say: The algorithms described on this page are essentially the BSDI algorithms plus accomodations we disussed at the Yahoo SMP meeting. However, I did not do a direct port. I did a from-scratch rewrite because, simply put, it was easier for me. The variables are named differently but I attempt to follow the same API. All the work is subject to change... the point is to make it work first, then clean it up later. Does this include the locking primitives? In the case of the locking primitives, there is functionality that we definitely need, such as the witness code, and it probably would save effort to use the BSD/OS code. I'm guessing that you are actually using the BSD/OS code in this case; I'm just looking for clarification. Thanks, Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message