From: Al Niessner <Al.Niessner@jpl.nasa.gov>
To: linux-kernel@vger.kernel.org
Subject: atomic_t and atomic_inc
Date: Thu, 22 Apr 2004 11:58:40 -0700 [thread overview]
Message-ID: <1082660320.28900.193.camel@morte.jpl.nasa.gov> (raw)
First, I am not subscribed to this list so please reply to me directly
if you wish a timely response to any questions. In any case, I will lurk
in the archives for responses.
I am using atomic_t to count interrupts from some piece of hardware.
These interrupts come at a fairly high rate -- 10 KHz and higher. The
problem is, will I get increment problem at the limit of atomic_t or
will it wrap around without error? I read the docs (man pages, on-line
api docs, this list and other stuff) and none of them talk about the
behavior of atomic_t at the boundaries. Furthermore, am I guaranteed of
any boundary behavior across platforms?
Thank you in advance for any and all help.
--
Al Niessner <Al.Niessner@jpl.nasa.gov>
Jet Propulsion Laboratory
All opinions stated above are mine and do not necessarily reflect
those of JPL or NASA.
----
| dS | >= 0
----
next reply other threads:[~2004-04-22 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 18:58 Al Niessner [this message]
2004-04-22 20:50 ` Richard B. Johnson
2004-05-15 22:54 ` Jamie Lokier
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=1082660320.28900.193.camel@morte.jpl.nasa.gov \
--to=al.niessner@jpl.nasa.gov \
--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®