public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: michael@optusnet.com.au
To: Terje Eggestad <terje.eggestad@scali.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] processes with shared vm
Date: 17 Aug 2001 22:26:25 +1000	[thread overview]
Message-ID: <m1y9oic1ou.fsf@mo.optusnet.com.au> (raw)
In-Reply-To: <997973469.7632.10.camel@pc-16> <998035017.663.13.camel@phantasy> <998035444.7627.4.camel@pc-16.office.scali.no> <998035750.1013.15.camel@phantasy> <998036130.7627.12.camel@pc-16.office.scali.no>
In-Reply-To: Terje Eggestad's message of "17 Aug 2001 10:15:30 +0200"



Why not just print out the address of the 'mm_struct'? 

That lets 'ps' treat the address as a cookie, and
thus count the number of occurences of each vm.

This has the additional advantages of:

* moving the intelligence out to the app
* reducing the kernel size, and
* make it easy to find out exactly which processes
are using which vm. (you just search for all occurences
of the cookie).

Michael.


Terje Eggestad <terje.eggestad@scali.no> writes:
> --=-L6iLOYILsDzljNLIi035
> Content-Type: text/plain
> Content-Transfer-Encoding: 7bit
> --- array.c.orig	Mon Mar 19 21:34:55 2001
> +++ array.c	Thu Aug 16 16:33:56 2001
> @@ -50,6 +50,12 @@
>   * Al Viro & Jeff Garzik :  moved most of the thing into base.c and
>   *			 :  proc_misc.c. The rest may eventually go into
>   *			 :  base.c too.
> + *
> + * Terje Eggestad    :  added in /proc/<pid>/status a VmClones: n
> + *                   :  that tells how many proc that uses the same VM (mm_struct).
> + *                   :  if there are clones add another field VmFirstClone with the
> + *                   :  clone with the lowest pid. Needed for things like gtop that adds 
> + *                   :  mem usage of groups of proc, or else they add up the usage of threads.
>   */

  reply	other threads:[~2001-08-17 12:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-17  7:50 [PATCH] processes with shared vm 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 [this message]
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
     [not found] <997973469.7632.10.camel@pc-16.suse.lists.linux.kernel>
2001-08-17  8:21 ` 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
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

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=m1y9oic1ou.fsf@mo.optusnet.com.au \
    --to=michael@optusnet.com.au \
    --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