From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] proc.c
Date: Fri, 3 May 2002 20:05:37 +0100 [thread overview]
Message-ID: <35757b878c871c14ab946e9318e58d99@caldo.demon.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 139 bytes --]
silly question. i'd overlooked that it was always the same element of the runq array
that was locked even though there's one per level.
[-- Attachment #2: Type: message/rfc822, Size: 2974 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 10 bytes --]
Lock runq;
[-- Attachment #2.1.2: Type: message/rfc822, Size: 1364 bytes --]
From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: [9fans] proc.c
Date: Fri, 3 May 2002 17:45:43 +0100
Message-ID: <ba4fe407f4ca01067f5a3730a662abb4@caldo.demon.co.uk>
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?
next reply other threads:[~2002-05-03 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-03 19:05 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-03 18:45 presotto
2002-05-03 16:45 forsyth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=35757b878c871c14ab946e9318e58d99@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).