From: Hugh Greenberg <hugh@galliumos.org>
To: linux-mm@kvack.org
Subject: Re: [REGRESSION] [BISECTED] kswapd high CPU usage
Date: Sat, 23 Jan 2016 15:57:21 +0000 (UTC) [thread overview]
Message-ID: <loom.20160123T165232-709@post.gmane.org> (raw)
In-Reply-To: 20160121161656.GA16564@node.shutemov.name
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.
--
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-23 16:00 UTC|newest]
Thread overview: 17+ 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 14:37 ` Nalorokk
2016-01-21 16:16 ` Kirill A. Shutemov
2016-01-21 16:16 ` Kirill A. Shutemov
2016-01-23 15:57 ` Hugh Greenberg [this message]
2016-01-25 10:38 ` Kirill A. Shutemov
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
-- strict thread matches above, loose matches on Subject: below --
2020-07-15 10:04 Alexey Vlasov
2020-08-10 13:47 ` Alexey Vlasov
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=loom.20160123T165232-709@post.gmane.org \
--to=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 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.