From: David Daney <ddaney.cavm@gmail.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Aaro Koskinen <aaro.koskinen@nokia.com>,
Joshua Kinard <kumba@gentoo.org>,
linux-mips@linux-mips.org, "Hill,
Steven" <Steven.Hill@cavium.com>
Subject: Re: THP broken on OCTEON?
Date: Mon, 23 May 2016 09:21:22 -0700 [thread overview]
Message-ID: <57432E02.9000008@gmail.com> (raw)
In-Reply-To: <20160523152007.GB28729@linux-mips.org>
On 05/23/2016 08:20 AM, Ralf Baechle wrote:
> On Mon, May 23, 2016 at 06:13:46PM +0300, Aaro Koskinen wrote:
>
>> I'm getting kernel crashes (see below) reliably when building Perl in
>> parallel (make -j16) on OCTEON EBH5600 board (8 cores, 4 GB RAM) with
>> Linux 4.6.
>>
>> It seems that CONFIG_TRANSPARENT_HUGEPAGE has something to do with the
>> issue - disabling it makes build go through fine.
>>
>> Any ideas?
>
> I thought it was working except on SGI Origin 200/2000 aka IP27 where
> Joshua Kinard (added to cc) was hitting issues as well.
>
> Joshua, does that similar to the issues you were hitting?
There is nothing OCTEON specific in the THP code, or huge pages in general.
That said, we have seen other THP related failures, and have never been
able to find the cause.
If someone can come up with a reproducible test case that triggers
quickly, we can run it in our simulator and easily find the problem.
There are THP tweaking knobs in /sys/kernel/mm/transparent_hugepage. If
you reduce the time in khugepaged/scan_sleep_millisecs, it often makes
things fail much more quickly.
David.
next prev parent reply other threads:[~2016-05-23 16:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 15:13 THP broken on OCTEON? Aaro Koskinen
2016-05-23 15:20 ` Ralf Baechle
2016-05-23 16:21 ` David Daney [this message]
2016-05-23 18:52 ` Aaro Koskinen
2016-05-23 19:03 ` David Daney
2016-05-23 19:03 ` David Daney
2016-05-23 19:08 ` Joshua Kinard
2016-05-23 20:02 ` Alastair Bridgewater
2016-05-23 18:57 ` Joshua Kinard
2016-05-23 19:22 ` Ralf Baechle
2016-05-23 19:40 ` Joshua Kinard
2016-05-23 20:01 ` Ralf Baechle
2016-05-24 21:21 ` Aaro Koskinen
2016-05-24 22:39 ` David Daney
2016-05-25 13:41 ` Aaro Koskinen
2016-05-26 9:33 ` Joshua Kinard
2016-05-26 13:36 ` Aaro Koskinen
2016-05-26 17:59 ` David Daney
2016-05-26 19:23 ` Aaro Koskinen
2016-05-26 22:13 ` David Daney
2016-05-27 17:14 ` Aaro Koskinen
2016-05-27 21:03 ` Joshua Kinard
2016-05-27 22:05 ` Aaro Koskinen
2016-05-27 22:22 ` Joshua Kinard
2016-06-22 22:05 ` David Daney
2016-06-23 12:08 ` Aaro Koskinen
2016-06-23 12:08 ` Aaro Koskinen
2016-06-24 11:38 ` Joshua Kinard
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=57432E02.9000008@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=Steven.Hill@cavium.com \
--cc=aaro.koskinen@nokia.com \
--cc=kumba@gentoo.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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.