| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <4D919F75.5070601@redhat.com> Date: Tue, 29 Mar 2011 10:59:33 +0200 From: Avi Kivity <avi@...hat.com> To: John Lepikhin <johnlepikhin@...il.com> CC: Dave Chinner <david@...morbit.com>, linux-kernel@...r.kernel.org, xfs@....sgi.com, linux-mm@...ck.org Subject: Re: Very aggressive memory reclaim On 03/29/2011 09:26 AM, John Lepikhin wrote: > 2011/3/29 Dave Chinner<david@...morbit.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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists