From: Peter Zijlstra <peterz@infradead.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Jason Wang <jasowang@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH] virtio_ring: use smp_store_mb
Date: Thu, 17 Dec 2015 12:22:22 +0100 [thread overview]
Message-ID: <20151217112222.GC6375@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1450347932-16325-1-git-send-email-mst@redhat.com>
On Thu, Dec 17, 2015 at 12:32:53PM +0200, Michael S. Tsirkin wrote:
> Seems to give a speedup on my box but I'm less sure about this one. E.g. as
> xchng faster than mfence on all/most intel CPUs? Anyone has an opinion?
Would help if you Cc people who would actually know this :-)
Yes, we've recently established that xchg is indeed faster than mfence
on at least recent machines, see:
lkml.kernel.org/r/CA+55aFynbkeuUGs9s-q+fLY6MeRBA6MjEyWWbbe7A5AaqsAknw@mail.gmail.com
> +static inline void virtio_store_mb(bool weak_barriers,
> + __virtio16 *p, __virtio16 v)
> +{
> +#ifdef CONFIG_SMP
> + if (weak_barriers)
> + smp_store_mb(*p, v);
> + else
> +#endif
> + {
> + WRITE_ONCE(*p, v);
> + mb();
> + }
> +}
Note that virtio_mb() is weirdly inconsistent with virtio_[rw]mb() in
that they use dma_* ops for weak_barriers, while virtio_mb() uses
smp_mb().
As previously stated, smp_mb() does not cover the same memory domains as
dma_mb() would.
next prev parent reply other threads:[~2015-12-17 11:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 10:32 [PATCH] virtio_ring: use smp_store_mb Michael S. Tsirkin
2015-12-17 10:52 ` Peter Zijlstra
2015-12-17 13:16 ` Michael S. Tsirkin
2015-12-17 13:57 ` Peter Zijlstra
2015-12-17 14:33 ` Michael S. Tsirkin
2015-12-17 14:39 ` Peter Zijlstra
2015-12-17 14:43 ` Michael S. Tsirkin
2015-12-20 9:25 ` new barrier type for paravirt (was Re: [PATCH] virtio_ring: use smp_store_mb) Michael S. Tsirkin
2015-12-20 17:07 ` [Xen-devel] " Andrew Cooper
2015-12-20 19:59 ` Peter Zijlstra
2015-12-21 7:10 ` Michael S. Tsirkin
2015-12-21 7:22 ` [PATCH RFC] smp_store_mb should use smp_mb Michael S. Tsirkin
2015-12-21 10:47 ` [Xen-devel] new barrier type for paravirt (was Re: [PATCH] virtio_ring: use smp_store_mb) David Vrabel
2015-12-21 11:52 ` Michael S. Tsirkin
2015-12-21 14:50 ` [Qemu-devel] " Stefano Stabellini
2015-12-17 11:22 ` Peter Zijlstra [this message]
2015-12-17 13:26 ` [PATCH] virtio_ring: use smp_store_mb Michael S. Tsirkin
2015-12-17 14:02 ` Peter Zijlstra
2015-12-17 14:34 ` Michael S. Tsirkin
2015-12-17 15:09 ` Peter Zijlstra
2015-12-17 15:52 ` Will Deacon
2015-12-17 19:21 ` 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=20151217112222.GC6375@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox