From: Dave Chinner <david@fromorbit.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-mm@kvack.org, John Lepikhin <johnlepikhin@gmail.com>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: Very aggressive memory reclaim
Date: Tue, 29 Mar 2011 12:57:27 +1100 [thread overview]
Message-ID: <20110329015727.GE3008@dastard> (raw)
In-Reply-To: <m2bp0u23wl.fsf@firstfloor.org>
On Mon, Mar 28, 2011 at 04:58:50PM -0700, Andi Kleen wrote:
> Dave Chinner <david@fromorbit.com> writes:
> >
> > 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
>
> Often it's to get pages of a higher order. Just tracing alloc_pages
> should tell you that.
Yes, the kmem/mm_page_alloc tracepoint gives us that. But in case
that is not the cause, grabbing all the trace points I suggested is
more likely to indicate where the problem is. I'd prefer to get more
data than needed the first time around than have to do multiple
round trips because a single trace point doesn't tell us the cause...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: John Lepikhin <johnlepikhin@gmail.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 12:57:27 +1100 [thread overview]
Message-ID: <20110329015727.GE3008@dastard> (raw)
In-Reply-To: <m2bp0u23wl.fsf@firstfloor.org>
On Mon, Mar 28, 2011 at 04:58:50PM -0700, Andi Kleen wrote:
> Dave Chinner <david@fromorbit.com> writes:
> >
> > 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
>
> Often it's to get pages of a higher order. Just tracing alloc_pages
> should tell you that.
Yes, the kmem/mm_page_alloc tracepoint gives us that. But in case
that is not the cause, grabbing all the trace points I suggested is
more likely to indicate where the problem is. I'd prefer to get more
data than needed the first time around than have to do multiple
round trips because a single trace point doesn't tell us the cause...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: John Lepikhin <johnlepikhin@gmail.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 12:57:27 +1100 [thread overview]
Message-ID: <20110329015727.GE3008@dastard> (raw)
In-Reply-To: <m2bp0u23wl.fsf@firstfloor.org>
On Mon, Mar 28, 2011 at 04:58:50PM -0700, Andi Kleen wrote:
> Dave Chinner <david@fromorbit.com> writes:
> >
> > 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
>
> Often it's to get pages of a higher order. Just tracing alloc_pages
> should tell you that.
Yes, the kmem/mm_page_alloc tracepoint gives us that. But in case
that is not the cause, grabbing all the trace points I suggested is
more likely to indicate where the problem is. I'd prefer to get more
data than needed the first time around than have to do multiple
round trips because a single trace point doesn't tell us the cause...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
--
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 1:54 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 [this message]
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
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=20110329015727.GE3008@dastard \
--to=david@fromorbit.com \
--cc=andi@firstfloor.org \
--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.