From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Am?rico_Wang <xiyou.wangcong@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: [PATCH 0/3][mmotm] showing size of kcore (Was Re: kcore patches (was Re: 2.6.32 -mm merge plans)
Date: Thu, 17 Sep 2009 11:41:38 +0900 [thread overview]
Message-ID: <20090917114138.e14a1183.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <1bc66b163326564dafb5a7dd8959fd56.squirrel@webmail-b.css.fujitsu.com>
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
--
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>
next prev parent reply other threads:[~2009-09-17 2:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 9:35 Américo Wang
2009-09-16 11:17 ` KAMEZAWA Hiroyuki
2009-09-17 2:41 ` KAMEZAWA Hiroyuki [this message]
2009-09-17 2:42 ` [PATCH 1/3][mmotm] kcore: more fixes for init KAMEZAWA Hiroyuki
2009-09-17 5:55 ` Américo Wang
2009-09-17 2:44 ` [PATCH 2/3][mmotm] showing size of kcore KAMEZAWA Hiroyuki
2009-09-17 6:02 ` Américo Wang
2009-09-17 6:10 ` [PATCH 2/3][mmotm] showing size of kcore v2 KAMEZAWA Hiroyuki
2009-09-18 2:20 ` Américo Wang
2009-09-17 2:45 ` [PATCH 3/3][mmotm] updateing size of kcore KAMEZAWA Hiroyuki
2009-09-17 6:59 ` Américo Wang
2009-09-17 7:14 ` KAMEZAWA Hiroyuki
2009-09-18 2:05 ` Américo Wang
2009-09-17 3:09 ` kcore patches (was Re: 2.6.32 -mm merge plans) Américo Wang
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=20090917114138.e14a1183.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=xiyou.wangcong@gmail.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