Re: [PATCH] NUMA spinlock [BZ #23962]

["H.J. Lu" <hjl dot tools at gmail dot com>]

On Thu, Jan 10, 2019 at 8:32 AM Florian Weimer <fweimer@redhat.com> wrote:
>
> * Carlos O'Donell:
>
> > My opinion is that for the health and evolution of a NUMA-aware spinlock
> > and MCS lock, that we should create a distinct project and library that
> > should have those locks, and then work to put them into downstream
> > distributions. This will support key users being able to use supported
> > versions of those libraries, and give the needed feedback about the API
> > and the performance. It may take 1-2 years to get that feedback and every
> > piece of feedback will improve the final API/ABI we put into glibc or
> > even into the next ISO C standard as pat of the C thread interface.
>
> I think it's something taht could land in tbb, for which many
> distributions already have mechanisms to ship updated versions after a
> release.

We will work on a standalone library:

https://gitlab.com/numa-spinlock/numa-spinlock

The implementation is done.  But many pieces are missing:

1. Documentation.
2. Make tests portable for non-x86 platforms.
3. Do we need symbol versioning?
4. ...

We are looking for contributors.

Thanks.

-- 
H.J.