Messages in this thread | | | Date | Thu, 17 Sep 2009 11:41:38 +0900 | From | KAMEZAWA Hiroyuki <> | Subject | [PATCH 0/3][mmotm] showing size of kcore (Was Re: kcore patches (was Re: 2.6.32 -mm merge plans) |
| |
On Wed, 16 Sep 2009 20:17:52 +0900 (JST) "KAMEZAWA Hiroyuki" <kamezawa.hiroyu@jp.fujitsu.com> wrote: > But for now, we have to use some fixed value....and using above > patch for 2.6.31 is not very bad. >
This set is based on mmotm's kcore patch stack. So, just for discussing.
[1/3] ... clean up (tiny bug fix) [2/3] ... show size of /proc/kcore [3/3] ... update kcore size at memory hotplug.
After patches, /proc/kcore's size is as following. == [kamezawa@bluextal mmotm-2.6.31-Sep14]$ ls -l /proc/kcore -r-------- 1 root root 140737486266368 2009-09-17 11:53 /proc/kcore [kamezawa@bluextal mmotm-2.6.31-Sep14]$ == I'm not sure how this value is useful...but..hmm..better than zero ? (The reason of very big value is because vmalloc area is too large.)
Thanks, -Kame
| |