public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave McCracken <dmccr@us.ibm.com>
To: Miquel van Smoorenburg <miquels@cistron-office.nl>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.4.9 Make thread group id visible in /proc/<pid>/status
Date: Mon, 20 Aug 2001 14:30:52 -0500	[thread overview]
Message-ID: <33840000.998335852@baldur> (raw)
In-Reply-To: <9lrn8s$t23$1@ncc1701.cistron.net>
In-Reply-To: <E15Yrlh-0006JF-00@the-village.bc.nu> <26210000.998324773@baldur> <9lrn8s$t23$1@ncc1701.cistron.net>



--On Monday, August 20, 2001 19:09:16 +0000 Miquel van Smoorenburg 
<miquels@cistron-office.nl> wrote:

> Hmm, I've always been a bit curious about this .. I don't think getpid()
> should return tgid instead of pid. It looks broken to me. Thread groups
> are a good idea, but they should act more like process groups do.
> Switching pid and tgid is something that the LinuxThreads library
> should probably do, but not the kernel. IMHO.
>
> If one really wants CLONE_PID to work, fix CLONE_PID.

I wasn't on the list when getpid() was changed to return tgid.  I don't 
have a strong feeling about it, though it does make pthread semantics 
simpler.

CLONE_PID really isn't the semantic we want, though.  That would make all 
tasks in the process have the same pid, and no way to address a specific 
task.  We'd have to introduce something like a task id or a thread id. 
Having tgid and pid gives us the tools we need, and minimizes the 
compatibility issues.

Dave McCracken

======================================================================
Dave McCracken          IBM Linux Base Kernel Team      1-512-838-3059
dmccr@us.ibm.com                                        T/L   678-3059


      parent reply	other threads:[~2001-08-20 19:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-20 15:39 [PATCH] 2.4.9 Make thread group id visible in /proc/<pid>/status Dave McCracken
2001-08-20 16:19 ` Alan Cox
2001-08-20 16:26   ` Dave McCracken
2001-08-20 18:50     ` [PATCH] 2.4.9 Make thread group id visible in/proc/<pid>/status george anzinger
2001-08-20 18:59       ` Dave McCracken
2001-08-20 19:52         ` george anzinger
2001-08-20 20:03           ` Dave McCracken
2001-08-20 19:09     ` [PATCH] 2.4.9 Make thread group id visible in /proc/<pid>/status Miquel van Smoorenburg
2001-08-20 19:15       ` Ulrich Drepper
2001-08-20 19:30       ` Dave McCracken [this message]

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=33840000.998335852@baldur \
    --to=dmccr@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miquels@cistron-office.nl \
    /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