All of lore.kernel.org
 help / color / mirror / Atom feed
From: valdis.kletnieks@vt.edu
To: Jan Kara <jack@suse.cz>
Cc: Pavel Machek <pavel@ucw.cz>,
	Mel Gorman <mgorman@techsingularity.net>,
	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, 29 Jan 2019 20:06:39 -0500	[thread overview]
Message-ID: <14875.1548810399@turing-police.cc.vt.edu> (raw)
In-Reply-To: <20190128091627.GA27972@quack2.suse.cz>

On Mon, 28 Jan 2019 10:16:27 +0100, Jan Kara said:

> So my buffer_migrate_page_norefs() is certainly buggy in its current
> incarnation (as a result block device page cache is not migratable at all).
> I've sent Andrew a patch over week ago but so far it got ignored. The patch
> is attached, can you give it a try whether it changes something for you?
> Thanks!

Been running with the patch for about 24 hours, haven't seen kcompactd
misbehave.  I even fired up a Chrome with a lot of tabs open, a Firefox, and a
kernel build, intentionally drove the system into swapping, and kcompactd
didn't make it into the top 10 on 'top'.

I'm willing to say put a "tested-by:" on that one,  it looks fixed from here.
If there's any remaining bugs, they're ones I can't seem to trigger...


  parent reply	other threads:[~2019-01-30  1:06 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 [this message]
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

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=14875.1548810399@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=aarcange@redhat.com \
    --cc=akpm@osdl.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.