So, some further investigation shows that on sparc (but not sparc64)
the vmspace for userland processes is pretty huge - the t_mincore test
already has a vmspace vm-vm_map.size value of 9118 pages before it even
does the first mmap. Given the low resource limits cited upthread (~3500
locked pages)
On Thu, 24 May 2012, Martin Husemann wrote:
On Wed, May 23, 2012 at 07:15:41PM +0100, David Laight wrote:
What are the default ulimit values?
Good point. Page size is 4k, with 32MB the limits are
# ulimit -a
time (-t seconds) unlimited
file (-f blocks )
In the regular sparc test runs on qemu the emulated sparc machine only
has 32MB of ram. In this setup the /usr/tests/lib/libc/sys/t_mincore test
mincore_resid fails. If we allow qemu ot provide more memory, the test
succeeds.
The part of the test that fails in low memory environments is:
An
I have not tried the test, but ntpd(8) on m68k machines
(with less than 32MB) always complains mlockall() failed.
---
Izumi Tsutsui
On Thu, May 24, 2012 at 01:30:39AM +0900, Izumi Tsutsui wrote:
I have not tried the test, but ntpd(8) on m68k machines
(with less than 32MB) always complains mlockall() failed.
Yeah, that is because libc already is too big or something.
However, in this case the mlockall() suceeds.
Martin
On Wed, May 23, 2012 at 06:15:32PM +0200, Martin Husemann wrote:
In the regular sparc test runs on qemu the emulated sparc machine only
has 32MB of ram. In this setup the /usr/tests/lib/libc/sys/t_mincore test
mincore_resid fails. If we allow qemu ot provide more memory, the test
succeeds.
On Wed, May 23, 2012 at 07:15:41PM +0100, David Laight wrote:
What are the default ulimit values?
Good point. Page size is 4k, with 32MB the limits are
# ulimit -a
time (-t seconds) unlimited
file (-f blocks ) unlimited
data (-d kbytes ) 65536
stack
