From: Ralf Baechle <ralf@linux-mips.org>
To: David Daney <ddaney@caviumnetworks.com>
Cc: linux-mips@linux-mips.org, wli@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] Enable hugetlbfs for more systems.
Date: Tue, 16 Jun 2009 11:20:34 +0100 [thread overview]
Message-ID: <20090616102034.GC13622@linux-mips.org> (raw)
In-Reply-To: <1243471666-27915-4-git-send-email-ddaney@caviumnetworks.com>
On Wed, May 27, 2009 at 05:47:45PM -0700, David Daney wrote:
> From: David Daney <ddaney@caviumnetworks.com>
> Date: Wed, 27 May 2009 17:47:45 -0700
> To: linux-mips@linux-mips.org, ralf@linux-mips.org
> Cc: wli@holomorphy.com, David Daney <ddaney@caviumnetworks.com>
Holomorphy.com is unreachable since like a year. Use wli@kernel.org.
> Subject: [PATCH 4/5] Enable hugetlbfs for more systems.
>
> As part of adding hugetlbfs support for MIPS, I am adding a new
> kconfig variable 'SYS_SUPPORTS_HUGETLBFS'. Since some mips cpu
> varients don't yet support it, we can enable selection of HUGETLBFS on
> a system by system basis from the arch/mips/Kconfig.
>
> CC: William Irwin <wli@holomorphy.com>
> Signed-off-by: David Daney <ddaney@caviumnetworks.com>
> ---
> fs/Kconfig | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/fs/Kconfig b/fs/Kconfig
> index 9f7270f..c36d63b 100644
> --- a/fs/Kconfig
> +++ b/fs/Kconfig
> @@ -124,7 +124,7 @@ config TMPFS_POSIX_ACL
> config HUGETLBFS
> bool "HugeTLB file system support"
> depends on X86 || IA64 || PPC64 || SPARC64 || (SUPERH && MMU) || \
> - (S390 && 64BIT) || BROKEN
> + (S390 && 64BIT) || SYS_SUPPORTS_HUGETLBFS || BROKEN
I'm ok with this patch but it's really crying for some follup patch to
convert all the other architectures to use SYS_SUPPORTS_HUGETLBFS.
Ralf
parent reply other threads:[~2009-06-16 10:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1243471666-27915-4-git-send-email-ddaney@caviumnetworks.com>]
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=20090616102034.GC13622@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ddaney@caviumnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=wli@kernel.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