public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave McCracken <dmccr@us.ibm.com>
To: Andi Kleen <ak@suse.de>
Cc: Terje Eggestad <terje.eggestad@scali.no>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] processes with shared vm
Date: Fri, 17 Aug 2001 16:15:50 -0500	[thread overview]
Message-ID: <6400000.998082950@baldur> (raw)
In-Reply-To: <20010817225537.B2429@gruyere.muc.suse.de>
In-Reply-To: <997973469.7632.10.camel@pc-16.suse.lists.linux.kernel> <oupelqbw0z4.fsf@pigdrop.muc.suse.de> <998038019.7627.21.camel@pc-16.office.scali.no> <36530000.998058370@baldur> <20010817225537.B2429@gruyere.muc.suse.de>

--On Friday, August 17, 2001 22:55:37 +0200 Andi Kleen <ak@suse.de> wrote:

> Even with a tgid you would need some way to avoid its counter wrapping
> and getting reused.

While in theory the pid that is used for tgid should never die while the 
thread group exists, this case needs to be handled for thread groups in 
general.  The number shouldn't be re-used for a pid as long as it's in use 
as a tgid.

> Also gtop should display correct results even with the programs
> that don't use CLONE_THREAD.

Are there any programs that use CLONE_VM and not CLONE_THREAD?

Actually I think we should make tgid visible in /proc in general because 
it's a useful thing to know, whether it's the right mechanism for gtop or 
not.  I'll work up a patch.

Dave McCracken

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


  reply	other threads:[~2001-08-17 21:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <997973469.7632.10.camel@pc-16.suse.lists.linux.kernel>
2001-08-17  8:21 ` [PATCH] processes with shared vm Andi Kleen
2001-08-17  8:31   ` Robert Love
2001-08-17  8:46   ` Terje Eggestad
2001-08-17 14:26     ` Dave McCracken
2001-08-17 20:55       ` Andi Kleen
2001-08-17 21:15         ` Dave McCracken [this message]
2001-08-18 13:29           ` Terje Eggestad
2001-08-31 23:53           ` Mike Touloumtzis
     [not found] <Pine.LNX.4.10.10108171428450.21522-100000@coffee.psychology.mcmaster.ca>
     [not found] ` <Pine.LNX.4.10.10108171428450.21522-100000@coffee.psychology.mcm aster.ca>
2001-08-17 14:39   ` Dave McCracken
2001-08-17  7:50 Terje Eggestad
2001-08-17  7:56 ` Robert Love
2001-08-17  8:04   ` Terje Eggestad
2001-08-17  8:08     ` Robert Love
2001-08-17  8:15       ` Terje Eggestad
2001-08-17 12:26         ` michael
2001-08-18 14:15           ` Terje Eggestad
2001-08-19  6:24             ` Albert D. Cahalan
2001-08-19 12:23               ` Terje Eggestad
2001-08-19 23:25                 ` Albert D. Cahalan

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=6400000.998082950@baldur \
    --to=dmccr@us.ibm.com \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=terje.eggestad@scali.no \
    /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