This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: AW: RFC: POSIX timers and threads in a realtime context
- From: Zack Weinberg <zackw at panix dot com>
- To: Joseph Myers <joseph at codesourcery dot com>
- Cc: Rich Felker <dalias at libc dot org>, "Warlich, Christof" <christof dot warlich at siemens dot com>, "libc-alpha at sourceware dot org" <libc-alpha at sourceware dot org>
- Date: Tue, 6 Oct 2015 11:37:56 -0400
- Subject: Re: AW: RFC: POSIX timers and threads in a realtime context
- Authentication-results: sourceware.org; auth=none
- References: <6D83E89737156549AEA25EF9ED712C5D158489 at DEFTHW99EK1MSX dot ww902 dot siemens dot net> <20151005160303 dot GK8645 at brightrain dot aerifal dot cx> <6D83E89737156549AEA25EF9ED712C5D1585ED at DEFTHW99EK1MSX dot ww902 dot siemens dot net> <alpine dot DEB dot 2 dot 10 dot 1510061203190 dot 4225 at digraph dot polyomino dot org dot uk> <20151006143203 dot GO8645 at brightrain dot aerifal dot cx> <alpine dot DEB dot 2 dot 10 dot 1510061457370 dot 21786 at digraph dot polyomino dot org dot uk>
On Tue, Oct 6, 2015 at 10:59 AM, Joseph Myers <joseph@codesourcery.com> wrote:
> On Tue, 6 Oct 2015, Rich Felker wrote:
>> This latter approach would not solve the issue being discussed here --
>> a separate/third-party libinux-syscalls could not justifiably inspect
>> the internals of the pthread structure.
>
> Then that needs to be included in the analysis message starting the new
> thread - an explanation of why libinux-syscalls would not be appropriate
> for pthread_gettid_np. (Note that the libinux-syscalls proposal is for a
> library built with glibc and possibly linked in through the libc.so linker
> script, not something third-party.)
It seems to me that Christof's second proposal (add a SIGEV_PTHREAD_ID
that takes a pthread_t) is *much* simpler than doing all this work,
and also far more likely to get standardized.
zw