From: Chris Webb <chris@arachsys.com>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Minchan Kim <minchan.kim@gmail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: Over-eager swapping
Date: Wed, 4 Aug 2010 10:58:12 +0100 [thread overview]
Message-ID: <20100804095811.GC2326@arachsys.com> (raw)
In-Reply-To: <20100804032400.GA14141@localhost>
Wu Fengguang <fengguang.wu@intel.com> writes:
> This is interesting. Why is it waiting for 1m here? Are there high CPU
> loads? Would you do a
>
> echo t > /proc/sysrq-trigger
>
> and show us the dmesg?
Annoyingly, magic-sysrq isn't compiled in on these kernels. Is there another
way I can get this info for you? Replacing the kernels on the machines is a
painful job as I have to give the clients running on them quite a bit of
notice of the reboot, and I haven't been able to reproduce the problem on a
test machine.
I also think the swap use is much better following a reboot, and only starts
to spiral out of control after the machines have been running for a week or
so.
However, your suggestion is right that the CPU loads on these machines are
typically quite high. The large number of kvm virtual machines they run mean
thatl oads of eight or even sixteen in /proc/loadavg are not unusual, and
these are higher when there's swap than after it has been removed. I assume
this is mostly because of increased IO wait, as this number increases
significantly in top.
Cheers,
Chris.
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-08-04 10:00 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 12:47 Over-eager swapping 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2012-04-23 9:27 Richard Davies
2012-04-23 12:07 ` Zdenek Kaspar
2012-04-23 17:19 ` Dave Hansen
2012-04-24 0:35 ` Minchan Kim
2012-04-24 11:16 ` Peter Lieven
2012-04-25 14:41 ` Rik van Riel
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=20100804095811.GC2326@arachsys.com \
--to=chris@arachsys.com \
--cc=fengguang.wu@intel.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=penberg@cs.helsinki.fi \
/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).