From: Michal Hocko <mhocko@kernel.org>
To: Daniel Jordan <lkmldmj@gmail.com>
Cc: john terragon <terragonjohn@yahoo.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"bugzilla-daemon@bugzilla.kernel.org"
<bugzilla-daemon@bugzilla.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Daniel Jordan <daniel.m.jordan@oracle.com>
Subject: Re: [Bug 200105] High paging activity as soon as the swap is touched (with steps and code to reproduce it)
Date: Mon, 23 Jul 2018 15:02:35 +0200 [thread overview]
Message-ID: <20180723130235.GF31229@dhcp22.suse.cz> (raw)
In-Reply-To: <f20b1529-fcb9-8d0a-6259-fe76977e00d6@gmail.com>
[I am really sorry to be slow on responding]
On Sat 21-07-18 10:39:05, Daniel Jordan wrote:
> John's issue only happens using a LUKS encrypted swap partition,
> unencrypted swap or swap encrypted without LUKS works fine.
>
> In one test (out5.txt) where most system memory is taken by anon pages
> beforehand, the heavy direct reclaim that Michal noticed lasts for 24
> seconds, during which on average if I've crunched my numbers right,
> John's test program was allocating at 4MiB/s, the system overall
> (pgalloc_normal) was allocating at 235MiB/s, and the system was
> swapping out (pswpout) at 673MiB/s. pgalloc_normal and pswpout stay
> roughly the same each second, no big swings.
>
> Is the disparity between allocation and swapout rate expected?
>
> John ran perf during another test right before the last test program
> was started (this doesn't include the initial large allocation
> bringing the system close to swapping). The top five allocators
> (kmem:mm_page_alloc):
>
> # Overhead Pid:Command
> # ........ .......................
> #
> 48.45% 2005:memeater # the test program
> 32.08% 73:kswapd0
> 3.16% 1957:perf_4.17
> 1.41% 1748:watch
> 1.16% 2043:free
Huh, kswapd allocating memory sounds really wrong here. Is it possible
that the swap device driver is double buffering and allocating a new
page for each one to swap out?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-07-23 13:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-200105-8545@https.bugzilla.kernel.org/>
[not found] ` <bug-200105-8545-FomWhXSVhq@https.bugzilla.kernel.org/>
2018-07-20 8:19 ` [Bug 200105] High paging activity as soon as the swap is touched (with steps and code to reproduce it) john terragon
2018-07-21 14:39 ` Daniel Jordan
2018-07-21 14:43 ` Daniel Jordan
2018-07-21 20:09 ` john terragon
2018-07-23 13:02 ` Michal Hocko [this message]
2018-10-10 1:35 ` Daniel Jordan
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=20180723130235.GF31229@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=daniel.m.jordan@oracle.com \
--cc=linux-mm@kvack.org \
--cc=lkmldmj@gmail.com \
--cc=terragonjohn@yahoo.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.