From owner-freebsd-arch Mon Apr 1 8:47:58 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 6A88937B419; Mon, 1 Apr 2002 08:47:49 -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 g31GlO4F018326; Mon, 1 Apr 2002 18:47:24 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Eivind Eklund Cc: Dag-Erling Smorgrav , "Andrew R. Reiter" , "Greg 'groggy' Lehey" , arch@FreeBSD.ORG Subject: Re: mutex profiling In-Reply-To: Your message of "Mon, 01 Apr 2002 18:41:58 +0200." <20020401184158.A15491@phoenix.dmnshq.net> Date: Mon, 01 Apr 2002 18:47:24 +0200 Message-ID: <18325.1017679644@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 In message <20020401184158.A15491@phoenix.dmnshq.net>, Eivind Eklund writes: >On Mon, Apr 01, 2002 at 06:31:31PM +0200, Dag-Erling Smorgrav wrote: >> "Andrew R. Reiter" writes: >> > Can we perhaps have the ability to dump the lock char * description? Or >> > are you doing this way b/c you can get the file and line #'s? Looks good, >> > tho. >> >> I can get both; I'm doing it this way because Eivind did it this way >> and it didn't occur to me to change it. Is one preferrable to the >> other? > >The use of filename/line combinations was done to be able to find what actual >lock aquisitions result in introduction of large amounts of latency. The >basic reason I wrote this patch was to be able to find what parts of our code >result in latency, to focus effort there. > >Measuring the lock types themselves (which is what the lock description would >give you) give a much less granular set of information. This accumulation can >(non-trivially) be done separately, but if you do the accumulation, it is not >possible to recover the information about where the latency is introduced. I think you misunderstood, I think the request was to get the lock name in addition to the file/line info. -- 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