From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Cc: mhocko@suse.cz, vbabka@suse.cz
Subject: 5.7-rc0: kswapd eats cpu during a disk test?!
Date: Sun, 31 May 2020 12:34:31 +0200 [thread overview]
Message-ID: <20200531103431.GA28429@amd> (raw)
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
Hi!
This is simple cat /dev/sda > /dev/zero... on thinkpad x60 (x86-32),
with spinning rust.
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1000 root 20 0 0 0 0 R 53.3 0.0 57:34.93 kswapd0
27897 root 20 0 6976 580 536 R 44.5 0.0 1:44.53 cat
It keeps both CPUs busy... and I don't think that's right.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next reply other threads:[~2020-05-31 10:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-31 10:34 Pavel Machek [this message]
2020-06-01 8:55 ` 5.7-rc0: kswapd eats cpu during a disk test?! Vlastimil Babka
2020-06-12 22:45 ` Pavel Machek
2020-06-12 23:05 ` Pavel Machek
[not found] ` <20200613044738.11764-1-hdanton@sina.com>
2020-06-13 6:48 ` Pavel Machek
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=20200531103431.GA28429@amd \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=vbabka@suse.cz \
/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