linux32 sysctl limits?
Steve Kargl
sgk at troutmask.apl.washington.edu
Fri Oct 8 23:12:10 UTC 2010
On Sat, Oct 09, 2010 at 01:20:13AM +0300, Kostik Belousov wrote:
> On Fri, Oct 08, 2010 at 03:17:01PM -0700, Steve Kargl wrote:
> > 'man linux' does not list or describe the following sysctl
> > variables.
> >
> > compat.linux32.maxvmem: 0
> > compat.linux32.maxssiz: 67108864
> > compat.linux32.maxdsiz: 536870912
> >
> > Are there any limitations with setting these to
> > say 1G for stack and 4G for data on a system with
> > 16G of memory?
>
> The linux ABI processes are 32bit, so you cannot reallistically assign
> 4Gb to maxdsiz. The space between data (bss) end and stack bottom is
> used for mappings, so it should be kept large enough.
Does this mean that maxssiz+maxdsiz=3G would allow
1G for mappings? The only linux app that will be
running is matlab (and I suppose any children processes
of matlab).
--
Steve
More information about the freebsd-amd64
mailing list