From owner-freebsd-arch Sun Mar 31 14:13:18 2002 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 682E837B41B for ; Sun, 31 Mar 2002 14:13:15 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g2VMCoe7029647; Mon, 1 Apr 2002 00:12:50 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Dag-Erling Smorgrav Cc: arch@FreeBSD.ORG Subject: Re: mutex profiling In-Reply-To: Your message of "01 Apr 2002 00:07:18 +0200." Date: Mon, 01 Apr 2002 00:12:50 +0200 Message-ID: <29646.1017612770@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG With the footnote that the TSC's are not synchronized on SMP systems, this looks like a nice initial tool to get some kind of picture of the locking situation in the kernel. Poul-Henning In message , Dag-Erling Smorgrav writes: >--=-=-= > >The attached patch (derived from patches by Eivind) adds code to >record statistics about MTX_DEF locks. It's currently i386-only as it >uses the TSC to measure the amount of time each mutex is held. Once -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message