From: Randy Dunlap <rdunlap@xenotime.net>
To: David Howells <dhowells@redhat.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] FRV: Permit large kmalloc allocations
Date: Mon, 2 Oct 2006 08:57:44 -0700 [thread overview]
Message-ID: <20061002085744.55bf8c28.rdunlap@xenotime.net> (raw)
In-Reply-To: <20061002153708.22649.96337.stgit@warthog.cambridge.redhat.com>
On Mon, 02 Oct 2006 16:37:08 +0100 David Howells wrote:
> From: David Howells <dhowells@redhat.com>
>
> Permit kmalloc() to make allocations of up to 32MB if so configured. This may
> be useful under NOMMU conditions where vmalloc() can't do this.
>
> Signed-Off-By: David Howells <dhowells@redhat.com>
> ---
>
> arch/frv/Kconfig | 8 ++++++++
> 1 files changed, 8 insertions(+), 0 deletions(-)
>
> diff --git a/arch/frv/Kconfig b/arch/frv/Kconfig
> index f7b171b..69f9846 100644
> --- a/arch/frv/Kconfig
> +++ b/arch/frv/Kconfig
> @@ -86,6 +86,14 @@ config HIGHPTE
> with a lot of RAM, this can be wasteful of precious low memory.
> Setting this option will put user-space page tables in high memory.
>
> +config LARGE_ALLOCS
> + bool "Allow allocating large blocks (> 1MB) of memory"
> + help
> + Allow the slab memory allocator to keep chains for very large memory
> + sizes - upto 32MB. You may need this if your system has a lot of RAM,
up to (2 words)
> + and you need to able to allocate very large contiguous chunks. If
> + unsure, say N.
> +
> source "mm/Kconfig"
---
~Randy
next prev parent reply other threads:[~2006-10-02 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-02 15:37 David Howells
2006-10-02 15:57 ` Randy Dunlap [this message]
2006-10-02 16:27 ` David Howells
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=20061002085744.55bf8c28.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®