From: Andrea Arcangeli <aarcange@redhat.com>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: linux-mm@kvack.org, ebru.akagunduz@gmail.com,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
kirill.shutemov@linux.intel.com, riel@redhat.com, vbabka@suse.cz,
zhangyanfei@cn.fujitsu.com, Will Deacon <will.deacon@arm.com>,
Andre Przywara <andre.przywara@arm.com>,
Marc Zyngier <marc.zyngier@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [BUG] Read-Only THP causes stalls (commit 10359213d)
Date: Tue, 26 May 2015 16:42:47 +0200 [thread overview]
Message-ID: <20150526144247.GJ26958@redhat.com> (raw)
In-Reply-To: <20150526080848.GA27075@cbox>
On Tue, May 26, 2015 at 10:08:48AM +0200, Christoffer Dall wrote:
> > echo 0 > /sys/kernel/mm/transparent_hugepage/khugepaged/pages_to_scan
>
> this returns -EINVAL.
>
Oops sorry, I haven't re-read the code, pages_to_scan 0 does not make
sense, it would only be useful for debugging purposes because it
doesn't shut off khugepaged entirely, so it is ok that it returns
-EINVAL, just it won't allow this debug tweak...
> But I'm trying now with:
>
> echo never > /sys/kernel/mm/transparent_hugepage/enabled
>
> >
> > and verify the problem goes away without having to revert the patch?
>
> will let you know, so far so good...
I only intended to disable khugepaged, to validate the theory it was
that patch that made the difference.
Increasing the sleep time is equivalent to set pages_to_scan to 0, so
you can use this instead:
echo 3600000 >/sys/kernel/mm/transparent_hugepage/khugepaged/scan_sleep_millisecs
echo 3600000 >/sys/kernel/mm/transparent_hugepage/khugepaged/alloc_sleep_millisecs
In addition to knowing if it still happens with THP disables, it's
interesting to know also if it happens with THP enabled but khugepaged
disabled.
> what is memhog? I couldn't find the utility in Google...
Somebody answered, yes it's from numactl.
> I did try with the above settings and just push a bunch of data into
> ramfs and tmpfs and indeed the sytem died very quickly (on v4.0-rc4).
That's fine, memhog just was a way to hit swap. tmpfs pages aren't
candidate for khugepaged THP collapsing, so it'd be perhaps quicker to
reproduce with something like memhog that uses anonymous memory but it
still happens, as long as you hit swap it's ok.
If other arm don't exhibit this problem, perhaps it has to do with
some difference in THP, I recall there were two models for arm.
Thanks,
Andrea
--
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>
prev parent reply other threads:[~2015-05-26 14:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 19:34 Christoffer Dall
2015-05-25 10:05 ` Kirill A. Shutemov
2015-05-25 10:19 ` Christoffer Dall
2015-05-25 14:15 ` Andrea Arcangeli
2015-05-26 8:08 ` Christoffer Dall
2015-05-26 10:57 ` Marc Zyngier
2015-05-26 14:24 ` Steve Capper
2015-05-26 14:35 ` Christoffer Dall
2015-05-26 14:48 ` Steve Capper
2015-05-26 14:58 ` Andrea Arcangeli
2015-05-26 14:42 ` Andrea Arcangeli [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=20150526144247.GJ26958@redhat.com \
--to=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andre.przywara@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=ebru.akagunduz@gmail.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marc.zyngier@arm.com \
--cc=riel@redhat.com \
--cc=vbabka@suse.cz \
--cc=will.deacon@arm.com \
--cc=zhangyanfei@cn.fujitsu.com \
/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