On 13.02.2019 15:08, Martin Pieuchot wrote:
+ val = rwlock->value;
+ if (val == UNLOCKED || (val & WAITING))
+ break;
+
+ SPIN_WAIT();
+ }
+
+ while ((error = _rthread_rwlock_tryrdlock(rwlock)) == EBUSY) {
+
On 2019-01-30, Martin Pieuchot wrote:
> Newer version with fewer atomics and some barrier corrections as pointed
> out by visa@.
This has now gone through a full amd64 package build without problems.
--
Christian "naddy" Weisgerber na...@mips.inka.de
On 12/02/19(Tue) 23:25, Paul Irofti wrote:
> On Wed, Jan 30, 2019 at 12:29:20PM -0200, Martin Pieuchot wrote:
> > On 28/01/19(Mon) 14:57, Martin Pieuchot wrote:
> > > Summer is really warm here. No need to make my machines hotter by
> > > spinning a lot. So here's a futex(2) based pthread_rwlock*
On Wed, Jan 30, 2019 at 12:29:20PM -0200, Martin Pieuchot wrote:
> On 28/01/19(Mon) 14:57, Martin Pieuchot wrote:
> > Summer is really warm here. No need to make my machines hotter by
> > spinning a lot. So here's a futex(2) based pthread_rwlock*
> > implementation. I should look familiar to tho
On Thu, Feb 07, 2019 at 06:37:35PM +, Stuart Henderson wrote:
> On 2019/01/30 12:29, Martin Pieuchot wrote:
> > On 28/01/19(Mon) 14:57, Martin Pieuchot wrote:
> > > Summer is really warm here. No need to make my machines hotter by
> > > spinning a lot. So here's a futex(2) based pthread_rwloc
On 2019/01/30 12:29, Martin Pieuchot wrote:
> On 28/01/19(Mon) 14:57, Martin Pieuchot wrote:
> > Summer is really warm here. No need to make my machines hotter by
> > spinning a lot. So here's a futex(2) based pthread_rwlock*
> > implementation. I should look familiar to those of you that review
On Wed, Jan 30, 2019 at 12:29:20PM -0200, Martin Pieuchot wrote:
> On 28/01/19(Mon) 14:57, Martin Pieuchot wrote:
> > Summer is really warm here. No need to make my machines hotter by
> > spinning a lot. So here's a futex(2) based pthread_rwlock*
> > implementation. I should look familiar to tho
On 28/01/19(Mon) 14:57, Martin Pieuchot wrote:
> Summer is really warm here. No need to make my machines hotter by
> spinning a lot. So here's a futex(2) based pthread_rwlock*
> implementation. I should look familiar to those of you that reviewed
> the mutex & semaphore implementations. It uses