Prev: [PATCH 07/11] USB: musb: fix musb_platform_set_mode() definition
Next: [PATCH 1/3] usb console: fix mutex lock regression
From: KAMEZAWA Hiroyuki on 16 Sep 2009 22:50
On Wed, 16 Sep 2009 20:17:52 +0900 (JST)
"KAMEZAWA Hiroyuki" <kamezawa.hiroyu(a)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(a)bluextal mmotm-2.6.31-Sep14]$ ls -l /proc/kcore
-r-------- 1 root root 140737486266368 2009-09-17 11:53 /proc/kcore
[kamezawa(a)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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH 07/11] USB: musb: fix musb_platform_set_mode() definition
Next: [PATCH 1/3] usb console: fix mutex lock regression