linux-kernel - Re: [PATCH] FRV: Permit large kmalloc allocations

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20061002085744.55bf8c28.rdunlap@xenotime.net>
Date:	Mon, 2 Oct 2006 08:57:44 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	David Howells <dhowells@...hat.com>
Cc:	akpm@...l.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] FRV: Permit large kmalloc allocations

On Mon, 02 Oct 2006 16:37:08 +0100 David Howells wrote:

> From: David Howells <dhowells@...hat.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@...hat.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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/