Date: Mon, 12 Nov 2001 16:26:27 -0800 (PST)
From: John Baldwin <jhb@FreeBSD.org>
To: John Baldwin <jhb@FreeBSD.org>
Cc: Terry Lambert <tlambert2@mindspring.com>, Robert Watson <rwatson@FreeBSD.ORG>, freebsd-arch@FreeBSD.ORG, Matthew Dillon <dillon@apollo.backplane.com>
Subject: Re: cur{thread/proc}, or not.
Message-ID: <XFMail.011112162627.jhb@FreeBSD.org>
In-Reply-To: <XFMail.011112162428.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <jhb@FreeBSD.org> -- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.011112162627.jhb>