From: Dipankar Sarma <dipankar@in.ibm.com>
To: Dave Miller <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] barriers in lockfree rtcache
Date: Fri, 3 Jan 2003 15:56:00 +0530 [thread overview]
Message-ID: <20030103102600.GC8582@in.ibm.com> (raw)
Dave,
This patch fixes several things in ipv4 route cache that I missed in
the last patch -
1. All the memory barriers are SMP-only avoiding unnecessary overhead on UP.
2. My forward porting merge of the rt_rcu patch dropped two changes in
rt_intern_hash() in around 2.5.43 that ordered the writes while
inserting a dst entry at the start of a hash chain. The dst entry updates
must be visible to other (weakly ordered) CPUs before it is inserted.
The necessary smp_wmb()s are added.
3. Comments to go with the write ordering.
Please apply.
Thanks
Dipankar
diff -urN linux-2.5.54-base/net/ipv4/route.c linux-2.5.54-rt_barriers/net/ipv4/route.c
--- linux-2.5.54-base/net/ipv4/route.c 2003-01-02 08:53:15.000000000 +0530
+++ linux-2.5.54-rt_barriers/net/ipv4/route.c 2003-01-03 14:44:31.000000000 +0530
@@ -234,7 +234,7 @@
{
struct rt_cache_iter_state *st = seq->private;
- read_barrier_depends();
+ smp_read_barrier_depends();
r = r->u.rt_next;
while (!r) {
rcu_read_unlock();
@@ -718,7 +718,18 @@
if (compare_keys(&rth->fl, &rt->fl)) {
/* Put it first */
*rthp = rth->u.rt_next;
+ /*
+ * Since lookup is lockfree, the deletion
+ * must be visible to another weakly ordered CPU before
+ * the insertion at the start of the hash chain.
+ */
+ smp_wmb();
rth->u.rt_next = rt_hash_table[hash].chain;
+ /*
+ * Since lookup is lockfree, the update writes
+ * must be ordered for consistency on SMP.
+ */
+ smp_wmb();
rt_hash_table[hash].chain = rth;
rth->u.dst.__use++;
@@ -900,7 +911,7 @@
while ((rth = *rthp) != NULL) {
struct rtable *rt;
- read_barrier_depends();
+ smp_read_barrier_depends();
if (rth->fl.fl4_dst != daddr ||
rth->fl.fl4_src != skeys[i] ||
rth->fl.fl4_tos != tos ||
@@ -1148,7 +1159,7 @@
rcu_read_lock();
for (rth = rt_hash_table[hash].chain; rth;
rth = rth->u.rt_next) {
- read_barrier_depends();
+ smp_read_barrier_depends();
if (rth->fl.fl4_dst == daddr &&
rth->fl.fl4_src == skeys[i] &&
rth->rt_dst == daddr &&
@@ -1740,7 +1751,7 @@
rcu_read_lock();
for (rth = rt_hash_table[hash].chain; rth; rth = rth->u.rt_next) {
- read_barrier_depends();
+ smp_read_barrier_depends();
if (rth->fl.fl4_dst == daddr &&
rth->fl.fl4_src == saddr &&
rth->fl.iif == iif &&
@@ -2105,7 +2116,7 @@
rcu_read_lock();
for (rth = rt_hash_table[hash].chain; rth; rth = rth->u.rt_next) {
- read_barrier_depends();
+ smp_read_barrier_depends();
if (rth->fl.fl4_dst == flp->fl4_dst &&
rth->fl.fl4_src == flp->fl4_src &&
rth->fl.iif == 0 &&
@@ -2335,7 +2346,7 @@
rcu_read_lock();
for (rt = rt_hash_table[h].chain, idx = 0; rt;
rt = rt->u.rt_next, idx++) {
- read_barrier_depends();
+ smp_read_barrier_depends();
if (idx < s_idx)
continue;
skb->dst = dst_clone(&rt->u.dst);
next reply other threads:[~2003-01-03 10:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 10:26 Dipankar Sarma [this message]
2003-01-06 8:41 ` [PATCH] barriers in lockfree rtcache David S. Miller
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=20030103102600.GC8582@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.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