[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130517050126.GZ20323@brightrain.aerifal.cx>
Date: Fri, 17 May 2013 01:01:26 -0400
From: Rich Felker <dalias@...ifal.cx>
To: musl@...ts.openwall.com
Subject: Re: cpuset/affinity interfaces and TSX lock elision in musl
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
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
