From owner-freebsd-current@FreeBSD.ORG Sun Jul 30 00:53:43 2006 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 D729816A4DA for ; Sun, 30 Jul 2006 00:53:43 +0000 (UTC) (envelope-from jd@ugcs.caltech.edu) Received: from groat.ugcs.caltech.edu (groat.ugcs.caltech.edu [131.215.176.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F4AD43D46 for ; Sun, 30 Jul 2006 00:53:43 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by groat.ugcs.caltech.edu (Postfix, from userid 3640) id 508CB5880B; Sat, 29 Jul 2006 17:53:42 -0700 (PDT) Date: Sat, 29 Jul 2006 17:53:42 -0700 From: Paul Allen To: Michal Mertl Message-ID: <20060730005342.GJ12597@groat.ugcs.caltech.edu> References: <200607280928.36573.jhb@freebsd.org> <20060728134701.GA45273@uk.tiscali.com> <20060728210154.GC748@turion.vk2pj.dyndns.org> <1154189612.1565.10.camel@genius.i.cz> <20060729205655.GE748@turion.vk2pj.dyndns.org> <20060729211530.GA50342@uk.tiscali.com> <1154212340.3609.18.camel@genius.i.cz> <20060729230214.GI12597@groat.ugcs.caltech.edu> <1154216319.23616.23.camel@genius.i.cz> <1154217036.23616.28.camel@genius.i.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1154217036.23616.28.camel@genius.i.cz> Sender: jd@ugcs.caltech.edu Cc: Peter Jeremy , Paul Allen , Brian Candler , freebsd-current@freebsd.org Subject: Re: vmstat's entries type 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: Sun, 30 Jul 2006 00:53:43 -0000 >From Michal Mertl , Sun, Jul 30, 2006 at 01:50:36AM +0200: > Michal Mertl wrote: > > Paul Allen wrote: > > > Surely all you need to do is a cheap crit_enter,crit_exit > > > while updating the 64-bit per cpu counters. and on > > > a 64-bit arch you skip the crit_enter,crit_exit. > > > > Critical_enter/exit seem to be quite lightweight (single > > read/modify/write of a variable). > > One more question. Why do you say that crit_* can be avoided on 64-bit > arch? If the reason was that "increment of a 64 bit number is one > operation there" it probably is not true - as somebody already stated, > some instruction sets don't allow atomic increment of a memory location. > > Michal Which FreeBSD tier-I 64b arch do you have in mind... > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"