From: PINTU KUMAR <pintu_agarwal@yahoo.com>
To: Stefan Beller <stefanbeller@googlemail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mgorman@suse.de" <mgorman@suse.de>
Subject: Re: Help about calculating total memory consumption during booting
Date: Mon, 30 Dec 2013 17:52:19 -0800 (PST) [thread overview]
Message-ID: <1388454739.81970.YahooMailNeo@web160105.mail.bf1.yahoo.com> (raw)
In-Reply-To: <52C0854D.2090802@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 2291 bytes --]
Hi,
Thanks for the reply, I know about top, but top does not help much in arriving at the total memory consumption.
I need the physical memory usage breakup of each process during bootup, with a segregate of user and kernel allocation.
1) If I add up all "Pss" field in "proc/<PID>/smaps, do I get the total Used memory?
2) Is the Pss value includes the kernel side allocation as well?
3) What fields I should choose from /proc/meminfo" to correctly arrive at the "Used" memory in the system?
4) What about the memory allocation for kernel threads during booting? Why does its Pss/Rss value shows 0 always
I already tried adding up all "PSS" values in every PIDs, but still it does not match any where near to the total used memory in the system.
Please help.
Thanks,
Pintu
>________________________________
> From: Stefan Beller <stefanbeller@googlemail.com>
>To: PINTU KUMAR <pintu_agarwal@yahoo.com>; "linux-mm@kvack.org" <linux-mm@kvack.org>; "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>; "mgorman@suse.de" <mgorman@suse.de>
>Sent: Monday, 30 December 2013 1:55 AM
>Subject: Re: Help about calculating total memory consumption during booting
>
>
>On 29.12.2013 19:17, PINTU KUMAR wrote:
>> Hi,
>>
>> I need help in roughly calculating the total memory consumption in an embedded Linux system just after booting is finished.
>> I know, I can see the memory stats using "free" and "/proc/meminfo"
>>
>> But, I need the breakup of "Used" memory during bootup, for both kernel space and user application.
>>
>> Example, on my ARM machine with 128MB RAM, the free memory reported is roughly:
>> Total: 90MB
>> Used: 88MB
>> Free: 2MB
>> Buffer+Cached: (5+19)MB
>>
>> Now, my question is, how to find the breakup of this "Used" memory of "88MB".
>> This should include both kernel space allocation and user application allocation(including daemons).
>>
>
>http://www.linuxatemyram.com/ dont panic ;)
>
>How about htop, top or
>"valgrind --tool massif"
>
>
>
>
>
>--
>To unsubscribe, send a message with 'unsubscribe linux-mm' in
>the body to majordomo@kvack.org. For more info on Linux MM,
>see: http://www.linux-mm.org/ .
>Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
>
>
>
[-- Attachment #2: Type: text/html, Size: 5587 bytes --]
next prev parent reply other threads:[~2013-12-31 1:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-29 18:17 PINTU KUMAR
2013-12-29 20:25 ` Stefan Beller
2013-12-31 1:52 ` PINTU KUMAR [this message]
2013-12-31 1:54 ` PINTU KUMAR
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=1388454739.81970.YahooMailNeo@web160105.mail.bf1.yahoo.com \
--to=pintu_agarwal@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=stefanbeller@googlemail.com \
/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