From: "David S. Miller" <davem@redhat.com>
To: ak@suse.de
Cc: dcn@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: atomic64_t proposal
Date: Tue, 27 Aug 2002 13:29:44 -0700 (PDT) [thread overview]
Message-ID: <20020827.132944.123972162.davem@redhat.com> (raw)
In-Reply-To: <p73sn102hvu.fsf@oldwotan.suse.de>
From: Andi Kleen <ak@suse.de>
Date: 27 Aug 2002 21:58:45 +0200
If yes, the implementation on 32bit could be a problem. e.g. some
archs need space in there for spinlocks, so it would be needed to limit
the usable range.
x86 would need 1 bit, some other 32-bit platforms would be ok
with just a byte (ie. 8 bits).
I don't like this whole transparent idea just like you Andi.
People should ask for the types they want, if they want 64-bits
of counter, they should explicitly use atomic64_t and use the
atomic64_t operations on that type.
next prev parent reply other threads:[~2002-08-27 20:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200208271937.OAA78345@cyan.americas.sgi.com.suse.lists.linux.kernel>
2002-08-27 19:58 ` atomic64_t proposal Andi Kleen
2002-08-27 20:29 ` David S. Miller [this message]
2002-08-27 20:54 ` Benjamin LaHaise
2002-08-29 17:15 ` Dean Nelson
2002-08-28 15:45 Robin Holt
2002-08-28 21:39 ` H. Peter Anvin
-- 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=20020827.132944.123972162.davem@redhat.com \
--to=davem@redhat.com \
--cc=ak@suse.de \
--cc=dcn@sgi.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