From: Avi Kivity <avi@redhat.com>
To: John Lepikhin <johnlepikhin@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: Very aggressive memory reclaim
Date: Tue, 29 Mar 2011 10:59:33 +0200 [thread overview]
Message-ID: <4D919F75.5070601@redhat.com> (raw)
In-Reply-To: <AANLkTi==vw7Dy-oK31PxHadwUaDRUUk+TM0ECSZ=chfv@mail.gmail.com>
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
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: John Lepikhin <johnlepikhin@gmail.com>
Cc: Dave Chinner <david@fromorbit.com>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com,
linux-mm@kvack.org
Subject: Re: Very aggressive memory reclaim
Date: Tue, 29 Mar 2011 10:59:33 +0200 [thread overview]
Message-ID: <4D919F75.5070601@redhat.com> (raw)
In-Reply-To: <AANLkTi==vw7Dy-oK31PxHadwUaDRUUk+TM0ECSZ=chfv@mail.gmail.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: John Lepikhin <johnlepikhin@gmail.com>
Cc: Dave Chinner <david@fromorbit.com>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com,
linux-mm@kvack.org
Subject: Re: Very aggressive memory reclaim
Date: Tue, 29 Mar 2011 10:59:33 +0200 [thread overview]
Message-ID: <4D919F75.5070601@redhat.com> (raw)
In-Reply-To: <AANLkTi==vw7Dy-oK31PxHadwUaDRUUk+TM0ECSZ=chfv@mail.gmail.com>
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
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-03-29 8:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 16:39 Very aggressive memory reclaim John Lepikhin
2011-03-28 17:42 ` Steven Rostedt
[not found] ` <4D90C071.7040205@mnsu.edu>
2011-03-28 18:50 ` John Lepikhin
2011-03-30 13:48 ` Wu Fengguang
2011-03-28 21:53 ` Dave Chinner
2011-03-28 21:53 ` Dave Chinner
2011-03-28 21:53 ` Dave Chinner
2011-03-28 22:52 ` Minchan Kim
2011-03-28 22:52 ` Minchan Kim
2011-03-28 22:52 ` Minchan Kim
2011-03-29 2:55 ` KOSAKI Motohiro
2011-03-29 2:55 ` KOSAKI Motohiro
2011-03-29 2:55 ` KOSAKI Motohiro
2011-03-29 7:33 ` John Lepikhin
2011-03-29 7:33 ` John Lepikhin
2011-03-29 7:33 ` John Lepikhin
2011-03-29 7:22 ` John Lepikhin
2011-03-29 7:22 ` John Lepikhin
2011-03-28 23:58 ` Andi Kleen
2011-03-28 23:58 ` Andi Kleen
2011-03-28 23:58 ` Andi Kleen
2011-03-29 1:57 ` Dave Chinner
2011-03-29 1:57 ` Dave Chinner
2011-03-29 1:57 ` Dave Chinner
2011-03-29 7:26 ` John Lepikhin
2011-03-29 7:26 ` John Lepikhin
2011-03-29 7:26 ` John Lepikhin
2011-03-29 8:59 ` Avi Kivity [this message]
2011-03-29 8:59 ` Avi Kivity
2011-03-29 8:59 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D919F75.5070601@redhat.com \
--to=avi@redhat.com \
--cc=johnlepikhin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.