From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18898 invoked by alias); 10 Jan 2019 16:41:10 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 18876 invoked by uid 89); 10 Jan 2019 16:41:10 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=health, Hx-languages-length:900 X-HELO: mail-qt1-f194.google.com Return-Path: Subject: Re: [PATCH] NUMA spinlock [BZ #23962] To: Florian Weimer Cc: "H.J. Lu" , Szabolcs Nagy , libc-alpha References: <20181226025019.38752-1-ling.ma@MacBook-Pro-8.local> <7D8A82D6-6F0A-4860-856A-EB0C8CD13E9C@antfin.com> <0a474516-b8c8-48cf-aeea-e57c77b78cbd.ling.ml@antfin.com> <8c67f319-31bf-818b-4a89-66d25328026e@arm.com> <87ef9oe0zf.fsf@oldenburg2.str.redhat.com> <97275e72-dc1b-fc2a-d908-b94ef7064ed8@redhat.com> <87y37siic1.fsf@oldenburg2.str.redhat.com> From: Carlos O'Donell Openpgp: preference=signencrypt Message-ID: <479415e1-3aba-b456-fc67-0614fbd462a1@redhat.com> Date: Thu, 10 Jan 2019 16:41:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.3.1 MIME-Version: 1.0 In-Reply-To: <87y37siic1.fsf@oldenburg2.str.redhat.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2019-01/txt/msg00231.txt.bz2 On 1/10/19 11:32 AM, Florian Weimer 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. Absolutely. That's a great idea. -- Cheers, Carlos.