From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Huang Ying <ying.huang@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH -mm 3/4] llist, Move cpu_relax after cmpxchg
Date: Tue, 6 Sep 2011 06:52:39 -0400 [thread overview]
Message-ID: <20110906105239.GC21602@Krystal> (raw)
In-Reply-To: <1315290307-25145-3-git-send-email-ying.huang@intel.com>
* Huang Ying (ying.huang@intel.com) wrote:
> If the first cmpxchg calling succeeds, it is not necessary to use
> cpu_relax before cmpxchg. So cpu_relax in a busy loop involving
> cmpxchg should go after cmpxchg instead of before that. This patch
> fixes this in llist.
>
Acked-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Thanks!
MAthieu
> Signed-off-by: Huang Ying <ying.huang@intel.com>
> Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> ---
> include/linux/llist.h | 21 +++++++++++++++------
> 1 file changed, 15 insertions(+), 6 deletions(-)
>
> --- a/include/linux/llist.h
> +++ b/include/linux/llist.h
> @@ -156,11 +156,14 @@ static inline void llist_add(struct llis
> CHECK_NMI_SAFE_CMPXCHG();
>
> entry = head->first;
> - do {
> + for (;;) {
> old_entry = entry;
> new->next = entry;
> + entry = cmpxchg(&head->first, old_entry, new);
> + if (entry == old_entry)
> + break;
> cpu_relax();
> - } while ((entry = cmpxchg(&head->first, old_entry, new)) != old_entry);
> + }
> }
>
> /**
> @@ -178,11 +181,14 @@ static inline void llist_add_batch(struc
> CHECK_NMI_SAFE_CMPXCHG();
>
> entry = head->first;
> - do {
> + for (;;) {
> old_entry = entry;
> new_last->next = entry;
> + entry = cmpxchg(&head->first, old_entry, new_first);
> + if (entry == old_entry)
> + break;
> cpu_relax();
> - } while ((entry = cmpxchg(&head->first, old_entry, new_first)) != old_entry);
> + }
> }
>
> /**
> @@ -206,13 +212,16 @@ static inline struct llist_node *llist_d
> CHECK_NMI_SAFE_CMPXCHG();
>
> entry = head->first;
> - do {
> + for (;;) {
> if (entry == NULL)
> return NULL;
> old_entry = entry;
> next = entry->next;
> + entry = cmpxchg(&head->first, old_entry, next);
> + if (entry == old_entry)
> + break;
> cpu_relax();
> - } while ((entry = cmpxchg(&head->first, old_entry, next)) != old_entry);
> + }
>
> return entry;
> }
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2011-09-06 10:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 6:25 [PATCH -mm 1/4] llist, Make all llist functions inline Huang Ying
2011-09-06 6:25 ` [PATCH -mm 2/4] llist, Define macro to check NMI safe cmpxchg Huang Ying
2011-09-06 10:50 ` Mathieu Desnoyers
2011-09-06 6:25 ` [PATCH -mm 3/4] llist, Move cpu_relax after cmpxchg Huang Ying
2011-09-06 10:52 ` Mathieu Desnoyers [this message]
2011-09-06 6:25 ` [PATCH -mm 4/4] irq_work, Use llist in irq_work Huang Ying
2011-09-06 10:57 ` Mathieu Desnoyers
2011-09-07 0:55 ` Huang Ying
2011-09-07 7:52 ` Peter Zijlstra
2011-09-06 10:47 ` [PATCH -mm 1/4] llist, Make all llist functions inline Mathieu Desnoyers
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=20110906105239.GC21602@Krystal \
--to=mathieu.desnoyers@efficios.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=ying.huang@intel.com \
/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).