From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: atomic64_t proposal
Date: 28 Aug 2002 14:39:28 -0700 [thread overview]
Message-ID: <akjfug$o47$1@cesium.transmeta.com> (raw)
In-Reply-To: Pine.LNX.4.44.0208281040010.14946-100000@rmholt.homeip.net
Followup to: <Pine.LNX.4.44.0208281040010.14946-100000@rmholt.homeip.net>
By author: Robin Holt <holt@rmholt.homeip.net>
In newsgroup: linux.dev.kernel
>
> I do like the atomic_inc, atomic_dec, etc being able to handle either
> type. While producing code, I can do a simple check at the beginning of
> the block and define the appropriate type for a particular architecture.
>
Great. How do you expect to implement atomic_inc() et al so that that
can actually be done? Consider that atomic64_t may very well need
full-blown spinlocks, whereas a 32-bit atomic_t may not.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-08-28 21:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 15:45 atomic64_t proposal Robin Holt
2002-08-28 21:39 ` H. Peter Anvin [this message]
[not found] <200208271937.OAA78345@cyan.americas.sgi.com.suse.lists.linux.kernel>
2002-08-27 19:58 ` Andi Kleen
2002-08-27 20:29 ` David S. Miller
2002-08-27 20:54 ` Benjamin LaHaise
2002-08-29 17:15 ` Dean Nelson
-- strict thread matches above, loose matches on Subject: below --
2002-08-27 19:37 Dean Nelson
2002-08-27 20:02 ` Andreas Schwab
2002-08-28 14:59 ` Dean Nelson
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='akjfug$o47$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/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