From: Florian Weimer <fweimer@redhat.com>
To: Trevor Gross via Libc-help <libc-help@sourceware.org>
Cc: Trevor Gross <tmgross@umich.edu>, jistone@redhat.com
Subject: Re: RFC: A way to get a TID from a pthread_t handler
Date: Thu, 11 Jan 2024 22:32:25 +0100 [thread overview]
Message-ID: <87a5pbv9na.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CALNs47sOjkNckJpv_FZx_N=q_WnMtgBo9OR2hMmq-3-anvS3aA@mail.gmail.com> (Trevor Gross via Libc-help's message of "Thu, 11 Jan 2024 01:10:18 -0500")
* Trevor Gross via Libc-help:
> It seems like there isn't a good way to get the thread ID from a
> pthread_t. If you are within the thread then you can call gettid(),
> but there is no public API to get a spawned thread's TID after calling
> pthread_create().
>
> This value is stored in the pthread, so a new public function could
> just be a basic getter:
>
> pid_t pthread_gettid(pthread_t threadid)
> {
> struct pthread *pd = (struct pthread *) threadid;
> return pd->tid;
> }
>
> Would an addition like this likely get accepted? Or is there anything
> overlooked about an easier way to recover the spawned thread's TID?
We should probably make a copy of the TID inside pthread_create and
return that from pthread_gettid, instead of pd->tid that might be
cleared by the kernel upon thread exit. This way, pthread_gettid
remains valid until pthread_join is called.
Thanks,
Florian
next prev parent reply other threads:[~2024-01-11 21:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 6:10 Trevor Gross
2024-01-11 18:23 ` Carlos O'Donell
2024-01-12 7:29 ` Trevor Gross
2024-01-11 21:32 ` Florian Weimer [this message]
2024-01-12 7:55 ` Trevor Gross
2024-01-15 19:47 ` Adhemerval Zanella Netto
2024-01-15 19:54 ` Florian Weimer
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=87a5pbv9na.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=jistone@redhat.com \
--cc=libc-help@sourceware.org \
--cc=tmgross@umich.edu \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).