From: Tomasz Sterna <tomek@xiaoka.com>
To: musl@lists.openwall.com
Subject: Re: [PATCH] add sched_getcpu
Date: Fri, 04 Mar 2016 23:21:49 +0100 [thread overview]
Message-ID: <1457130109.10711.8.camel@xiaoka.com> (raw)
In-Reply-To: <20160302232635.GP9349@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
W dniu 02.03.2016, śro o godzinie 18∶26 -0500, użytkownik Rich Felker
napisał:
> The only safe way to make your own threads is to refrain from using
> libc at all and do your own syscalls. Even calling syscall() may not
> be safe (on i386/glibc it probably uses the vdso syscall pointer from
> TLS); you really need to use asm to make the syscall.
I understand.
Thank you for explaining.
> Is there a reason "pthreads is not a good way to do it"?
The thread API I am implementing differs much to pthreads, which
required a lot of glue code translating one API to another and felt
hand wrenching.
On the other hand implementing it on bare syscalls was refreshingly
simple.
But if I do not want to implement the whole libc with it, I will need
to revisit this idea.
C'est la vie...
--
/o__
(_<^' The man on tops walks a lonely street; the "chain" of command is often a noose.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-03-04 22:21 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 16:49 Nathan Zadoks
2016-02-29 16:57 ` Nathan Zadoks
2016-02-29 16:57 ` Nathan Zadoks
2016-02-29 17:00 ` Nathan Zadoks
2016-02-29 17:23 ` Alexander Monakov
2016-02-29 17:33 ` Alexander Monakov
2016-03-01 13:45 ` [PATCH] add sched_getcpu, with vDSO support Nathan Zadoks
2016-03-01 15:56 ` Nathan Zadoks
2016-03-02 5:55 ` Rich Felker
2016-03-02 16:26 ` [PATCH 0/2] add sched_getcpu, take n+1 Nathan Zadoks
2016-03-02 16:26 ` [PATCH 1/2] add sched_getcpu Nathan Zadoks
2016-03-02 16:26 ` [PATCH 2/2] add sched_getcpu vDSO support Nathan Zadoks
2016-03-03 3:01 ` [PATCH 0/2] add sched_getcpu, take n+1 Rich Felker
2016-02-29 17:49 ` [PATCH] add sched_getcpu nathan
2016-02-29 17:52 ` nathan
2016-02-29 20:17 ` Alexander Monakov
2016-02-29 20:49 ` Nathan Zadoks
2016-02-29 18:38 ` Rich Felker
2016-02-29 19:59 ` Alexander Monakov
2016-02-29 20:05 ` Rich Felker
2016-02-29 20:10 ` Alexander Monakov
2016-02-29 20:17 ` Rich Felker
2016-02-29 21:09 ` Tomasz Sterna
2016-02-29 21:21 ` Nathan Zadoks
2016-02-29 21:30 ` Rich Felker
2016-03-01 20:35 ` Tomasz Sterna
2016-03-01 22:34 ` Rich Felker
2016-03-02 20:46 ` Tomasz Sterna
2016-03-02 21:19 ` Szabolcs Nagy
2016-03-02 23:26 ` Rich Felker
2016-03-04 22:21 ` Tomasz Sterna [this message]
2016-03-04 23:33 ` Rich Felker
2016-03-05 11:40 ` Tomasz Sterna
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=1457130109.10711.8.camel@xiaoka.com \
--to=tomek@xiaoka.com \
--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).