From: me@tobin.cc (Tobin C. Harding)
To: kernelnewbies@lists.kernelnewbies.org
Subject: atomic test and set
Date: Wed, 18 Oct 2017 11:40:44 +1100 [thread overview]
Message-ID: <20171018004044.GA8552@eros> (raw)
Hi,
Do we have an atomic test and set function in the kernel. I have tried
const int KEY_FLAG_BIT = 1;
...
static siphash_key_t ptr_secret __read_mostly;
static unsigned long have_key = 0;
if (test_and_set_bit(KEY_FLAG_BIT, &have_key))
get_random_bytes(&ptr_secret, sizeof(ptr_secret));
But that doesn't work.
I looked in include/linux/atomic.h and thought about using
static atomic_t have_key = ATOMIC_INIT(0);
if (atomic_xchg(&have_key, 1) == 0)
get_random_bytes(&ptr_secret, sizeof(ptr_secret));
This works. My question is; does this code LOAD the value at have_key and STORE the argument on
every call? Or does it LOAD the value, check if it is the same as the argument, and STORE _only_ if
it is different?
(Is this whole discussion just premature optimization?)
I cannot grok the macros in atomic.h, they seem circular. Here is the macro definitions in call
chain order starting with atomic_xchg()
#define atomic_xchg(...) \
__atomic_op_fence(atomic_xchg, __VA_ARGS__)
#define __atomic_op_fence(op, args...) \
({ \
typeof(op##_relaxed(args)) __ret; \
smp_mb__before_atomic(); \
__ret = op##_relaxed(args); \
smp_mb__after_atomic(); \
__ret; \
})
#define atomic_xchg_release(...) \
__atomic_op_release(atomic_xchg, __VA_ARGS__)
#define __atomic_op_release(op, args...) \
({ \
smp_mb__before_atomic(); \
op##_relaxed(args); \
})
#define atomic_xchg_relaxed atomic_xchg
thanks,
Tobin.
next reply other threads:[~2017-10-18 0:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 0:40 Tobin C. Harding [this message]
2017-10-18 1:33 ` atomic test and set Anish Kumar
2017-10-20 14:22 ` Yubin Ruan
2017-10-20 8:55 ` Tobin C. Harding
2017-10-20 9:33 ` Yubin Ruan
2017-10-22 1:50 ` Tobin C. Harding
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=20171018004044.GA8552@eros \
--to=me@tobin.cc \
--cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.