From: Michal Hocko <mhocko@kernel.org>
To: Jerry Lee <leisurelysw24@gmail.com>
Cc: linux-mm@kvack.org
Subject: Re: kswapd consumes 100% CPU when highest zone is small
Date: Thu, 3 Mar 2016 09:22:55 +0100 [thread overview]
Message-ID: <20160303082254.GA26202@dhcp22.suse.cz> (raw)
In-Reply-To: <CAKQB+fss2UZOP-39GCpQY3T8MJoErm_0AeDnnAPZZ4MEWLXs7g@mail.gmail.com>
On Thu 03-03-16 10:23:03, Jerry Lee wrote:
> On 3 March 2016 at 01:36, Michal Hocko <mhocko@kernel.org> wrote:
>
> > On Wed 02-03-16 14:20:38, Jerry Lee wrote:
[...]
> > > Is there anything I could do to totally get rid of the problem?
> >
> > I would try to sacrifice those few megs and get rid of zone normal
> > completely. AFAIR mem=4G should limit the max_pfn to 4G so DMA32 should
> > cover the shole memory.
> >
>
> I came up with a patch that seem to work well on my system. But, I
> am afraid that it breaks the rule that all zones must be balanced for
> order-0 request and It may cause some other side-effect? I thought
> that the patch is just a workaround (a bad one) and not a cure-all.
One thing I haven't noticed previously is that you are running on the 3.12
kernel. I vaguely remember there were some fixes for small zones. Not
sure it would work for such a small zone but it would be worth trying I
guess. Could you retest with 4.4?
--
Michal Hocko
SUSE Labs
--
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-03-03 8:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 6:20 Jerry Lee
2016-03-02 14:21 ` chen feng
2016-03-03 1:56 ` Jerry Lee
2016-03-03 5:59 ` Chen Feng
2016-03-02 17:36 ` Michal Hocko
2016-03-03 2:23 ` Jerry Lee
2016-03-03 8:22 ` Michal Hocko [this message]
2016-03-03 9:27 ` Jerry Lee
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=20160303082254.GA26202@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=leisurelysw24@gmail.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