From: Dipankar Sarma <dipankar@in.ibm.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] RCU - Make barriers SMP-only
Date: Fri, 3 Jan 2003 14:43:34 +0530 [thread overview]
Message-ID: <20030103091334.GA8582@in.ibm.com> (raw)
Linus,
This patch makes the barriers used in RCU list macros SMP-only avoiding
the unnecessary overhead of atomic operation on UP. Please apply.
Thanks
Dipankar
list.h | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff -urN linux-2.5.54-base/include/linux/list.h linux-2.5.54-rcu_barriers/include/linux/list.h
--- linux-2.5.54-base/include/linux/list.h 2003-01-02 08:50:59.000000000 +0530
+++ linux-2.5.54-rcu_barriers/include/linux/list.h 2003-01-03 14:27:21.000000000 +0530
@@ -83,7 +83,7 @@
{
new->next = next;
new->prev = prev;
- wmb();
+ smp_wmb();
next->prev = new;
prev->next = new;
}
@@ -302,11 +302,11 @@
*/
#define list_for_each_rcu(pos, head) \
for (pos = (head)->next, prefetch(pos->next); pos != (head); \
- pos = pos->next, ({ read_barrier_depends(); 0;}), prefetch(pos->next))
+ pos = pos->next, ({ smp_read_barrier_depends(); 0;}), prefetch(pos->next))
#define __list_for_each_rcu(pos, head) \
for (pos = (head)->next; pos != (head); \
- pos = pos->next, ({ read_barrier_depends(); 0;}))
+ pos = pos->next, ({ smp_read_barrier_depends(); 0;}))
/**
* list_for_each_safe_rcu - iterate over an rcu-protected list safe
@@ -317,7 +317,7 @@
*/
#define list_for_each_safe_rcu(pos, n, head) \
for (pos = (head)->next, n = pos->next; pos != (head); \
- pos = n, ({ read_barrier_depends(); 0;}), n = pos->next)
+ pos = n, ({ smp_read_barrier_depends(); 0;}), n = pos->next)
#else
#warning "don't include kernel headers in userspace"
reply other threads:[~2003-01-03 9:03 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=20030103091334.GA8582@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 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.