From owner-freebsd-arch  Thu Nov 30  5:44:41 2000
Delivered-To: freebsd-arch@freebsd.org
Received: from berserker.bsdi.com (berserker.twistedbit.com [199.79.183.1])
	by hub.freebsd.org (Postfix) with ESMTP id 6B7AA37B401
	for <arch@FreeBSD.ORG>; Thu, 30 Nov 2000 05:44:39 -0800 (PST)
Received: from berserker.bsdi.com (cp@localhost.bsdi.com [127.0.0.1])
	by berserker.bsdi.com (8.11.1/8.9.3) with ESMTP id eAUDiTv03105;
	Thu, 30 Nov 2000 06:44:29 -0700 (MST)
	(envelope-from cp@berserker.bsdi.com)
Message-Id: <200011301344.eAUDiTv03105@berserker.bsdi.com>
To: Alfred Perlstein <bright@wintelcom.net>
Cc: arch@FreeBSD.ORG
Subject: Re: serious problem with mutexs and userland visibility? 
In-reply-to: Your message of "Wed, 29 Nov 2000 12:55:09 PST."
             <20001129125508.O8051@fw.wintelcom.net> 
From: Chuck Paterson <cp@bsdi.com>
Date: Thu, 30 Nov 2000 06:44:29 -0700
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

You might want to look at how the lock manager deals with
mutices. This same approach ought to work for the cred stuff which
has a lower usage rate that the lock manager, and you can adjust
you level of lock sharing.


Chuck


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