From: RVK <rvk@prodmail.net>
To: Benedikt Spranger <b.spranger@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Thread_Id
Date: Thu, 14 Jul 2005 11:01:35 +0530 [thread overview]
Message-ID: <42D5F8B7.2070508@prodmail.net> (raw)
In-Reply-To: <1120740201.4988.53.camel@atlas.tec.linutronix.de>
You are right Ben....gettid() will do for me. Previously for 2.4.x
(2.4.18)thread libraries I normally was using pthread_self().
Raghu
Benedikt Spranger wrote:
>Hi,
>
>
>>Can anyone suggest me how to get the threadId using 2.6.x kernels.
>>pthread_self() does not work and returns some -ve integer.
>>
>>
>
>Let me guess: You are looking for get_tid() :-)
>
>Bene
>.
>
>
>
next prev parent reply other threads:[~2005-07-14 5:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-23 15:02 [PATCH] quieten OOM killer noise Anton Blanchard
2005-07-03 17:26 ` Daniel Walker
2005-07-03 17:38 ` Anton Blanchard
2005-07-03 20:12 ` Daniel Walker
2005-07-04 12:01 ` Al Boldi
2005-07-09 5:09 ` Paul Jackson
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 ` RVK [this message]
[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 ` Thread_Id Benedikt Spranger
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
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=42D5F8B7.2070508@prodmail.net \
--to=rvk@prodmail.net \
--cc=b.spranger@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
/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