From: "Arunkumar" <akumars@omnesysindia.com>
To: linux-mm <linux-mm@kvack.org>
Subject: Doubt about statm_pgd_range patch
Date: Wed, 4 Feb 2004 12:23:44 +0530 [thread overview]
Message-ID: <018601c3eaeb$a1ba2150$250010ac@CLNT37> (raw)
In-Reply-To: <38540000.1075876171@[10.10.2.4]>
Hi,
I had a doubt as to why the vsize reported in /proc/nn/stat
and /proc/nn/statm differs. My search on the topic lead me
to the details about the stam_pgd_range sucks patch
(William Lee Irwin III) which is now included the latest
2.6.xxx RC mm series.
I guess if i make similar changes to proc/array.c according
to those patches, both stat and statm will report the vsize
in the same manner -
(vma->vm_end - vma->vm_start)
with statm reporting in pages and stat reporting in bytes
If this is the case can i report vsize of my process from
/proc/self/stat value to be more correct than that in statm?
(iam running 2.4 kernel and stat already reports vsize in
this manner in 2.4 kernels right ?)
Or does this patch need any other changes in kernel
vm structures etc ?
Thanks
Arun
--
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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-02-04 6:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 4:46 Active Memory Defragmentation: Our implementation & problems Alok Mooley
2004-02-03 21:26 ` Dave Hansen
2004-02-03 22:26 ` Martin J. Bligh
2004-02-04 5:09 ` Alok Mooley
2004-02-04 5:24 ` Mike Fedyk
2004-02-04 5:54 ` Dave Hansen
2004-02-04 6:05 ` Martin J. Bligh
2004-02-04 6:22 ` Dave Hansen
2004-02-04 6:29 ` Martin J. Bligh
2004-02-04 6:40 ` Dave Hansen
2004-02-04 7:17 ` Martin J. Bligh
2004-02-04 8:30 ` Andrew Morton
2004-02-04 6:53 ` Arunkumar [this message]
2004-02-04 6:57 ` IWAMOTO Toshihiro
2004-02-04 7:10 ` Dave Hansen
2004-02-04 7:50 ` IWAMOTO Toshihiro
2004-02-04 10:33 ` Hirokazu Takahashi
2004-02-04 18:33 ` Alok Mooley
2004-02-04 18:46 ` Dave Hansen
2004-02-04 18:54 ` Alok Mooley
2004-02-04 19:07 ` Richard B. Johnson
2004-02-04 19:18 ` Alok Mooley
2004-02-04 19:33 ` Richard B. Johnson
2004-02-05 5:07 ` Alok Mooley
2004-02-05 19:03 ` Pavel Machek
2004-02-04 19:35 ` Dave McCracken
2004-02-04 21:59 ` Timothy Miller
2004-02-04 23:24 ` Dave Hansen
2004-02-05 16:32 ` Dave McCracken
2004-02-04 19:37 ` Timothy Miller
2004-02-04 19:43 ` Dave Hansen
2004-02-04 19:59 ` Richard B. Johnson
2004-02-04 19:56 ` Dave Hansen
2004-02-05 5:19 ` Alok Mooley
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='018601c3eaeb$a1ba2150$250010ac@CLNT37' \
--to=akumars@omnesysindia.com \
--cc=linux-mm@kvack.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