From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/3323 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: cpuset/affinity interfaces and TSX lock elision in musl Date: Fri, 17 May 2013 01:01:26 -0400 Message-ID: <20130517050126.GZ20323@brightrain.aerifal.cx> References: <20130516203658.GW20323@brightrain.aerifal.cx> <1368766151.18069.252@driftwood> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1368766902 15287 80.91.229.3 (17 May 2013 05:01:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 17 May 2013 05:01:42 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-3327-gllmg-musl=m.gmane.org@lists.openwall.com Fri May 17 07:01:42 2013 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1UdCnV-0006dk-3L for gllmg-musl@plane.gmane.org; Fri, 17 May 2013 07:01:41 +0200 Original-Received: (qmail 28253 invoked by uid 550); 17 May 2013 05:01:40 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 28244 invoked from network); 17 May 2013 05:01:40 -0000 Content-Disposition: inline In-Reply-To: <1368766151.18069.252@driftwood> User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:3323 Archived-At: On Thu, May 16, 2013 at 11:49:11PM -0500, Rob Landley wrote: > On 05/16/2013 03:36:58 PM, Rich Felker wrote: > >On Thu, May 16, 2013 at 06:37:01PM +0200, Daniel Cegiełka wrote: > >> 1) Are there any plans to add support for cpuset/affinity > >interfaces? > > > >I sat down to do it one day, and it was so ugly I got sick and put it > >off again. Seriously. There's a huge abundance of CPU_* > >macros/functions for manipulating abstract bitsets, but all "cpu set" > >specific for no good reason. > > > >If anyone wants to volunteer to do these, it would be a big relief to > >me. Some caveats: > > Meh, the data format's trivial. It's just that the documentation is > in an insane place, namely here: It's also the exact same format as fd_set and sigset_t, i.e. the only natural set implementation. What's frustrating is that we have to have 3+ sets of interfaces that do exactly the same thing... Rich