From owner-freebsd-arch  Tue Oct  3 13:10:20 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 E0C0E37B66C; Tue,  3 Oct 2000 13:10:17 -0700 (PDT)
Received: from berserker.bsdi.com (cp@LOCALHOST [127.0.0.1])
	by berserker.bsdi.com (8.9.3/8.9.3) with ESMTP id OAA13053;
	Tue, 3 Oct 2000 14:10:14 -0600 (MDT)
Message-Id: <200010032010.OAA13053@berserker.bsdi.com>
Cc: Alfred Perlstein <bright@wintelcom.net>,
	John Baldwin <jhb@freebsd.org>, arch@freebsd.org,
	John Polstra <jdp@polstra.com>, Daniel Eischen <eischen@vigrid.com>,
	Matt Dillon <dillon@earth.backplane.com>, Greg Lehey <grog@lemis.com>
Subject: Re: Mutexes and semaphores 
In-reply-to: Your message of "Tue, 03 Oct 2000 14:01:02 MDT."
             <200010032001.OAA12968@berserker.bsdi.com> 
From: Chuck Paterson <cp@bsdi.com>
Date: Tue, 03 Oct 2000 14:10:14 -0600
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Alfred:

More on sys_getppid

You could arrange for the fault handler to do the "right thing"
when you faulted in this case. This could all be done without
any locks since it is process private data. This might be a useful
feature in general.

Chuck



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