xfs
[Top] [All Lists]

Re: Very aggressive memory reclaim

To: John Lepikhin <johnlepikhin@xxxxxxxxx>
Subject: Re: Very aggressive memory reclaim
From: Avi Kivity <avi@xxxxxxxxxx>
Date: Tue, 29 Mar 2011 10:59:33 +0200
Cc: Dave Chinner <david@xxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx, linux-mm@xxxxxxxxx
In-reply-to: <AANLkTi==vw7Dy-oK31PxHadwUaDRUUk+TM0ECSZ=chfv@xxxxxxxxxxxxxx>
References: <AANLkTinFqqmE+fTMTLVU-_CwPE+LQv7CpXSQ5+CdAKLK@xxxxxxxxxxxxxx> <20110328215344.GC3008@dastard> <AANLkTi==vw7Dy-oK31PxHadwUaDRUUk+TM0ECSZ=chfv@xxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110307 Fedora/3.1.9-0.39.b3pre.fc14 Lightning/1.0b3pre Thunderbird/3.1.9
On 03/29/2011 09:26 AM, John Lepikhin wrote:
2011/3/29 Dave Chinner<david@xxxxxxxxxxxxx>:

>  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

<Prev in Thread] Current Thread [Next in Thread>