From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <66e41ec29dc2fbbb5ea622fec600451d@plan9.bell-labs.com>
From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] proc.c
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="upas-jaridrlnywwphhkfoqsdpchtjt"
Date: Fri,  3 May 2002 14:45:41 -0400
Topicbox-Message-UUID: 87c3cf12-eaca-11e9-9e20-41e7f4b1d025

This is a multi-part message in MIME format.
--upas-jaridrlnywwphhkfoqsdpchtjt
Content-Disposition: inline
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Lock runq;
--upas-jaridrlnywwphhkfoqsdpchtjt
Content-Type: message/rfc822
Content-Disposition: inline

Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Fri May  3 12:52:14 EDT 2002
Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Fri May  3 12:52:13 EDT 2002
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.8.6])
	by mail.cse.psu.edu (CSE Mail Server) with ESMTP
	id C257F19A7B; Fri,  3 May 2002 12:52:06 -0400 (EDT)
Delivered-To: 9fans@cse.psu.edu
Received: from lavoro.home.cs.york.ac.uk (public1-york1-5-cust17.leed.broadband.ntl.com [80.0.45.17])
	by mail.cse.psu.edu (CSE Mail Server) with SMTP id 296AA19A77
	for <9fans@cse.psu.edu>; Fri,  3 May 2002 12:51:32 -0400 (EDT)
Message-ID: <ba4fe407f4ca01067f5a3730a662abb4@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
From: forsyth@caldo.demon.co.uk
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: [9fans] proc.c
Sender: 9fans-admin@cse.psu.edu
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0.9
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive: <https://lists.cse.psu.edu/archives/9fans/>
Date: Fri, 3 May 2002 17:45:43 +0100

i must be missing something.  i've wondered
which lock protects nrdy in /sys/src/9/port/proc.c
on a multiprocessor, and if it doesn't matter, why not?

--upas-jaridrlnywwphhkfoqsdpchtjt--