linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Linux-MM <linux-mm@kvack.org>
Subject: Re: "tell us why you want to disable CONFIG_COMPACTION" --> spikes from VMs?
Date: Sun, 20 Dec 2020 19:29:29 +0000	[thread overview]
Message-ID: <20201220192929.GW15600@casper.infradead.org> (raw)
In-Reply-To: <CAHmME9oMB65sKa7iAFS3Ma62yf9HFQnNar2pCEjxOAw06Me3Cw@mail.gmail.com>

On Sat, Dec 19, 2020 at 07:48:58PM +0100, Jason A. Donenfeld wrote:
> Hi,
> 
> In trying to debug an issue, I came across this text in the config
> COMPACTION menu item:
> 
> > Compaction is the only memory management component to form
> > high order (larger physically contiguous) memory blocks
> > reliably. The page allocator relies on compaction heavily and
> > the lack of the feature can lead to unexpected OOM killer
> > invocations for high order memory requests. You shouldn't
> > disable this option unless there really is a strong reason for
> > it and then we would be really interested to hear about that at
> > linux-mm@kvack.org.
> 
> So, here I am as requested.
> 
> My system has 64 gigs of ram. Often times when starting up VMs, with
> either QEMU/KVM or with VMware, the VM will be extremely sluggish and
> laggy for a little while, usually around 5 minutes. During that phase,
> I see kcompact0 using 100% CPU. But other times this doesn't happen at
> all. I figured I'd try removing CONFIG_COMPACTION and seeing what
> happens, but then I saw your admonishment, so here I am.

My initial question is "What is kcompactd doing?"  There are a number
of tracepoints in kcompactd, so you should be able to enable them all
and find out.


      reply	other threads:[~2020-12-20 19:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-19 18:48 "tell us why you want to disable CONFIG_COMPACTION" --> spikes from VMs? Jason A. Donenfeld
2020-12-20 19:29 ` Matthew Wilcox [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=20201220192929.GW15600@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=Jason@zx2c4.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;
as well as URLs for NNTP newsgroup(s).