From: kaz Kojima <kkojima@rr.iij4u.or.jp>
To: davidm@hpl.hp.com
Cc: libc-hacker@sources.redhat.com
Subject: Re: [PATCH] SH: atomic.h fixes
Date: Sat, 29 Mar 2003 06:59:00 -0000 [thread overview]
Message-ID: <200303290410.h2T4AX828165@r-rr.iij4u.or.jp> (raw)
In-Reply-To: Your message of "Fri, 28 Mar 2003 19:02:57 -0800" <16005.3297.263899.620401@napali.hpl.hp.com>
David Mosberger <davidm@napali.hpl.hp.com> wrote:
> Perhaps a pointer to Bershad's paper might be appropriate, too:
>
> B.N. Bershad, D. Redell, and J. Ellis. Fast Mutual Exclusion for
> Uniprocessors. Proceedings of the Fifth Architectural Support for
> Programming Languages and Operating Systems (ASPLOS), pp. 223-233,
> October 1992.
>
> http://www.cs.washington.edu/homes/bershad/Papers/Rcs.ps
Thanks for the pointer. I'll read it.
Regards,
kaz
next prev parent reply other threads:[~2003-03-29 4:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-29 1:23 kaz Kojima
2003-03-29 2:06 ` Ulrich Drepper
2003-03-29 2:13 ` kaz Kojima
2003-03-29 2:26 ` Roland McGrath
2003-03-29 2:39 ` kaz Kojima
2003-03-29 2:40 ` Roland McGrath
2003-03-29 3:03 ` kaz Kojima
2003-03-29 4:10 ` David Mosberger
2003-03-29 6:59 ` kaz Kojima [this message]
2003-03-29 2:36 ` Ulrich Drepper
2003-03-29 2:58 ` kaz Kojima
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=200303290410.h2T4AX828165@r-rr.iij4u.or.jp \
--to=kkojima@rr.iij4u.or.jp \
--cc=davidm@hpl.hp.com \
--cc=libc-hacker@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).