From: Christoph Hellwig <hch@infradead.org>
To: Eric B Munson <ebmunson@us.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Eric B Munson <emunson@mgebm.net>,
akpm@linux-foundation.org, mingo@redhat.com,
hugh.dickins@tiscali.co.uk, riel@redhat.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
anton@samba.org
Subject: Re: [PATCH] Add trace event for munmap
Date: Thu, 8 Jul 2010 13:35:15 -0400 [thread overview]
Message-ID: <20100708173515.GA11652@infradead.org> (raw)
In-Reply-To: <20100708144407.GA8141@us.ibm.com>
On Thu, Jul 08, 2010 at 03:44:07PM +0100, Eric B Munson wrote:
> On Thu, 08 Jul 2010, Peter Zijlstra wrote:
>
> > On Thu, 2010-07-08 at 15:05 +0100, Eric B Munson wrote:
> > > This patch adds a trace event for munmap which will record the starting
> > > address of the unmapped area and the length of the umapped area. This
> > > event will be used for modeling memory usage.
> >
> > Does it make sense to couple this with a mmap()/mremap()/brk()
> > tracepoint?
> >
>
> We were using the mmap information collected by perf, but I think
> those might also be useful so I will send a followup patch to add
> them.
What kind of infrastructure is perf using for recording
mmap()/mremap()/brk() information?
--
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:[~2010-07-08 17:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 14:05 [PATCH] Add trace event for munmap Eric B Munson
2010-07-08 14:15 ` Rik van Riel
2010-07-08 14:22 ` Peter Zijlstra
2010-07-08 14:44 ` Eric B Munson
2010-07-08 17:35 ` Christoph Hellwig [this message]
2010-07-08 17:48 ` Peter Zijlstra
2010-07-08 17:51 ` Christoph Hellwig
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=20100708173515.GA11652@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=anton@samba.org \
--cc=ebmunson@us.ibm.com \
--cc=emunson@mgebm.net \
--cc=hugh.dickins@tiscali.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=riel@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).