From: Jerry Lee <leisurelysw24@gmail.com>
To: linux-mm@kvack.org
Subject: kswapd consumes 100% CPU when highest zone is small
Date: Wed, 2 Mar 2016 14:20:38 +0800 [thread overview]
Message-ID: <CAKQB+ft3q2O2xYG2CTmTM9OCRLCP2FPTfHQ3jvcFSM-FGrjgGA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1469 bytes --]
Hi,
I have a x86_64 system with 2G RAM using linux-3.12.x. During copying
large
files (e.g. 100GB), kswapd easily consumes 100% CPU until the file is
deleted
or the page cache is dropped. With setting the min_free_kbytes from 16384
to
65536, the symptom is mitigated but I can't totally get rid of the problem.
After some trial and error, I found that highest zone is always unbalanced
with
order-0 page request so that pgdat_blanaced() continuously return false and
kswapd can't sleep.
Here's the watermarks (min_free_kbytes = 65536) in my system:
Node 0, zone DMA
pages free 2167
min 138
low 172
high 207
scanned 0
spanned 4095
present 3996
managed 3974
Node 0, zone DMA32
pages free 215375
min 16226
low 20282
high 24339
scanned 0
spanned 1044480
present 490971
managed 464223
Node 0, zone Normal
pages free 7
min 18
low 22
high 27
scanned 0
spanned 1536
present 1536
managed 523
Besides, when the kswapd crazily spins, the value of the following entries
in vmstat increases quickly even when I stop copying file:
pgalloc_dma 17719
pgalloc_dma32 3262823
slabs_scanned 937728
kswapd_high_wmark_hit_quickly 54333233
pageoutrun 54333235
Is there anything I could do to totally get rid of the problem?
Thanks
[-- Attachment #2: Type: text/html, Size: 2052 bytes --]
next reply other threads:[~2016-03-02 6:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 6:20 Jerry Lee [this message]
2016-03-02 14:21 ` chen feng
2016-03-03 1:56 ` Jerry Lee
2016-03-03 5:59 ` Chen Feng
2016-03-02 17:36 ` Michal Hocko
2016-03-03 2:23 ` Jerry Lee
2016-03-03 8:22 ` Michal Hocko
2016-03-03 9:27 ` Jerry Lee
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=CAKQB+ft3q2O2xYG2CTmTM9OCRLCP2FPTfHQ3jvcFSM-FGrjgGA@mail.gmail.com \
--to=leisurelysw24@gmail.com \
--cc=linux-mm@kvack.org \
/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