From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Richard Davies <richard@arachsys.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Minchan Kim <minchan.kim@gmail.com>,
Wu Fengguang <fengguang.wu@intel.com>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
Christoph Lameter <cl@linux-foundation.org>,
Lee Schermerhorn <lee.schermerhorn@hp.com>,
Chris Webb <chris@arachsys.com>, Badari <pbadari@us.ibm.com>
Subject: Re: Over-eager swapping
Date: Mon, 23 Apr 2012 10:19:15 -0700 [thread overview]
Message-ID: <4F958F13.1000005@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120423092730.GB20543@alpha.arachsys.com>
On 04/23/2012 02:27 AM, Richard Davies wrote:
> # cat /proc/meminfo
> MemTotal: 65915384 kB
> MemFree: 271104 kB
> Buffers: 36274368 kB
Your "Buffers" are the only thing that really stands out here. We used
to see this kind of thing on ext3 a lot, but it's gotten much better
lately. From slabinfo, you can see all the buffer_heads:
buffer_head 8175114 8360937 104 39 1 : tunables 0 0
0 : slabdata 214383 214383 0
I _think_ this was a filesystems issue where the FS for some reason kept
the buffers locked down. The swapping just comes later as so much of
RAM is eaten up by buffers.
--
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:[~2012-04-23 17:19 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 9:27 Over-eager swapping Richard Davies
2012-04-23 12:07 ` Zdenek Kaspar
2012-04-23 17:19 ` Dave Hansen [this message]
2012-04-24 0:35 ` Minchan Kim
2012-04-24 11:16 ` Peter Lieven
2012-04-25 14:41 ` Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2010-08-02 12:47 Chris Webb
2010-08-02 23:55 ` Minchan Kim
2010-08-03 3:31 ` Chris Webb
2010-08-03 4:09 ` Minchan Kim
2010-08-03 4:28 ` Wu Fengguang
2010-08-03 4:47 ` Minchan Kim
2010-08-03 6:39 ` Wu Fengguang
2010-08-03 21:49 ` Chris Webb
2010-08-04 2:21 ` Wu Fengguang
2010-08-04 3:10 ` Minchan Kim
2010-08-04 3:24 ` Wu Fengguang
2010-08-04 9:58 ` Chris Webb
2010-08-04 11:49 ` Wu Fengguang
2010-08-04 12:04 ` Chris Webb
2010-08-18 14:38 ` Wu Fengguang
2010-08-18 14:46 ` Chris Webb
2010-08-18 15:21 ` Wu Fengguang
2010-08-18 15:57 ` Christoph Lameter
2010-08-18 16:20 ` Wu Fengguang
2010-08-18 15:57 ` Lee Schermerhorn
2010-08-18 15:58 ` Chris Webb
2010-08-18 16:13 ` Christoph Lameter
2010-08-18 16:32 ` Chris Webb
2010-08-19 5:16 ` Balbir Singh
2010-08-19 10:20 ` Chris Webb
2010-08-19 19:03 ` Christoph Lameter
2010-08-18 16:13 ` Wu Fengguang
2010-08-18 16:31 ` Chris Webb
2010-08-19 5:13 ` Balbir Singh
2010-08-18 16:45 ` Balbir Singh
2010-08-19 9:25 ` Chris Webb
2010-08-19 15:13 ` Balbir Singh
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=4F958F13.1000005@linux.vnet.ibm.com \
--to=dave@linux.vnet.ibm.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=chris@arachsys.com \
--cc=cl@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=pbadari@us.ibm.com \
--cc=richard@arachsys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).