From: Andrew Morton <akpm@osdl.org>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] counting bounce pages.
Date: Mon, 25 Apr 2005 03:53:57 -0700 [thread overview]
Message-ID: <20050425035357.2919e68f.akpm@osdl.org> (raw)
In-Reply-To: <426CC767.8050507@jp.fujitsu.com>
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
>
> This is a patch for counting bounce pages.
> With this, pages for bounce buffer is coutned and shown in /proc/meminfo.
As it's purely a debug thing, perhaps /proc/vmstat would be a better place
for displaying this info.
> Because pages for bounce buffer are not counted in anywhere,
> sometimes it seems that there are many leaked pages.
> ex)
> I found 1.7GB of bounce buffer pages in a crash dump of ia64 kernel,
> which was passed me to check memory usage. :(
whoops.
> BTW, I'm not sure whether # of bounce buffer should be includeded in Buffers:
> of /proc/meminfo.
No, "Buffers:" is "the number of bytes allocated to blockdevice pagecache".
Usually this is filesystem metadata.
> --- linux-2.6.12-rc2-mm3/fs/proc/proc_misc.c~count_bounce 2005-04-25 12:08:28.000000000 +0900
> +++ linux-2.6.12-rc2-mm3-kamezawa/fs/proc/proc_misc.c 2005-04-25 16:06:39.000000000 +0900
> @@ -114,7 +114,7 @@ static int uptime_read_proc(char *page,
>
> return proc_calc_metrics(page, start, off, count, eof, len);
> }
> -
> +extern atomic_t nr_bounce_pages;
Please always put extern declarations into .h files, with the declaration
visible to the definition and to all users.
> + "Bounce : %8lu kB\n"
There's an unneeded space in there.
prev parent reply other threads:[~2005-04-25 10:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-25 10:33 KAMEZAWA Hiroyuki
2005-04-25 10:53 ` Andrew Morton [this message]
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=20050425035357.2919e68f.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®