On Tue 13-09-16 14:04:49, Janani Ravichandran wrote: > > > On Sep 12, 2016, at 8:16 AM, Michal Hocko <mhocko@xxxxxxxxxx> wrote: > > > > Hi, > > Hello Michal, > > > I am sorry I didn't follow up on the previous submission. > > That’s alright :) > > > I find this > > _really_ helpful. It is great that you could build on top of existing > > tracepoints but one thing is not entirely clear to me. Without a begin > > marker in __alloc_pages_nodemask we cannot really tell how long the > > whole allocation took, which would be extremely useful. Or do you use > > any graph tracer tricks to deduce that? > > I’m using the function graph tracer to see how long __alloc_pages_nodemask() > took. How can you map the function graph tracer to a specif context? Let's say I would like to know why a particular allocation took so long. Would that be possible? -- Michal Hocko SUSE Labs -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>