From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Hugh Greenberg <hugh@galliumos.org>
Cc: linux-mm@kvack.org
Subject: Re: [REGRESSION] [BISECTED] kswapd high CPU usage
Date: Mon, 25 Jan 2016 12:38:53 +0200 [thread overview]
Message-ID: <20160125103853.GD11095@node.shutemov.name> (raw)
In-Reply-To: <loom.20160123T165232-709@post.gmane.org>
On Sat, Jan 23, 2016 at 03:57:21PM +0000, Hugh Greenberg wrote:
> Kirill A. Shutemov <kirill <at> shutemov.name> writes:
> >
> > Could you try to insert "late_initcall(set_recommended_min_free_kbytes);"
> > back and check if makes any difference.
> >
>
> We tested adding late_initcall(set_recommended_min_free_kbytes);
> back in 4.1.14 and it made a huge difference. We aren't sure if the
> issue is 100% fixed, but it could be. We will keep testing it.
It would be nice to have values of min_free_kbytes before and after
set_recommended_min_free_kbytes() in your configuration.
--
Kirill A. Shutemov
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-01-25 10:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 14:28 [REGRESSION] [BISECTED] kswapd high CPU usage Nalorokk
2016-01-21 14:37 ` Fwd: " Nalorokk
2016-01-21 16:16 ` Kirill A. Shutemov
2016-01-23 15:57 ` Hugh Greenberg
2016-01-25 10:38 ` Kirill A. Shutemov [this message]
2016-01-25 16:37 ` Hugh Greenberg
2016-01-25 16:46 ` Hugh Greenberg
2016-02-02 13:59 ` Kirill A. Shutemov
2016-02-02 14:41 ` Sergey Senozhatsky
2016-02-02 16:24 ` Minchan Kim
2016-03-14 16:00 ` Hugh Greenberg
2016-03-14 16:07 ` Hugh Greenberg
2016-03-15 17:16 ` Hugh Greenberg
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=20160125103853.GD11095@node.shutemov.name \
--to=kirill@shutemov.name \
--cc=hugh@galliumos.org \
--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).