From: Borislav Petkov <bp@alien8.de>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Davidlohr Bueso <dave@stgolabs.net>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
the arch/x86 maintainers <x86@kernel.org>,
Davidlohr Bueso <dbueso@suse.de>,
"H. Peter Anvin" <hpa@zytor.com>,
virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH v3 0/4] x86: faster mb()+documentation tweaks
Date: Thu, 14 Jan 2016 12:39:34 +0100 [thread overview]
Message-ID: <20160114113934.GC19941@pd.tnic> (raw)
In-Reply-To: <1452715911-12067-1-git-send-email-mst@redhat.com>
On Wed, Jan 13, 2016 at 10:12:22PM +0200, Michael S. Tsirkin wrote:
> mb() typically uses mfence on modern x86, but a micro-benchmark shows that it's
> 2 to 3 times slower than lock; addl that we use on older CPUs.
>
> So let's use the locked variant everywhere.
>
> While I was at it, I found some inconsistencies in comments in
> arch/x86/include/asm/barrier.h
>
> The documentation fixes are included first - I verified that
> they do not change the generated code at all. They should be
> safe to apply directly.
>
> The last patch changes mb() to lock addl. I was unable to
> measure a speed difference on a macro benchmark,
> but I noted that even doing
> #define mb() barrier()
> seems to make no difference for most benchmarks
> (it causes hangs sometimes, of course).
>
> HPA asked that the last patch is deferred until we hear back from
> intel, which makes sense of course. So it needs HPA's ack.
>
> I hope I'm not splitting this up too much - the reason is I wanted to isolate
> the code changes (that people might want to test for performance)
> from comment changes approved by Linus, from (so far unreviewed) changes
> I came up with myself.
>
> Changes from v2:
> add patch adding cc clobber for addl
> tweak commit log for patch 2
> use addl at SP-4 (as opposed to SP) to reduce data dependencies
>
> Michael S. Tsirkin (4):
> x86: add cc clobber for addl
> x86: drop a comment left over from X86_OOSTORE
> x86: tweak the comment about use of wmb for IO
First three look ok to me regardless of what happens with 4. So applied.
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2016-01-14 11:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 20:12 [PATCH v3 0/4] x86: faster mb()+documentation tweaks Michael S. Tsirkin
2016-01-13 20:12 ` [PATCH v3 1/4] x86: add cc clobber for addl Michael S. Tsirkin
2016-01-13 20:12 ` [PATCH v3 2/4] x86: drop a comment left over from X86_OOSTORE Michael S. Tsirkin
2016-01-13 20:12 ` [PATCH v3 3/4] x86: tweak the comment about use of wmb for IO Michael S. Tsirkin
2016-01-13 20:12 ` [PATCH v3 4/4] x86: drop mfence in favor of lock+addl Michael S. Tsirkin
2016-01-14 11:39 ` Borislav Petkov [this message]
2016-01-26 8:23 ` [PATCH v3 0/4] x86: faster mb()+documentation tweaks Michael S. Tsirkin
2016-01-26 8:26 ` Boris Petkov
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=20160114113934.GC19941@pd.tnic \
--to=bp@alien8.de \
--cc=dave@stgolabs.net \
--cc=dbueso@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mst@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@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