From: Rik van Riel <riel@redhat.com>
To: Larry Woodman <lwoodman@redhat.com>
Cc: linux-mm@kvack.org
Subject: Re: [Patch] mm tracepoints
Date: Thu, 19 Mar 2009 11:47:55 -0400 [thread overview]
Message-ID: <49C2692B.20006@redhat.com> (raw)
In-Reply-To: <1237233134.1476.119.camel@dhcp-100-19-198.bos.redhat.com>
Larry Woodman wrote:
> I've implemented several mm tracepoints to track page allocation and
> freeing, various types of pagefaults and unmaps, and critical page
> reclamation routines. This is useful for debugging memory allocation
> issues and system performance problems under heavy memory loads.
> Thoughts?:
It looks mostly good.
I believe that the vmscan.c tracepoints could be a little
more verbose though, it would be useful to know whether we
are scanning anon or file pages and whether or not we're
doing lumpy reclaim. Possibly the priority level, too.
--
All rights reversed.
--
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-03-19 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 19:52 [Patch] mm tracepoints Larry Woodman
2009-03-19 15:47 ` Rik van Riel [this message]
2009-03-19 15:55 ` Larry Woodman
2009-03-23 18:54 ` Larry Woodman
[not found] <497DD8E5.1040305@nortel.com>
[not found] ` <20090126075957.69b64a2e@infradead.org>
[not found] ` <497F5289.404@nortel.com>
2009-01-27 20:16 ` marching through all physical memory in software Eric W. Biederman
2009-01-28 19:38 ` Pavel Machek
2009-01-30 9:05 ` Nigel Cunningham
[not found] ` <1236291400.1476.50.camel@dhcp-100-19-198.bos.redhat.com>
2009-03-06 21:16 ` [Patch] mm tracepoints Andrew Morton
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=49C2692B.20006@redhat.com \
--to=riel@redhat.com \
--cc=linux-mm@kvack.org \
--cc=lwoodman@redhat.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;
as well as URLs for NNTP newsgroup(s).