From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Gregory Haskins <gregory.haskins@gmail.com>,
netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@elte.hu, linux-mm@kvack.org,
akpm@linux-foundation.org, hpa@zytor.com,
Rusty Russell <rusty@rustcorp.com.au>,
s.hetze@linux-ag.com,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCHv7 3/3] vhost_net: a kernel-level virtio server
Date: Tue, 03 Nov 2009 22:11:12 +0100 [thread overview]
Message-ID: <4AF09C70.6090505@gmail.com> (raw)
In-Reply-To: <20091103195841.GB6669@redhat.com>
Michael S. Tsirkin a écrit :
>
> Paul, you acked this previously. Should I add you acked-by line so
> people calm down? If you would rather I replace
> rcu_dereference/rcu_assign_pointer with rmb/wmb, I can do this.
> Or maybe patch Documentation to explain this RCU usage?
>
So you believe I am over-reacting to this dubious use of RCU ?
RCU documentation is already very complex, we dont need to add yet another
subtle use, and makes it less readable.
It seems you use 'RCU api' in drivers/vhost/net.c as convenient macros :
#define rcu_dereference(p) ({ \
typeof(p) _________p1 = ACCESS_ONCE(p); \
smp_read_barrier_depends(); \
(_________p1); \
})
#define rcu_assign_pointer(p, v) \
({ \
if (!__builtin_constant_p(v) || \
((v) != NULL)) \
smp_wmb(); \
(p) = (v); \
})
There are plenty regular uses of smp_wmb() in kernel, not related to Read Copy Update,
there is nothing wrong to use barriers with appropriate comments.
(And you already use mb(), wmb(), rmb(), smp_wmb() in your patch)
BTW there is at least one locking bug in vhost_net_set_features()
Apparently, mutex_unlock() doesnt trigger a fault if mutex is not locked
by current thread... even with DEBUG_MUTEXES / DEBUG_LOCK_ALLOC
static void vhost_net_set_features(struct vhost_net *n, u64 features)
{
size_t hdr_size = features & (1 << VHOST_NET_F_VIRTIO_NET_HDR) ?
sizeof(struct virtio_net_hdr) : 0;
int i;
<<!>> mutex_unlock(&n->dev.mutex);
n->dev.acked_features = features;
smp_wmb();
for (i = 0; i < VHOST_NET_VQ_MAX; ++i) {
mutex_lock(&n->vqs[i].mutex);
n->vqs[i].hdr_size = hdr_size;
mutex_unlock(&n->vqs[i].mutex);
}
mutex_unlock(&n->dev.mutex);
vhost_net_flush(n);
}
WARNING: multiple messages have this Message-ID (diff)
From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Gregory Haskins <gregory.haskins@gmail.com>,
netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@elte.hu, linux-mm@kvack.org,
akpm@linux-foundation.org, hpa@zytor.com,
Rusty Russell <rusty@rustcorp.com.au>,
s.hetze@linux-ag.com,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCHv7 3/3] vhost_net: a kernel-level virtio server
Date: Tue, 03 Nov 2009 22:11:12 +0100 [thread overview]
Message-ID: <4AF09C70.6090505@gmail.com> (raw)
In-Reply-To: <20091103195841.GB6669@redhat.com>
Michael S. Tsirkin a écrit :
>
> Paul, you acked this previously. Should I add you acked-by line so
> people calm down? If you would rather I replace
> rcu_dereference/rcu_assign_pointer with rmb/wmb, I can do this.
> Or maybe patch Documentation to explain this RCU usage?
>
So you believe I am over-reacting to this dubious use of RCU ?
RCU documentation is already very complex, we dont need to add yet another
subtle use, and makes it less readable.
It seems you use 'RCU api' in drivers/vhost/net.c as convenient macros :
#define rcu_dereference(p) ({ \
typeof(p) _________p1 = ACCESS_ONCE(p); \
smp_read_barrier_depends(); \
(_________p1); \
})
#define rcu_assign_pointer(p, v) \
({ \
if (!__builtin_constant_p(v) || \
((v) != NULL)) \
smp_wmb(); \
(p) = (v); \
})
There are plenty regular uses of smp_wmb() in kernel, not related to Read Copy Update,
there is nothing wrong to use barriers with appropriate comments.
(And you already use mb(), wmb(), rmb(), smp_wmb() in your patch)
BTW there is at least one locking bug in vhost_net_set_features()
Apparently, mutex_unlock() doesnt trigger a fault if mutex is not locked
by current thread... even with DEBUG_MUTEXES / DEBUG_LOCK_ALLOC
static void vhost_net_set_features(struct vhost_net *n, u64 features)
{
size_t hdr_size = features & (1 << VHOST_NET_F_VIRTIO_NET_HDR) ?
sizeof(struct virtio_net_hdr) : 0;
int i;
<<!>> mutex_unlock(&n->dev.mutex);
n->dev.acked_features = features;
smp_wmb();
for (i = 0; i < VHOST_NET_VQ_MAX; ++i) {
mutex_lock(&n->vqs[i].mutex);
n->vqs[i].hdr_size = hdr_size;
mutex_unlock(&n->vqs[i].mutex);
}
mutex_unlock(&n->dev.mutex);
vhost_net_flush(n);
}
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Gregory Haskins <gregory.haskins@gmail.com>,
netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@elte.hu, linux-mm@kvack.org,
akpm@linux-foundation.org, hpa@zytor.com,
Rusty Russell <rusty@rustcorp.com.au>,
s.hetze@linux-ag.com,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCHv7 3/3] vhost_net: a kernel-level virtio server
Date: Tue, 03 Nov 2009 22:11:12 +0100 [thread overview]
Message-ID: <4AF09C70.6090505@gmail.com> (raw)
In-Reply-To: <20091103195841.GB6669@redhat.com>
Michael S. Tsirkin a ecrit :
>
> Paul, you acked this previously. Should I add you acked-by line so
> people calm down? If you would rather I replace
> rcu_dereference/rcu_assign_pointer with rmb/wmb, I can do this.
> Or maybe patch Documentation to explain this RCU usage?
>
So you believe I am over-reacting to this dubious use of RCU ?
RCU documentation is already very complex, we dont need to add yet another
subtle use, and makes it less readable.
It seems you use 'RCU api' in drivers/vhost/net.c as convenient macros :
#define rcu_dereference(p) ({ \
typeof(p) _________p1 = ACCESS_ONCE(p); \
smp_read_barrier_depends(); \
(_________p1); \
})
#define rcu_assign_pointer(p, v) \
({ \
if (!__builtin_constant_p(v) || \
((v) != NULL)) \
smp_wmb(); \
(p) = (v); \
})
There are plenty regular uses of smp_wmb() in kernel, not related to Read Copy Update,
there is nothing wrong to use barriers with appropriate comments.
(And you already use mb(), wmb(), rmb(), smp_wmb() in your patch)
BTW there is at least one locking bug in vhost_net_set_features()
Apparently, mutex_unlock() doesnt trigger a fault if mutex is not locked
by current thread... even with DEBUG_MUTEXES / DEBUG_LOCK_ALLOC
static void vhost_net_set_features(struct vhost_net *n, u64 features)
{
size_t hdr_size = features & (1 << VHOST_NET_F_VIRTIO_NET_HDR) ?
sizeof(struct virtio_net_hdr) : 0;
int i;
<<!>> mutex_unlock(&n->dev.mutex);
n->dev.acked_features = features;
smp_wmb();
for (i = 0; i < VHOST_NET_VQ_MAX; ++i) {
mutex_lock(&n->vqs[i].mutex);
n->vqs[i].hdr_size = hdr_size;
mutex_unlock(&n->vqs[i].mutex);
}
mutex_unlock(&n->dev.mutex);
vhost_net_flush(n);
}
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-11-03 21:13 UTC|newest]
Thread overview: 107+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1257267892.git.mst@redhat.com>
2009-11-03 17:24 ` [PATCHv7 1/3] tun: export underlying socket Michael S. Tsirkin
2009-11-03 17:24 ` Michael S. Tsirkin
2009-11-03 17:24 ` Michael S. Tsirkin
2009-11-04 13:30 ` David Miller
2009-11-04 13:30 ` David Miller
2009-11-04 13:30 ` David Miller
2009-11-03 17:24 ` Michael S. Tsirkin
2009-11-03 17:24 ` [PATCHv7 2/3] mm: export use_mm/unuse_mm to modules Michael S. Tsirkin
2009-11-03 17:24 ` Michael S. Tsirkin
2009-11-03 17:24 ` Michael S. Tsirkin
2009-11-03 17:32 ` Gregory Haskins
2009-11-03 17:32 ` Gregory Haskins
2009-11-03 17:24 ` Michael S. Tsirkin
2009-11-03 17:24 ` [PATCHv7 3/3] vhost_net: a kernel-level virtio server Michael S. Tsirkin
2009-11-03 17:24 ` Michael S. Tsirkin
2009-11-03 17:24 ` Michael S. Tsirkin
2009-11-03 18:03 ` Eric Dumazet
2009-11-03 18:03 ` Eric Dumazet
2009-11-03 18:03 ` Eric Dumazet
2009-11-03 18:03 ` Eric Dumazet
2009-11-03 18:08 ` Gregory Haskins
2009-11-03 18:08 ` Gregory Haskins
2009-11-03 18:14 ` Gregory Haskins
2009-11-03 18:51 ` Eric Dumazet
2009-11-03 18:51 ` Eric Dumazet
2009-11-03 18:51 ` Eric Dumazet
2009-11-03 18:51 ` Eric Dumazet
2009-11-03 19:50 ` Gregory Haskins
2009-11-03 19:50 ` Gregory Haskins
2009-11-03 19:58 ` Michael S. Tsirkin
2009-11-03 19:58 ` Michael S. Tsirkin
2009-11-03 19:58 ` Michael S. Tsirkin
2009-11-03 21:11 ` Eric Dumazet [this message]
2009-11-03 21:11 ` Eric Dumazet
2009-11-03 21:11 ` Eric Dumazet
2009-11-04 12:04 ` Michael S. Tsirkin
2009-11-04 12:04 ` Michael S. Tsirkin
2009-11-04 12:04 ` Michael S. Tsirkin
2009-11-04 12:04 ` Michael S. Tsirkin
2009-11-03 21:11 ` Eric Dumazet
2009-11-03 19:58 ` Michael S. Tsirkin
2009-11-03 23:57 ` Paul E. McKenney
2009-11-03 23:57 ` Paul E. McKenney
2009-11-03 23:57 ` Paul E. McKenney
2009-11-03 23:57 ` Paul E. McKenney
2009-11-04 11:57 ` Michael S. Tsirkin
2009-11-04 11:57 ` Michael S. Tsirkin
2009-11-04 11:57 ` Michael S. Tsirkin
2009-11-04 17:25 ` Paul E. McKenney
2009-11-04 17:25 ` Paul E. McKenney
2009-11-04 17:25 ` Paul E. McKenney
2009-11-04 17:33 ` Eric Dumazet
2009-11-04 17:33 ` Eric Dumazet
2009-11-04 17:33 ` Eric Dumazet
2009-11-04 17:33 ` Eric Dumazet
2009-11-04 19:06 ` Michael S. Tsirkin
2009-11-04 19:06 ` Michael S. Tsirkin
2009-11-04 19:06 ` Michael S. Tsirkin
2009-11-04 19:12 ` Gregory Haskins
2009-11-04 19:12 ` Gregory Haskins
2009-11-06 5:01 ` Rusty Russell
2009-11-06 5:01 ` Rusty Russell
2009-11-06 5:01 ` Rusty Russell
2009-11-06 16:30 ` Paul E. McKenney
2009-11-06 16:30 ` Paul E. McKenney
2009-11-06 16:30 ` Paul E. McKenney
2009-11-08 4:09 ` Rusty Russell
2009-11-08 4:09 ` Rusty Russell
2009-11-08 19:36 ` Paul E. McKenney
2009-11-08 19:36 ` Paul E. McKenney
2009-11-08 19:36 ` Paul E. McKenney
2009-11-08 4:09 ` Rusty Russell
2009-11-04 17:25 ` Paul E. McKenney
2009-11-04 11:57 ` Michael S. Tsirkin
2009-11-03 18:14 ` Gregory Haskins
2009-11-03 19:55 ` Michael S. Tsirkin
2009-11-03 19:55 ` Michael S. Tsirkin
2009-11-03 19:55 ` Michael S. Tsirkin
2009-11-03 19:55 ` Michael S. Tsirkin
2009-11-04 11:08 ` Andi Kleen
2009-11-04 11:08 ` Andi Kleen
2009-11-04 12:10 ` Michael S. Tsirkin
2009-11-04 12:10 ` Michael S. Tsirkin
2009-11-04 12:59 ` Andi Kleen
2009-11-04 12:59 ` Andi Kleen
2009-11-04 12:59 ` Andi Kleen
2009-11-04 13:08 ` Michael S. Tsirkin
2009-11-04 13:08 ` Michael S. Tsirkin
2009-11-04 13:08 ` Michael S. Tsirkin
2009-11-04 13:15 ` Andi Kleen
2009-11-04 13:15 ` Andi Kleen
2009-11-04 13:15 ` Andi Kleen
2009-11-04 13:17 ` Michael S. Tsirkin
2009-11-04 13:17 ` Michael S. Tsirkin
2009-11-04 13:17 ` Michael S. Tsirkin
2009-11-04 13:37 ` Andi Kleen
2009-11-04 13:37 ` Andi Kleen
2009-11-04 13:37 ` Andi Kleen
2009-11-04 13:41 ` Michael S. Tsirkin
2009-11-04 13:41 ` Michael S. Tsirkin
2009-11-04 16:37 ` Michael S. Tsirkin
2009-11-04 16:37 ` Michael S. Tsirkin
2009-11-04 16:37 ` Michael S. Tsirkin
2009-11-04 13:41 ` Michael S. Tsirkin
2009-11-04 12:10 ` Michael S. Tsirkin
2009-11-04 11:08 ` Andi Kleen
2009-11-03 17:24 ` Michael S. Tsirkin
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=4AF09C70.6090505@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=gregory.haskins@gmail.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rusty@rustcorp.com.au \
--cc=s.hetze@linux-ag.com \
--cc=virtualization@lists.linux-foundation.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.