LKML Archive on
help / color / mirror / Atom feed
From: Jamie Lokier <>
To: "Richard B. Johnson" <>
Cc: Al Niessner <>,
Subject: Re: atomic_t and atomic_inc
Date: Sat, 15 May 2004 23:54:01 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <Pine.LNX.4.53.0404221641120.940@chaos>

Richard B. Johnson wrote:
> Type atomic_t is an integer that can be accessed in memory
> with an uninterruptible instruction. This limits the atomic_t
> type in 32-bit machines to 32-bits, in 64-bit machines to 64-bits,
> etc. It has nothing to do with wrap-around. If you increment
> 0xffffffff it becomes 0 even it it's an atomic type.

Note that atomic_t used to be 24 bits on Sparc.  It isn't any more, though.

-- Jame

      reply	other threads:[~2004-05-15 22:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-22 18:58 Al Niessner
2004-04-22 20:50 ` Richard B. Johnson
2004-05-15 22:54   ` Jamie Lokier [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: atomic_t and atomic_inc' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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 NNTP newsgroup(s).