Date: Thu, 15 Nov 2001 12:01:50 -0800 (PST)
From: John Baldwin <jhb@FreeBSD.org>
To: Dag-Erling Smorgrav <des@ofug.org>
Cc: Robert Watson <rwatson@FreeBSD.ORG>, Matthew Dillon <dillon@apollo.backplane.com>, Alfred Perlstein <bright@mu.org>, Greg Lehey <grog@FreeBSD.ORG>, Bruce Evans <bde@zeta.org.au>, Peter Wemm <peter@wemm.org>, freebsd-arch@FreeBSD.ORG
Subject: Re: cur{thread/proc}, or not.
Message-ID: <XFMail.011115120150.jhb@FreeBSD.org>
In-Reply-To: <xzpbsi36ccs.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On 15-Nov-01 Dag-Erling Smorgrav wrote: > 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? Only for certain things. We don't actually lock the process unless we need to down inside of a syscall. > DES > -- > Dag-Erling Smorgrav - des@ofug.org -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "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.011115120150.jhb>