From owner-freebsd-arch Mon Nov 12 16:26:45 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by hub.freebsd.org (Postfix) with ESMTP id 6667D37B419 for ; Mon, 12 Nov 2001 16:26:33 -0800 (PST) Received: (qmail 4112 invoked from network); 13 Nov 2001 00:26:32 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 13 Nov 2001 00:26:32 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 12 Nov 2001 16:26:27 -0800 (PST) From: John Baldwin To: John Baldwin Subject: Re: cur{thread/proc}, or not. Cc: Terry Lambert , Cc: Terry Lambert , Robert Watson , freebsd-arch@FreeBSD.ORG, Matthew Dillon 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 On 13-Nov-01 John Baldwin wrote: > Then if a structure (like lockmgr locks or sx locks) wants to cache the lock > pointer instead of doing the hash all the time, it can just do > > foo->f_lock = mtx_pool_find(foo); > > This actually isn't all that difficult, it just adds the ability to lookup > and > cache the mutex associated with an address. I would also like it under mtx_* > so it's clear what type of locks are in the pool, but that's just me. :) s/difficult/different/ It's not difficult either, but that wasn't my point. :) -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message