From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Bugs found while working on global thread list
Date: Fri, 15 Feb 2019 14:03:12 -0500 [thread overview]
Message-ID: <20190215190312.GD23599@brightrain.aerifal.cx> (raw)
In-Reply-To: <20190215183836.GC23599@brightrain.aerifal.cx>
3. Not exactly a bug, but found looking at cruft/bloat in struct
pthread: the start function pointer and argument are reused in a
hackish way for timer threads. There are actually a lot of ugly hacks
in the whole way SIGEV_THREAD timers are implemented, that could be
eliminated by either waiting for the signal (rather than handling it)
or doing away with use of signals and kernel timers entirely for
SIGEV_THREAD, and instead implementing it all in userspace with
clock_nanosleep.
prev parent reply other threads:[~2019-02-15 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 18:38 Rich Felker
2019-02-15 19:03 ` Rich Felker [this message]
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=20190215190312.GD23599@brightrain.aerifal.cx \
--to=dalias@libc.org \
--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).