From: David Daney <ddaney.cavm@gmail.com>
To: Sebastian Gottschall <s.gottschall@dd-wrt.com>
Cc: linux-mips@linux-mips.org
Subject: Re: MIPS: Add dependencies for HAVE_ARCH_TRANSPARENT_HUGEPAGE
Date: Wed, 20 Mar 2013 16:12:37 -0700 [thread overview]
Message-ID: <514A4265.2080709@gmail.com> (raw)
In-Reply-To: <kiddfo$82s$1@ger.gmane.org>
On 03/20/2013 03:33 PM, Sebastian Gottschall wrote:
> Am 04.03.2013 05:17, schrieb Ben Hutchings:
>> The MIPS implementation of transparent huge-pages (THP) is 64-bit only,
>> and of course also requires that the CPU supports huge-pages.
>>
>> Currently it's entirely possible to enable THP in other configurations,
>> which then fail to build due to pfn_pmd() not being defined.
>>
>> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
>> Cc: David Daney <david.daney@cavium.com>
>> ---
>> --- a/arch/mips/Kconfig
>> +++ b/arch/mips/Kconfig
>> @@ -19,7 +19,7 @@ config MIPS
>> select HAVE_KRETPROBES
>> select HAVE_DEBUG_KMEMLEAK
>> select ARCH_BINFMT_ELF_RANDOMIZE_PIE
>> - select HAVE_ARCH_TRANSPARENT_HUGEPAGE
>> + select HAVE_ARCH_TRANSPARENT_HUGEPAGE if CPU_SUPPORTS_HUGEPAGES
>> && 64BIT
>> select RTC_LIB if !MACH_LOONGSON
>> select GENERIC_ATOMIC64 if !64BIT
>> select ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE
>>
> why? the mips32 74k platform (broadcom bcm4706 for instance) does
> support huge pages.
The hardware may support pages larger than 64K, but does the Linux
kernel? I think not.
> and some of these devices are also using highmem for
> accessing more than 128mb ram (which is totally broken in all current
> kernels too and causing filesystem corruptions)
> i was able to fix the highmem problem using a patch which was submitted
> but never taken into the mainline, but i just was able to get thb
> partially to work on mips32. but i think it would be possible to support
> this on mips32 as well. so why leaving it out?
As they say... Patches are welcome. If you get Linux HUGE pages working
for 32-bit kernels send a patch to enable the transparent variety as well.
David Daney
next prev parent reply other threads:[~2013-03-20 23:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-02 20:51 THP broken on MIPS-32 [3.8] Ben Hutchings
2013-03-04 4:17 ` MIPS: Add dependencies for HAVE_ARCH_TRANSPARENT_HUGEPAGE Ben Hutchings
2013-03-04 18:13 ` David Daney
2013-03-12 14:07 ` Ralf Baechle
2013-03-20 22:33 ` Sebastian Gottschall
2013-03-20 23:12 ` David Daney [this message]
2013-03-21 0:16 ` Sebastian Gottschall
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=514A4265.2080709@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=s.gottschall@dd-wrt.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