public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mtk dot manpages at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/6399] New: gettid() should have a wrapper Date: Mon, 14 Apr 2008 13:04:00 -0000 [thread overview] Message-ID: <20080414130401.6399.mtk.manpages@gmail.com> (raw) Currently, glibc does not provide a wrapper for gettid(). Nevertheless, There are number of corners of the Linux syscall API where the use of Linux thread IDs, as returned by gettid(), is essential: a) the SIGEV_THREAD_ID notification mechanism (a Linux extension) of POSIX timers (timer_create()). b) sched_setaffinity()/sched_getaffinity() can be used to set the CPU affinity of specific threads. c) The F_SETOWN and F_GETOWN commands of fcntl() can specify a thread ID. Given this, it seems time that gettid() should be promoted to full member status in glibc, and have a wrapper provided. -- Summary: gettid() should have a wrapper Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper at redhat dot com ReportedBy: mtk dot manpages at gmail dot com CC: glibc-bugs at sources dot redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=6399 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2008-04-14 13:04 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-04-14 13:04 mtk dot manpages at gmail dot com [this message] 2008-04-14 13:05 ` [Bug libc/6399] " mtk dot manpages at gmail dot com 2008-04-14 14:04 ` drepper at redhat dot com 2008-04-14 14:46 ` mtk dot manpages at gmail dot com 2008-04-16 10:37 ` michael dot kerrisk at gmail dot com
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=20080414130401.6399.mtk.manpages@gmail.com \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.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: linkBe 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).