From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Rafael Aquini <aquini@redhat.com>, Rik van Riel <riel@redhat.com>,
Mel Gorman <mgorman@suse.de>, Hugh Dickins <hughd@google.com>,
Suleiman Souhlal <suleiman@google.com>,
stable@kernel.org, Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>,
KVM list <kvm@vger.kernel.org>
Subject: commit 0bf1457f0cfca7b " mm: vmscan: do not swap anon pages just because free+file is low" causes heavy performance regression on paging
Date: Tue, 22 Apr 2014 12:55:37 +0200 [thread overview]
Message-ID: <53564AA9.3060905@de.ibm.com> (raw)
While preparing/testing some KVM on s390 patches for the next merge window (target is kvm/next which is based on 3.15-rc1) I faced a very severe performance hickup on guest paging (all anonymous memory).
All memory bound guests are in "D" state now and the system is barely unusable.
Reverting commit 0bf1457f0cfca7bc026a82323ad34bcf58ad035d
"mm: vmscan: do not swap anon pages just because free+file is low" makes the problem go away.
According to /proc/vmstat the system is now in direct reclaim almost all the time for every page fault (more than 10x more direct reclaims than kswap reclaims)
With the patch being reverted everything is fine again.
Any ideas?
Christian
next reply other threads:[~2014-04-22 10:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 10:55 Christian Borntraeger [this message]
2014-04-22 11:57 ` commit 0bf1457f0cfca7b " mm: vmscan: do not swap anon pages just because free+file is low" causes heavy performance regression on paging Christian Borntraeger
2014-04-22 14:40 ` Rik van Riel
2014-04-22 14:53 ` Rafael Aquini
2014-04-24 12:24 ` Johannes Weiner
2014-04-22 15:06 ` Johannes Weiner
2014-04-22 18:33 ` Christian Borntraeger
2014-04-22 18:58 ` Rafael Aquini
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=53564AA9.3060905@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=aquini@redhat.com \
--cc=ehrhardt@linux.vnet.ibm.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=riel@redhat.com \
--cc=stable@kernel.org \
--cc=suleiman@google.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