Messages in this thread | | | Date | Tue, 29 Mar 2011 10:59:33 +0200 | From | Avi Kivity <> | Subject | Re: Very aggressive memory reclaim |
| |
On 03/29/2011 09:26 AM, John Lepikhin wrote: > 2011/3/29 Dave Chinner<david@fromorbit.com>: > > > First it would be useful to determine why the VM is reclaiming so > > much memory. If it is somewhat predictable when the excessive > > reclaim is going to happen, it might be worth capturing an event > > trace from the VM so we can see more precisely what it is doiing > > during this event. In that case, recording the kmem/* and vmscan/* > > events is probably sufficient to tell us what memory allocations > > triggered reclaim and how much reclaim was done on each event. > > Do you mean I must add some debug to mm functions? I don't know any > other way to catch such events.
Download and build trace-cmd (git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git), and do
$ trace-cmd record -e kmem -e vmscan -b 30000
Hit ctrl-C when done and post the output file generated in cwd.
-- error compiling committee.c: too many arguments to function
| |