Date: 15 Nov 2001 20:52:19 +0100
From: Dag-Erling Smorgrav <des@ofug.org>
To: John Baldwin <jhb@FreeBSD.org>
Cc: freebsd-arch@FreeBSD.ORG, Peter Wemm <peter@wemm.org>, Bruce Evans <bde@zeta.org.au>, Greg Lehey <grog@FreeBSD.ORG>, Alfred Perlstein <bright@mu.org>, Matthew Dillon <dillon@apollo.backplane.com>, Robert Watson <rwatson@FreeBSD.ORG>
Subject: Re: cur{thread/proc}, or not.
Message-ID: <xzpbsi36ccs.fsf@flood.ping.uio.no>
In-Reply-To: <XFMail.011115112856.jhb@FreeBSD.org>
References: <XFMail.011115112856.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin <jhb@FreeBSD.org> writes: > Err, no. curthread doesn't even have a lock. Look at sys/proc.h. There are > some fields we don't use any locks on, because we assume that only curthread > messes with its own copy, or some such. Hmm, then you need to lock the entire process, don't you? DES -- Dag-Erling Smorgrav - des@ofug.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?xzpbsi36ccs.fsf>