From: miquels@cistron-office.nl (Miquel van Smoorenburg)
To: 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 19:09:16 +0000 (UTC) [thread overview]
Message-ID: <9lrn8s$t23$1@ncc1701.cistron.net> (raw)
In-Reply-To: <E15Yrlh-0006JF-00@the-village.bc.nu> <26210000.998324773@baldur>
In article <26210000.998324773@baldur>,
Dave McCracken <dmc@austin.ibm.com> wrote:
>
>--On Monday, August 20, 2001 17:19:13 +0100 Alan Cox
><alan@lxorguk.ukuu.org.uk> wrote:
>
>> I didnt think anyone was using the broken tgid stuff ?
>
>I was under the impression that the current LinuxThread library does use
>CLONE_THREAD, and I know of at least one project under way that's also
>using it (the NGPT pthread library). The getpid() system call already
>returns tgid instead of pid. I'm also looking into what's involved in
>making tgid more robust.
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.
Mike.
next prev parent reply other threads:[~2001-08-20 19:09 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 ` Miquel van Smoorenburg [this message]
2001-08-20 19:15 ` [PATCH] 2.4.9 Make thread group id visible in /proc/<pid>/status Ulrich Drepper
2001-08-20 19:30 ` Dave McCracken
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='9lrn8s$t23$1@ncc1701.cistron.net' \
--to=miquels@cistron-office.nl \
--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