Date: Fri, 15 Feb 2013 22:36:31 -0800 From: Oleksandr Tymoshenko <gonzo@bluezbox.com> To: Andre Oppermann <andre@freebsd.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r246204 - head/sys/arm/include Message-ID: <85D50AAD-F600-4EA5-9F92-146B2D6EA04C@bluezbox.com> In-Reply-To: <201302011026.r11AQVL9068427@svn.freebsd.org> References: <201302011026.r11AQVL9068427@svn.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2013-02-01, at 2:26 AM, Andre Oppermann <andre@freebsd.org> wrote: > Author: andre > Date: Fri Feb 1 10:26:31 2013 > New Revision: 246204 > URL: http://svnweb.freebsd.org/changeset/base/246204 > > Log: > Add VM_KMEM_SIZE_SCALE parameter set to 2 (50%) for all ARM platforms. > > VM_KMEM_SIZE_SCALE specifies which fraction of the available physical > memory, after deduction of the kernel itself and other early statically > allocated memory, can be used for the kmem_map. The kmem_map provides > for all UMA/malloc allocations in KVM space. > > Previously ARM was using a fixed kmem_map size of (12*1024*1024) = 12MB > without regard to effectively available memory. This is too small for > recent ARM SoC with more than 128MB of RAM. > > For reference a description of others related kmem_map parameters: > > VM_KMEM_SIZE default start size of kmem_map if SCALE is > not defined > VM_KMEM_SIZE_MIN hard floor on the kmem_map size > VM_KMEM_SIZE_MAX hard ceiling on the kmem_map size > VM_KMEM_SIZE_SCALE fraction of the available real memory to > be used for the kmem_map, limited by the > MIN and MAX parameters. > > Tested by: ian > MFC after: 1 week Hi Andre, this commit brake my Pandaboard with 1GB of memory. It panics early with following message: kmem_suballoc: bad status return of 3 If you need additional info/debugging - just let me know.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?85D50AAD-F600-4EA5-9F92-146B2D6EA04C>