Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 26 Apr 2019 10:38:36 +0300
From:      Konstantin Belousov <kostikbel@gmail.com>
To:        Mark Johnston <markj@freebsd.org>
Cc:        Wojciech Macek <wma@semihalf.com>, Wojciech Macek <wma@freebsd.org>, src-committers <src-committers@freebsd.org>, svn-src-all@freebsd.org, svn-src-head@freebsd.org
Subject:   Re: svn commit: r346593 - head/sys/sys
Message-ID:  <20190426073836.GP12936@kib.kiev.ua>
In-Reply-To: <20190426060456.GA59853@spy>
References:  <201904230636.x3N6aWQK057863@repo.freebsd.org> <20190425040817.GA3789@spy> <CANsEV8ca_y9EGxRQGoi%2BCMbCBn-8cfw_MJcRtujgP7vE0n_JKQ@mail.gmail.com> <20190425082222.GJ12936@kib.kiev.ua> <20190426060456.GA59853@spy>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Apr 26, 2019 at 02:04:56AM -0400, Mark Johnston wrote:
> On Thu, Apr 25, 2019 at 11:22:22AM +0300, Konstantin Belousov wrote:
> > On Thu, Apr 25, 2019 at 07:38:21AM +0200, Wojciech Macek wrote:
> > > Intel does not reorder reads against the condition "if" here. I know for
> > > sure that ARM does, but therestill might be some other architectures that
> > > also suffers such behavior - I just don't have any means to verify.
> > > I remember the discussion for rS302292 where we agreed that this kind of
> > > patches should be the least impacting in perfomrance as possible. Adding
> > > unconditional memory barrier causes significant performance drop on Intel,
> > > where in fact, the issue was never seen.
> > > 
> > Atomic_thread_fence_acq() is nop on x86, or rather, it is compiler memory
> > barrier.  If you need read/read fence on some architectures, I am sure
> > that you need compiler barrier on all.
> 
> To add a bit, one reason to prefer atomic(9) to explicit fences is
> precisely because it issues fences only when required by a given
> CPU architecture.  There is no "unconditional memory barrier" added by
> the diff even without the #ifdef.
Well, atomic_thread_fence_acq() is the explicit fence.  And on x86 it
does add unconditional compiler memory barrier.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190426073836.GP12936>