mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Jens Gustedt <jens.gustedt@inria.fr>
To: musl@lists.openwall.com
Subject: Re: Multi-threaded performance progress
Date: Tue, 26 Aug 2014 09:04:14 +0200	[thread overview]
Message-ID: <1409036654.4835.14.camel@eris.loria.fr> (raw)
In-Reply-To: <20140826034321.GA13999@brightrain.aerifal.cx>

[-- Attachment #1: Type: text/plain, Size: 1745 bytes --]

Am Montag, den 25.08.2014, 23:43 -0400 schrieb Rich Felker:
> This release cycle looks like it's going to be huge for multi-threaded
> performance issues. So far the cumulative improvement on my main
> development system, as measured by the cond_bench.c by Timo Teräs, is
> from ~250k signals in 2 seconds up to ~3.7M signals in 2 seconds.
> That's comparable to what glibc gets on similar hardware with a cond
> var implementation that's much less correct. The improvements are a
> result of adding private futex support, redesigning the cond var
> implementation, and improvements to the spin-before-futex-wait
> behavior.

Very impressive!

> We're near the end of my planned time frame for this release cycle,
> but I'm still interested in working with Jens to get C11 threads into
> this release if possible, so I'll probably extend it for a while
> still.

I would be very much in favor of getting C11 in one version or another
into the current release, as you said. In any case, it would be good
if we could claim support for C11 for that release. That would be
another item where musl could claim to be first, at least before
glibc. There is not much missing, I think. Come to mind:

 - one or two simple functions, such as the timespec_get that I posted
 - if we don't have C11 threads the feature test macro __STDC NO_THREAD__
 - perhaps some other feature test macros for unsupported features

Jens

-- 
:: INRIA Nancy Grand Est ::: AlGorille ::: ICube/ICPS :::
:: ::::::::::::::: office Strasbourg : +33 368854536   ::
:: :::::::::::::::::::::: gsm France : +33 651400183   ::
:: ::::::::::::::: gsm international : +49 15737185122 ::
:: http://icube-icps.unistra.fr/index.php/Jens_Gustedt ::



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2014-08-26  7:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26  3:43 Rich Felker
2014-08-26  7:04 ` Jens Gustedt [this message]
2014-08-26 10:44   ` Szabolcs Nagy
2014-08-26 11:09     ` Jens Gustedt
2014-08-26 16:35   ` Jens Gustedt
2014-08-26 17:32     ` Rich Felker
2014-08-26 17:53     ` Rich Felker
2014-08-26 18:30       ` Jens Gustedt
2014-08-26 19:05         ` Rich Felker
2014-08-26 19:34           ` Jens Gustedt
2014-08-26 20:26             ` Rich Felker
2014-08-26 21:15               ` Jens Gustedt
2014-08-26 21:36                 ` Rich Felker
2014-08-27  9:53                   ` Jens Gustedt
2014-08-27 16:47                     ` Rich Felker

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=1409036654.4835.14.camel@eris.loria.fr \
    --to=jens.gustedt@inria.fr \
    --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).