From: Roland McGrath <roland@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] sparc* bits/atomic.h
Date: Sun, 30 Mar 2003 23:59:00 -0000 [thread overview]
Message-ID: <200303302340.h2UNe1X00695@magilla.sf.frob.com> (raw)
In-Reply-To: Jakub Jelinek's message of Monday, 31 March 2003 00:44:05 +0200 <20030330224405.GA16629@sunsite.ms.mff.cuni.cz>
> 2003-03-31 Jakub Jelinek <jakub@redhat.com>
>
> * sysdeps/sparc/sparc32/bits/atomic.h: New file.
> * sysdeps/sparc/sparc32/sparcv9/bits/atomic.h: New file.
> * sysdeps/sparc/sparc64/bits/atomic.h: New file.
>
> * sysdeps/sparc/sparc32/atomicity.h: Removed.
> * sysdeps/sparc/sparc32/sparcv9/atomicity.h: Removed.
> * sysdeps/sparc/sparc64/atomicity.h: Removed.
Thanks, applied.
> sparc32 (not v9) lacks compare and swap, so it is implemented using
> test-and-set and a global lock. IMHO better than no locking at all,
> performance will suck as usually on those aging boxes.
Are there any actual MP boxes using those chips that Linux runs on? If not
then you could use a software atomic sequence with kernel support like SH does.
e.g., the low bit of the thread register says to reload the PC from some
other register (and clear the flag bit).
Thanks,
Roland
next parent reply other threads:[~2003-03-30 23:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030330224405.GA16629@sunsite.ms.mff.cuni.cz>
2003-03-30 23:59 ` Roland McGrath [this message]
[not found] <20030330184700.J13397@devserv.devel.redhat.com>
2003-03-31 7:18 ` Roland McGrath
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=200303302340.h2UNe1X00695@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=drepper@redhat.com \
--cc=jakub@redhat.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).