From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Tibor Bana <bana.tibor@gmail.com>,
Mel Gorman <mgorman@techsingularity.net>, Jan Kara <jack@suse.cz>,
Pavel Machek <pavel@ucw.cz>,
kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
vbabka@suse.cz, aarcange@redhat.com, rientjes@google.com,
mhocko@kernel.org, zi.yan@cs.rutgers.edu, hannes@cmpxchg.org
Subject: Re: [regression -next0117] What is kcompactd and why is he eating 100% of my cpu?
Date: Tue, 16 Feb 2021 17:33:14 -0500 [thread overview]
Message-ID: <35445.1613514794@turing-police> (raw)
In-Reply-To: <YCu8RuhvU1Env7OF@zx2c4.com>
[-- Attachment #1: Type: text/plain, Size: 398 bytes --]
On Tue, 16 Feb 2021 13:36:22 +0100, "Jason A. Donenfeld" said:
> Another anecdote: 5.11.0, 64 gigs of ram. If I run QEMU/KVM for a VM
> with 16 gigs at the same time as a VMware VM with 16 gigs of ram,
> kcompact goes wild and both VMs get really slow. The key here is running
> KVM at the same time as VMware.
Do things operated as expected if there are 2 KVM instances, or 2 VMware
instances?
[-- Attachment #2: Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2021-02-16 22:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 20:00 [regression -next0117] What is kcompactd and why is he eating 100% of my cpu? Pavel Machek
2019-01-27 2:56 ` valdis.kletnieks
2019-01-27 14:09 ` Mel Gorman
2019-01-27 14:15 ` Mel Gorman
2019-01-27 16:00 ` Pavel Machek
2019-01-27 21:36 ` valdis.kletnieks
2019-01-28 9:16 ` Jan Kara
2019-01-28 10:57 ` Sergey Senozhatsky
2019-01-28 11:03 ` Mel Gorman
2019-01-30 1:06 ` valdis.kletnieks
2019-01-30 4:29 ` valdis.kletnieks
2019-01-30 10:40 ` Mel Gorman
2021-01-25 18:54 ` Tibor Bana
2021-01-26 8:52 ` Valdis Klētnieks
2021-01-26 9:17 ` Mel Gorman
2021-01-27 19:29 ` Tibor Bana
2021-02-16 12:36 ` Jason A. Donenfeld
2021-02-16 22:33 ` Valdis Klētnieks [this message]
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=35445.1613514794@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=Jason@zx2c4.com \
--cc=aarcange@redhat.com \
--cc=akpm@osdl.org \
--cc=bana.tibor@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=pavel@ucw.cz \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
--cc=zi.yan@cs.rutgers.edu \
/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