From: "boyd, rounin" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] cc linux clusters
Date: Fri, 14 Nov 2003 01:45:59 +0100 [thread overview]
Message-ID: <059701c3aa55$ed14a0c0$b9844051@insultant.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0311130742460.32319-100000@maxroach.lanl.gov>
> LM knows a thing or two about this, having spent years in both the sunos,
> and irix trenches.
i am not convinced; 'coarse' vs ''fine' grained locking is nonsense.
if you are gonna lock stuff a) think about it b) do it right.
but you knew that.
next parent reply other threads:[~2003-11-14 0:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0311130742460.32319-100000@maxroach.lanl.gov>
2003-11-14 0:45 ` boyd, rounin [this message]
2003-11-13 4:16 Scott Schwartz
2003-11-13 4:27 ` boyd, rounin
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='059701c3aa55$ed14a0c0$b9844051@insultant.net' \
--to=boyd@insultant.net \
--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).