From mboxrd@z Thu Jan 1 00:00:00 1970 From: sahil.agg15@gmail.com (SAHIL) Date: Thu, 12 Mar 2015 07:09:32 +0530 Subject: Tracing allocators of virtual memory and main memory In-Reply-To: <53D6E252-3780-488F-B836-D2D16FF5A74E@gmail.com> References: <53D6E252-3780-488F-B836-D2D16FF5A74E@gmail.com> Message-ID: <512EDEA0-617C-46C7-9851-361F5F5FE4ED@gmail.com> To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org Hi Nicholas Yeah right, pidstat which read /proc gives me VSZ ans RSS but i need to backtrace when VSZ/RSS is high which indicates process is allocating memory which it is not even using. And to modify the question i need to analyze allocations per thread, using /proc will it will also include VSZ RSS of parent.? Regards Sahil Aggarwal > On Mar 11, 2015, at 11:00 PM, Nicholas Krause wrote: > > > >> On March 11, 2015 12:07:29 PM EDT, sahil aggarwal wrote: >> Hi all >> >> If i want to trace the allocators of virtual memory and main memory of >> process using ftrace on which functions i need to enable the probe.? >> >> Currently i have enabled sys_mmap,sys_brk for virtual allocations and >> mm_page_alloc, kmalloc, kmem_cache_alloc for main memory allocation. >> Will this give me whole picture of virtual and main memory >> allocations.? >> >> Thanks >> Regards >> Sahil >> >> ______ > Greetings Sachil, > The best way to do this is find > out the PID of your application > and look for it in /proc as there > should be a directory with the > information your looking for. > Nick >> Kernelnewbies mailing list >> Kernelnewbies at kernelnewbies.org >> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity.