From: cakturk@gmail.com (Cihangir Akturk)
To: kernelnewbies@lists.kernelnewbies.org
Subject: ACCESS_ONCE usage inside llist_add_batch function
Date: Sat, 28 Feb 2015 22:12:23 +0200 [thread overview]
Message-ID: <20150228201223.GA2291@lg> (raw)
Reading the lib/llist.c file in the kernel sources, I came across
the llist_add_bach function defined like this;
bool llist_add_batch(struct llist_node *new_first, struct llist_node *new_last,
struct llist_head *head)
{
struct llist_node *first;
do {
new_last->next = first = ACCESS_ONCE(head->first);
} while (cmpxchg(&head->first, first, new_first) != first);
return !first;
}
One thing bugging my mind is the ACCESS_ONCE macro. Is it really
needed here ? I mean I would write this function with ACCES_ONCE
moved outside the loop like as follows;
bool llist_add_batch(struct llist_node *new_first, struct llist_node *new_last,
struct llist_head *head)
{
struct llist_node *first, *old;
old = ACCESS_ONCE(head->first);
for (;;) {
first = old;
new_last->next = old;
old = cmpxchg(&head->first, first, new_first);
if (old == first)
break;
}
return !first;
}
I think that it may be faster to just use the return value of cmpxchg.
But I am not sure about this.
Is my understanding correct ?
next reply other threads:[~2015-02-28 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-28 20:12 Cihangir Akturk [this message]
2015-03-03 6:21 ` ACCESS_ONCE usage inside llist_add_batch function John de la Garza
2015-03-03 6:38 ` Chinmay V S
2015-03-04 0:41 ` Cihangir Akturk
2015-03-04 8:34 ` Arun KS
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=20150228201223.GA2291@lg \
--to=cakturk@gmail.com \
--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 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).