From: george anzinger <george@mvista.com>
To: Dave McCracken <dmc@austin.ibm.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel <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 11:50:37 -0700 [thread overview]
Message-ID: <3B815BFD.80D62209@mvista.com> (raw)
In-Reply-To: <E15Yrlh-0006JF-00@the-village.bc.nu> <26210000.998324773@baldur>
Dave McCracken 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.
>
> Dave McCracken
Are you possibly also looking into allocating a small data structure to
the thread group? A place to keep thread group signal info, perhaps?
George
next prev parent reply other threads:[~2001-08-20 18:51 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 ` george anzinger [this message]
2001-08-20 18:59 ` [PATCH] 2.4.9 Make thread group id visible in/proc/<pid>/status 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
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=3B815BFD.80D62209@mvista.com \
--to=george@mvista.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dmc@austin.ibm.com \
--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