From owner-cvs-all  Mon Feb 25 11:47:11 2002
Delivered-To: cvs-all@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id AC27C37B400; Mon, 25 Feb 2002 11:47:05 -0800 (PST)
Received: (from rwatson@localhost)
	by freefall.freebsd.org (8.11.6/8.11.6) id g1PJl5d30130;
	Mon, 25 Feb 2002 11:47:05 -0800 (PST)
	(envelope-from rwatson)
Message-Id: <200202251947.g1PJl5d30130@freefall.freebsd.org>
From: Robert Watson <rwatson@FreeBSD.org>
Date: Mon, 25 Feb 2002 11:47:05 -0800 (PST)
To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: cvs commit: www/en/smp index.sgml
X-FreeBSD-CVS-Branch: HEAD
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk
List-ID: <cvs-all.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20cvs-all>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20cvs-all>
X-Loop: FreeBSD.ORG

rwatson     2002/02/25 11:47:05 PST

  Modified files:
    en/smp               index.sgml 
  Log:
  Add a lock contention measuring tool to the list of desirable features
  without an owner.  To measure the effectiveness of our locking strategy,
  optimality of mutex pools, etc, we'll need a tool that tells us what
  locks are the "hottest", as well as other useful statistics such as
  average latency to wait on a lock, perhaps throughput on the lock, etc.
  This task will require some relatively in-depth analysis of what we need
  to know, not just hacking, but should prove interesting and highly
  valuable.
  
  Revision  Changes    Path
  1.22      +10 -1     www/en/smp/index.sgml

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message