From owner-freebsd-current Mon Jul 12 9:55:47 1999 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 A43D415059 for ; Mon, 12 Jul 1999 09:55:28 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id SAA20138; Mon, 12 Jul 1999 18:52:02 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Luoqi Chen , dfr@nlsystems.com, jeremyp@gsmx07.alcatel.com.au, freebsd-current@FreeBSD.ORG, mike@ducky.net Subject: Re: "objtrm" problem probably found (was Re: Stuck in "objtrm") In-reply-to: Your message of "Mon, 12 Jul 1999 09:47:11 PDT." <199907121647.JAA70249@apollo.backplane.com> Date: Mon, 12 Jul 1999 18:52:02 +0200 Message-ID: <20136.931798322@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > p.s. I'm pretty sure that the lock prefix costs nothing on a UP system, > and probably wouldn't be noticed on an SMP system either because the > write-allocation overhead is already pretty bad. But I haven't tested > it. it's actually quite expensive in terms of bus bandwidth because a lot of things have to be synchronized and stalled... -- 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