From: Brett <brettspamacct@fastclick.com>
To: Kevin Kahley <kkahley@cs.uic.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: exclusive memory held by a process
Date: Fri, 03 Oct 2003 16:32:20 -0700 [thread overview]
Message-ID: <3F7E0704.4020009@fastclick.com> (raw)
In-Reply-To: <Pine.GSO.4.10.10310031721300.28068-100000@ernie.cs.uic.edu>
I asked the same question yesterday. If you look in /prod/[pid]/maps
you can see the memory layout per process. Maybe you could find this
information out by looking through the maps files? I didn't get a
response about this but I'm still going to try this.
Good luck,
Brett
Kevin Kahley wrote:
> I am working with a pc system that has no swap space and no hard disk.
> I have direct control over 3 processes on this system and need to
> guarantee that they never use more than 190 MB of memory. I have been
> getting the information about memory usage from /proc/*pid*/status but can
> not seem to make exact sense of what it is reporting. Here are the values
> I am getting:
>
> Name: g
> State: S (sleeping)
> Tgid: 292
> Pid: 292
> PPid: 284
> TracerPid: 0
> Uid: 0 0 0 0
> Gid: 0 0 0 0
> FDSize: 256
> Groups:
> VmSize: 7772 kB
> VmLck: 7772 kB
> VmRSS: 7772 kB
> VmData: 4284 kB
> VmStk: 32 kB
> VmExe: 1028 kB
> VmLib: 1760 kB
> SigPnd: 0000000000000000
> SigBlk: 0000000080000000
> SigIgn: 0000000000010000
> SigCgt: 0000000380000000
> CapInh: 0000000000000000
> CapPrm: 00000000fffffeff
> CapEff: 00000000fffffeff
>
>
> Name: s
> State: S (sleeping)
> Tgid: 288
> Pid: 288
> PPid: 287
> TracerPid: 0
> Uid: 0 0 0 0
> Gid: 0 0 0 0
> FDSize: 32
> Groups:
> VmSize: 83248 kB
> VmLck: 83248 kB
> VmRSS: 83244 kB
> VmData: 81256 kB
> VmStk: 20 kB
> VmExe: 84 kB
> VmLib: 1760 kB
> SigPnd: 0000000000000000
> SigBlk: 0000000080000000
> SigIgn: 0000000000000000
> SigCgt: 7ffffffffffbfeff
> CapInh: 0000000000000000
> CapPrm: 00000000fffffeff
> CapEff: 00000000fffffeff
>
>
> Name: v
> State: S (sleeping)
> Tgid: 248
> Pid: 248
> PPid: 1
> TracerPid: 0
> Uid: 0 0 0 0
> Gid: 0 0 0 0
> FDSize: 32
> Groups:
> VmSize: 85576 kB
> VmLck: 85576 kB
> VmRSS: 77436 kB
> VmData: 74780 kB
> VmStk: 20 kB
> VmExe: 476 kB
> VmLib: 2452 kB
> SigPnd: 0000000000000000
> SigBlk: 0000000080000000
> SigIgn: 0000000000000000
> SigCgt: 00000003e78074ff
> CapInh: 0000000000000000
> CapPrm: 00000000fffffeff
> CapEff: 00000000fffffeff
>
>
> I have read in many places that VmSize is the total in-memory size of the
> running process, but does this include memory that is being shared? I
> thought about adding VmRSS, VmData, and VmStk, but that is greater than
> VmSize? Can anyone tell me what is the amount of memory solely used by a
> process? It's my understanding that my system should crash if these three
> processes exceed 190 MB, but using /proc/*pid* values does not confirm
> this...
>
> please CC me on any responses: kkahley@cs.uic.edu
>
> Thank you much in advance.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2003-10-03 23:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-03 22:34 exclusive memory held by a process Kevin Kahley
2003-10-03 23:32 ` Brett [this message]
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=3F7E0704.4020009@fastclick.com \
--to=brettspamacct@fastclick.com \
--cc=kkahley@cs.uic.edu \
--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