From owner-freebsd-current@FreeBSD.ORG Fri Oct 14 09:10:12 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A11F16A41F for ; Fri, 14 Oct 2005 09:10:12 +0000 (GMT) (envelope-from discussion-lists@linnet.org) Received: from orb.pobox.com (orb.pobox.com [207.8.226.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABE9643D46 for ; Fri, 14 Oct 2005 09:10:11 +0000 (GMT) (envelope-from discussion-lists@linnet.org) Received: from orb (localhost [127.0.0.1]) by orb.pobox.com (Postfix) with ESMTP id 12F3721EB; Fri, 14 Oct 2005 05:10:34 -0400 (EDT) Received: from mappit.local.linnet.org (212-74-113-67.static.dsl.as9105.com [212.74.113.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by orb.sasl.smtp.pobox.com (Postfix) with ESMTP id A65F08A; Fri, 14 Oct 2005 05:10:30 -0400 (EDT) Received: from lists by mappit.local.linnet.org with local (Exim 4.54 (FreeBSD)) id 1EQLZk-0004pw-OQ; Fri, 14 Oct 2005 10:10:04 +0100 Date: Fri, 14 Oct 2005 10:10:04 +0100 From: Brian Candler To: Brooks Davis Message-ID: <20051014091004.GC18513@uk.tiscali.com> References: <434E46C0.7060903@centtech.com> <200510131412.23525.max@love2party.net> <20051013181026.GB27418@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051013181026.GB27418@odin.ac.hmc.edu> User-Agent: Mutt/1.4.2.1i Cc: Max Laier , freebsd-current@freebsd.org, Eric Anderson Subject: Re: ufsstat - testers / feedback wanted! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Oct 2005 09:10:12 -0000 On Thu, Oct 13, 2005 at 11:10:26AM -0700, Brooks Davis wrote: > > I don't think you can measure one single interger (or 64bit) increase in face > > of a operation that has to access backing store. Even if there is a > > performance hit, you don't have to build your kernel with the option enabled. > > The one thing I'd be worried about here is that 64bit updates are > expensive on 32bit machines if you want them to be atomic. Relative to > backing store they probably still don't matter, but the might be > noticable. I'd be grateful if you could clarify that point for me. Are you saying that if I write long long foo; ... foo++; then the C compiler generates code for 'foo++' which is not thread-safe? (And therefore I would have to protect it with a mutex or critical section) Or are you saying that the C compiler inserts its own code around foo++ to turn it into a critical section, and therefore runs less efficiently than you'd expect? Regards, Brian.