From: Sven Eckelmann <sven.eckelmann@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Range of 24/32 bit for atomic_t since 2.6.3
Date: Mon, 26 Apr 2010 11:31:19 +0200 [thread overview]
Message-ID: <201004261131.20178.sven.eckelmann@gmx.de> (raw)
[-- Attachment #1: Type: Text/Plain, Size: 629 bytes --]
Hi,
currently arch/mn10300/include/asm/atomic.h and include/asm-generic/atomic.h
warns right before atomic_read/atomic_set/atomic_add_return/ atomic_sub_return
that atomic_t only guarantees a useful range of 24 bits.
Documentation/atomic_ops.txt informs about the historical reason why this was
true for 32-bit Sparc - something that was changes in linux 2.6.3 using a hash
array with spinlocks [1].
Is it save to assume that atomic_t provides us the full range of 32 bit after
2.6.3 and can those statements in both atomic.h be removed?
Kind regards,
Sven Eckelmann
[1] http://lwn.net/Articles/71732/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2010-04-26 9:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201004261131.20178.sven.eckelmann@gmx.de \
--to=sven.eckelmann@gmx.de \
--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
all inboxes | Powered by JetHome®