Add trace event for munmap
in [Kernel]
|
Prev: [PATCH] firewire: core: integrate software-forced bus resets with bus management
Next: 2.6.35-rc* regression: ERROR: Unable to locate IOAPIC for GSI *
From: Rik van Riel on 8 Jul 2010 10:20 On 07/08/2010 10:05 AM, 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. Sounds like a useful trace point to me. > Signed-of-by: Eric B Munson<emunson(a)mgebm.net> Reviewed-by: Rik van Riel <riel(a)redhat.com> -- All rights reversed -- 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/
From: Peter Zijlstra on 8 Jul 2010 10:30 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? -- 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/
From: Eric B Munson on 8 Jul 2010 11:00 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. -- Eric B Munson IBM Linux Technology Center emunson(a)mgebm.net
From: Christoph Hellwig on 8 Jul 2010 13:40 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 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/
From: Peter Zijlstra on 8 Jul 2010 13:50
On Thu, 2010-07-08 at 13:35 -0400, Christoph Hellwig wrote: > What kind of infrastructure is perf using for recording > mmap()/mremap()/brk() information? A direct hook into mmap_region(), see perf_event_mmap(). We used to only track VM_EXEC regions, but these days we can also track data regions (although it wouldn't track mremap and brk I think). We need the VM_EXEC maps to make sense of the instruction pointer samples. Eric recently added support for !VM_EXEC mmap() in order to interpret linear addresses provided by things like the software pagefault events and certain powerpc hardware events. -- 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/ |