public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave McCracken <dmccr@us.ibm.com>
To: Terje Eggestad <terje.eggestad@scali.no>, Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] processes with shared vm
Date: Fri, 17 Aug 2001 09:26:10 -0500	[thread overview]
Message-ID: <36530000.998058370@baldur> (raw)
In-Reply-To: <998038019.7627.21.camel@pc-16.office.scali.no>
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>


--On Friday, August 17, 2001 10:46:59 +0200 Terje Eggestad 
<terje.eggestad@scali.no> wrote:

> hought of all that, yes ps will have O(n^2) BUT ONLY FOR CLONED PROCS.
> How many cloned procs do you usually have????
>
> Even if I agree that there should be a linked list of all the cloned
> procs, it means major changes to the data structs in the kernel.
>
> With the number of threaded programs out there, this is "good enough".

There is a simpler way to do this.  All tasks belong to a thread group, and 
while thread groups are connected via a different clone flag 
(CLONE_THREAD), in practice CLONE_THREAD and CLONE_VM are generally used 
together.  It would be trivial to add TGID to the information in /proc, 
then assume all tasks with the same TGID have the same VM as well.  It 
would be just one more line in the /proc output and not require any 
additional overhead.

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 14:26 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 [this message]
2001-08-17 20:55       ` Andi Kleen
2001-08-17 21:15         ` Dave McCracken
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=36530000.998058370@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