From: Benedikt Spranger <b.spranger@linutronix.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
rvk@prodmail.net, Robert Hancock <hancockr@shaw.ca>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Thread_Id
Date: Thu, 14 Jul 2005 15:08:24 +0200 [thread overview]
Message-ID: <1121346504.5104.13.camel@atlas.tec.linutronix.de> (raw)
In-Reply-To: <20050714123917.GE4884@devserv.devel.redhat.com>
> And you certainly shouldn't be using gettid () syscall in NPTL, as it
> is just an implementation detail that there is a 1:1 mapping between
> NPTL threads and kernel threads. It can change at any time.
Maybe I missed the point, but I thought the 1:1 mapping between NPTL
threads and kernel threads is one of the advantages of NPTL and the idea
of a userland scheduler is quite dead.
So please let gettid do what man gettid assures:
gettid returns the thread ID of the current process. This is equal to
the process ID (as returned by getpid(2)), unless the process is part
of a thread group (created by specifying the CLONE_THREAD flag to the
clone(2) system call). All processes in the same thread group have the
same PID, but each one has a unique TID.
Bene
next prev parent reply other threads:[~2005-07-14 13:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4mfcK-UT-25@gated-at.bofh.it>
[not found] ` <4mUJ1-5ZG-23@gated-at.bofh.it>
2005-07-06 2:47 ` Thread_Id Robert Hancock
2005-07-14 5:33 ` Thread_Id RVK
2005-07-14 7:45 ` Thread_Id Arjan van de Ven
2005-07-14 10:06 ` Thread_Id RVK
2005-07-14 10:30 ` Thread_Id Arjan van de Ven
2005-07-14 11:20 ` Thread_Id RVK
2005-07-14 12:25 ` Thread_Id Arjan van de Ven
2005-07-14 12:39 ` Thread_Id Jakub Jelinek
2005-07-14 13:08 ` Benedikt Spranger [this message]
2005-07-14 13:49 ` Thread_Id RVK
2005-07-14 10:39 ` Thread_Id Ian Campbell
2005-07-14 11:02 ` Thread_Id RVK
2005-07-14 11:16 ` Thread_Id Ian Campbell
2005-07-14 11:24 ` Thread_Id RVK
2005-07-14 23:02 ` Thread_Id J.A. Magallon
2005-07-15 6:09 ` Thread_Id RVK
2005-07-15 6:18 ` Thread_Id Ian Campbell
2005-07-14 14:28 ` Thread_Id Robert Hancock
2005-07-23 15:02 [PATCH] quieten OOM killer noise Anton Blanchard
2005-07-05 12:15 ` Thread_Id RVK
2005-07-05 12:55 ` Thread_Id Arjan van de Ven
2005-07-07 12:43 ` Thread_Id Benedikt Spranger
2005-07-14 5:31 ` Thread_Id RVK
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=1121346504.5104.13.camel@atlas.tec.linutronix.de \
--to=b.spranger@linutronix.de \
--cc=arjan@infradead.org \
--cc=hancockr@shaw.ca \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rvk@prodmail.net \
/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
all inboxes | Powered by JetHome®