mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: Pedro Giffuni <pfg@FreeBSD.org>
Cc: musl@lists.openwall.com
Subject: Re: FreeBSD's Google Summer of Code 2016
Date: Sat, 5 Mar 2016 18:32:54 -0500	[thread overview]
Message-ID: <20160305233254.GL9349@brightrain.aerifal.cx> (raw)
In-Reply-To: <56DB6095.4060204@FreeBSD.org>

On Sat, Mar 05, 2016 at 05:41:25PM -0500, Pedro Giffuni wrote:
> First of all, great to hear there is interest on the musl side too.
> 
> I think the biggest precedent of porting linux-oriented C libraries
> came from Debian's kFreeBSD. We accomodated a little by for them
> by defining __FreeBSD_kernel__ in sys/param.h.
> 
> While using the optional linux-abi futex in FreeBSD could be an option,
> it is not really the cleanest option. The Debian guys did a port of
> NPTL using regular pthreads:
> 
> http://thread.gmane.org/gmane.linux.debian.ports.bsd/11702
> 
> I am certain this will require more research but it would be useful
> for other ports as well.

Glibc/NPTL has a lot of what I'd call "gratuitous abstraction" (like
the lll stuff) in their pthread primitives which makes this
"possible". I call it gratuitous because it's really really hard to
achieve correct implementations of the pthread sync primitives that
don't have serious corner-case bugs, and it's unlikely that their
abstractions actually suffice to make correct alternate
implementations.

musl does not have any such abstraction. We require a compare-and-swap
operation or equivalent on which arbitrary atomic operations can be
constructed, a futex or equivalent operation that's roughly
while(*addr==expected) sleep(), and implement all the sync primitives
just once on top of these.

In a worst case, futex can be emulated trivially by having wait and
wake both be nops; then everything just spins at 100% cpu load. Of
course this does not give very nice results. It's possible futex could
be emulated better; certainly it can be within a single process where
the futex wait queue could just be implemented in userspace, but
emulating process-shared futexes effectively this way sounds
nontrivial. Since the functionality is already there in the kernel,
though, just exposing it sounds like a much better solution to me.

Rich


  reply	other threads:[~2016-03-05 23:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-05 20:11 Pedro Giffuni
2016-03-05 21:25 ` Rich Felker
2016-03-05 22:41   ` Pedro Giffuni
2016-03-05 23:32     ` Rich Felker [this message]
2016-03-06  0:14       ` Pedro Giffuni
2016-03-06  0:25         ` Rich Felker
2016-03-06  0:31           ` Rich Felker
2016-03-06  1:11             ` Pedro Giffuni
2016-03-06  0:59           ` Pedro Giffuni
2016-03-06  1:08             ` Rich Felker
2016-03-07  8:32           ` Felix Fietkau
2016-03-07 13:06             ` Szabolcs Nagy
2016-03-07 14:22               ` Pedro Giffuni
2016-03-07 13:10             ` Pedro Giffuni

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=20160305233254.GL9349@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    --cc=pfg@FreeBSD.org \
    /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).