From: "Nikolay S." <nowhere@hakkenden.ath.cx>
To: linux-kernel@vger.kernel.org
Subject: Kswapd in 3.2.0-rc5 is a CPU hog
Date: Wed, 21 Dec 2011 07:10:36 +0400 [thread overview]
Message-ID: <1324437036.4677.5.camel@hakkenden.homenet> (raw)
Hello,
I'm using 3.2-rc5 on a machine, which atm does almost nothing except
file system operations and network i/o (i.e. file server). And there is
a problem with kswapd.
I'm playing with dd:
dd if=/some/big/file of=/dev/null bs=8M
I.e. I'm filling page cache.
So when the machine is just rebooted, kswapd during this operation is
almost idle, just 5-8 percent according to top.
After ~5 days of uptime (5 days, 2:10), the same operation demands ~70%
for kswapd:
PID USER S %CPU %MEM TIME+ SWAP COMMAND
420 root R 70 0.0 22:09.60 0 kswapd0
17717 nowhere D 27 0.2 0:01.81 10m dd
In fact, kswapd cpu usage on this operation steadily increases over
time.
Also read performance degrades over time. After reboot:
dd if=/some/big/file of=/dev/null bs=8M
1019+1 records in
1019+1 records out
8553494018 bytes (8.6 GB) copied, 16.211 s, 528 MB/s
After ~5 days uptime:
dd if=/some/big/file of=/dev/null bs=8M
1019+1 records in
1019+1 records out
8553494018 bytes (8.6 GB) copied, 29.0507 s, 294 MB/s
Whereas raw disk sequential read performance stays the same:
dd if=/some/big/file of=/dev/null bs=8M iflag=direct
1019+1 records in
1019+1 records out
8553494018 bytes (8.6 GB) copied, 14.7286 s, 581 MB/s
Also after dropping caches, situation somehow improves, but not to the
state of freshly restarted system:
PID USER S %CPU %MEM TIME+ SWAP COMMAND
420 root S 39 0.0 23:31.17 0 kswapd0
19829 nowhere D 24 0.2 0:02.72 7764 dd
perf shows:
31.24% kswapd0 [kernel.kallsyms] [k] _raw_spin_lock
26.19% kswapd0 [kernel.kallsyms] [k] shrink_slab
16.28% kswapd0 [kernel.kallsyms] [k] prune_super
6.55% kswapd0 [kernel.kallsyms] [k] grab_super_passive
5.35% kswapd0 [kernel.kallsyms] [k] down_read_trylock
4.03% kswapd0 [kernel.kallsyms] [k] up_read
2.31% kswapd0 [kernel.kallsyms] [k] put_super
1.81% kswapd0 [kernel.kallsyms] [k] drop_super
0.99% kswapd0 [kernel.kallsyms] [k] __put_super
0.25% kswapd0 [kernel.kallsyms] [k] __isolate_lru_page
0.23% kswapd0 [kernel.kallsyms] [k] free_pcppages_bulk
0.19% kswapd0 [r8169] [k] rtl8169_interrupt
0.15% kswapd0 [kernel.kallsyms] [k] twa_interrupt
P.S.: The message above was written couple of days ago. Now I'm at 10
days uptime, and this is the result as of today
PID USER S %CPU %MEM TIME+ SWAP COMMAND
420 root R 93 0.0 110:48.48 0 kswapd0
30085 nowhere D 42 0.2 0:04.36 10m dd
PPS: Please CC me.
next reply other threads:[~2011-12-21 3:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 3:10 Nikolay S. [this message]
2011-12-21 9:52 ` Michal Hocko
2011-12-21 10:15 ` nowhere
2011-12-21 10:24 ` Michal Hocko
2011-12-21 10:52 ` nowhere
2011-12-21 14:06 ` Alex Elder
2011-12-21 14:19 ` nowhere
2011-12-21 22:55 ` Dave Chinner
2011-12-23 9:01 ` nowhere
2011-12-23 10:20 ` Dave Chinner
2011-12-23 11:04 ` nowhere
2011-12-23 20:45 ` Dave Chinner
2011-12-25 9:09 ` Hillf Danton
2011-12-25 10:21 ` Nikolay S.
2011-12-26 12:35 ` Hillf Danton
2011-12-27 0:20 ` KAMEZAWA Hiroyuki
2011-12-27 13:33 ` Hillf Danton
2011-12-28 0:06 ` KAMEZAWA Hiroyuki
2011-12-27 2:15 ` KAMEZAWA Hiroyuki
2011-12-27 2:50 ` Nikolay S.
2011-12-27 4:44 ` KAMEZAWA Hiroyuki
2011-12-27 6:06 ` nowhere
2011-12-28 21:33 ` Dave Chinner
2011-12-28 22:57 ` KOSAKI Motohiro
2012-01-02 7:00 ` Dave Chinner
2011-12-27 3:57 ` Minchan Kim
2011-12-27 4:56 ` KAMEZAWA Hiroyuki
2012-01-10 22:33 ` Andrew Morton
2012-01-11 3:25 ` Nikolay S.
2012-01-11 4:42 ` Andrew Morton
2012-01-11 0:33 ` Dave Chinner
2012-01-11 1:17 ` 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=1324437036.4677.5.camel@hakkenden.homenet \
--to=nowhere@hakkenden.ath.cx \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®