All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olivier Croquette <ocroquette@free.fr>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Subject: Re: Thread and process dentifiers (CPU affinity, kill)
Date: Fri, 20 May 2005 16:51:10 +0200	[thread overview]
Message-ID: <428DF95E.2070703@free.fr> (raw)
In-Reply-To: <20050520125511.GC23488@csclub.uwaterloo.ca>

Lennart Sorensen wrote:

 > I believe Linux currently implements threads as seperate processes (at
 > least top and ps sees them that way).

> Have you tried NPTL (native posix threading library) which is supposed
> to become the threading standard on linux in the future (if it works
> out)?

Lennart,

 From the beginning we are talking about the present GNU/Linux systems, 
which do already use NTPL in standard. NPTL is no future standard, it is 
present standard.

This means basicly that 50% of your assertions (like the above) are 
wrong, and your conclusions "suffer" from that :)

The point is that if you make a ps on a decent Linux based system, you 
will *NOT* see one process for each thread. Nor they do appear in /proc.

This means there are *NOT* userland processes.

And therefore, you shall *NOT* be able to reference them as such where a 
process ID is required.


  reply	other threads:[~2005-05-20 15:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19 18:00 Thread and process dentifiers (CPU affinity, kill) Olivier Croquette
2005-05-19 18:23 ` Lennart Sorensen
2005-05-19 19:46   ` Chris Friesen
2005-05-20 12:55     ` Lennart Sorensen
2005-05-20 14:51       ` Olivier Croquette [this message]
2005-05-20 16:53         ` Lennart Sorensen
2005-05-20 18:13           ` Miquel van Smoorenburg
2005-05-20 20:12             ` Lennart Sorensen
2005-05-23 12:56               ` Nix
2005-05-20 20:17             ` Olivier Croquette
2005-05-20 20:38               ` Lee Revell

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=428DF95E.2070703@free.fr \
    --to=ocroquette@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.