This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Principles for API sources
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Joseph Myers <joseph at codesourcery dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Mon, 16 Nov 2015 12:40:36 -0500
- Subject: Re: Principles for API sources
- Authentication-results: sourceware.org; auth=none
- References: <alpine dot DEB dot 2 dot 10 dot 1511061326480 dot 10753 at digraph dot polyomino dot org dot uk> <5647941C dot 2020200 at redhat dot com> <alpine dot DEB dot 2 dot 10 dot 1511161043590 dot 25844 at digraph dot polyomino dot org dot uk>
On 11/16/2015 05:47 AM, Joseph Myers wrote:
> On Sat, 14 Nov 2015, Carlos O'Donell wrote:
>
>> Given the caveat that some specific syscalls are simply not useful and
>> or conflict with existing APIs and the best example I have is the often
>> requested gettid() which I think *could* exist, but we need an API design
>> review to harmonize this with existing pid_t based interfaces before
>> letting users use it and get confused.
>
> gettid and pthread_gettid_np are, I think, clearly useful because of other
> kernel APIs working with tids. It's things like set_thread_area and
> set_robust_list that should likely be excluded for conflicting with glibc.
I concede that perhaps the best we can do there is add the wrappers and
begin a documentation of how tid, pid, and pthread_t interact and the
interfaces that accept their values as inputs.
Cheers,
Carlos.