From: Wu Fengguang <fengguang.wu@intel.com>
To: John Lepikhin <johnlepikhin@gmail.com>
Cc: Jeffrey Hundstad <jeffrey.hundstad@mnsu.edu>,
"linux-kernel@vger.kernel.org. Alexander Viro"
<viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: Very aggressive memory reclaim
Date: Wed, 30 Mar 2011 21:48:05 +0800 [thread overview]
Message-ID: <20110330134804.GA10113@localhost> (raw)
In-Reply-To: <AANLkTikmQJFq633VNqNOMC-BfEC=BU=g7j5uW78P4B4Z@mail.gmail.com>
Hi John,
On Mon, Mar 28, 2011 at 10:50:56PM +0400, John Lepikhin wrote:
> 2011/3/28 Jeffrey Hundstad <jeffrey.hundstad@mnsu.edu>:
>
> > I'd take a look here:
> > http://www.linuxinsight.com/proc_sys_vm_hierarchy.html
>
> Yes, I already played with dirty_*, min_free_kbytes (3000kb),
> swappiness (0..100), vfs_cache_pressure (1..200) and zone_reclaim_mode
> (currently 0). Other parameters are set to defaults.
>
> By the way, there is no swap enabled. Instead of just dropping 50% of
> page caches, kernel was intensively swapping then there was a swap
> device.
Is your memory usage balanced across the nodes? You can check it via
/sys/devices/system/node/node*/meminfo.
Are there lots of high-order memory allocations? /proc/buddyinfo will
disclose some of them.
Thanks,
Fengguang
--
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-30 13:48 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 [this message]
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
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=20110330134804.GA10113@localhost \
--to=fengguang.wu@intel.com \
--cc=jeffrey.hundstad@mnsu.edu \
--cc=johnlepikhin@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=viro@zeniv.linux.org.uk \
/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.