Path: ...!feeds.phibee-telecom.net!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: jseigh Newsgroups: comp.arch Subject: Re: Is Intel exceptionally unsuccessful as an architecture designer? Date: Sun, 22 Sep 2024 07:44:43 -0400 Organization: A noiseless patient Spider Lines: 18 Message-ID: References: <21028ed32d20f0eea9a754fafdb64e45@www.novabbs.org> <20240918190027.00003e4e@yahoo.com> <920c561c4e39e91d3730b6aab103459b@www.novabbs.org> <%dAHO.54667$S9Vb.39628@fx45.iad> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Sun, 22 Sep 2024 13:44:43 +0200 (CEST) Injection-Info: dont-email.me; posting-host="b1159e7e7c889c486126828359848369"; logging-data="2318097"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18kCSUxlgwd3vz3D49pRloe" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:4y9iE8APotqaoGMoM0XM+A5bH+A= In-Reply-To: Content-Language: en-US Bytes: 2429 On 9/21/24 18:49, jseigh wrote: > > Well, we have asymmetric memory barriers now (membarrier() in linux) > so we can get rid of memory barriers in some cases.  For hazard > pointers which used to be a (load, store, mb, load) are now just > a (load, store, load).  Much faster,  from 8.02 nsecs to 0.79 nsecs. > So much so that other things which has heretofore been considered > to add negligible overhead are not so much by comparison.  Which can > be a little annoying because some like using those a lot. > I should correct those timings slightly. The measurements were for a hazard pointer load, a dummy dependent load, and a hazard pointer clear. If I measure w/o the dummy dependent load, the timings go from 7.75 to 0.61 nsecs respectively. Joe Seigh