mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rob Landley <rob@landley.net>
To: musl@lists.openwall.com
Cc: musl@lists.openwall.com
Subject: Re: cpuset/affinity interfaces and TSX lock elision in musl
Date: Sat, 18 May 2013 23:05:17 -0500	[thread overview]
Message-ID: <1368936317.2611.1@driftwood> (raw)
In-Reply-To: <20130517050126.GZ20323@brightrain.aerifal.cx> (from dalias@aerifal.cx on Fri May 17 00:01:26 2013)

On 05/17/2013 12:01:26 AM, Rich Felker wrote:
> 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...

Inside the kernel it's all the same set interface. It's just glibc that  
decided to add layers.

Rob

  reply	other threads:[~2013-05-19  4:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-16 16:37 Daniel Cegiełka
2013-05-16 20:36 ` Rich Felker
2013-05-17  4:49   ` Rob Landley
2013-05-17  5:01     ` Rich Felker
2013-05-19  4:05       ` Rob Landley [this message]
2013-05-17  7:41   ` Daniel Cegiełka
2013-05-17 11:28     ` Szabolcs Nagy
2013-05-17 17:29       ` Rich Felker
2013-05-19  4:40         ` Rob Landley
2013-05-19 20:51           ` Rich Felker
2013-05-19  4:12     ` Rob Landley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1368936317.2611.1@driftwood \
    --to=rob@landley.net \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).