From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: linux-kernel@vger.kernel.org, ltt-dev@shafik.org
Subject: Per CPU non locked atomic operations
Date: Sat, 3 Jun 2006 07:26:17 -0400 [thread overview]
Message-ID: <20060603112617.GB14581@Krystal> (raw)
Hi,
In the kernel tracer I develop (LTTng : http://ltt.polymtl.ca), I see a need
that could be shared by others : I extensively use per-CPU data structures to
provide efficient tracing. In addition to that, I use atomic operations (cmpxchg
and atomic increment) to keep track of offsets in the buffer so it can be
reentrant with NMI handlers.
Would there be some larger interest for having non LOCK prefixed versions of
atomic.h functions and cmpxchg for per-CPU variable purposes ?
Mathieu
OpenPGP public key: http://krystal.dyndns.org:8080/key/compudj.gpg
Key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
reply other threads:[~2006-06-03 11:26 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=20060603112617.GB14581@Krystal \
--to=compudj@krystal.dyndns.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@shafik.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