https://bugzilla.novell.com/show_bug.cgi?id=672055 https://bugzilla.novell.com/show_bug.cgi?id=672055#c3 --- Comment #3 from Mel Gorman <mgorman@novell.com> 2011-02-16 14:22:19 UTC --- (In reply to comment #1)
Does it happen with overcommit_memory == 1? 0 means a heuristic which might refuse to overcommit.
Agreed. mmap() would be expected to fail if /proc/sys/vm/overcommit_memory was 0 (the default). From the documentation "When this flag is 0, the kernel attempts to estimate the amount of free memory left when userspace requests more memory."
I don't think the former is a bug anyway. Why do you think it is?
The map of DVD may a bug though.
Maybe. While this is x86-64, was the test program a 64-bit binary? If it was 32-bit, a mmap() of a large file would still be expected to fail due to a lack of virtual addressing space and have nothing to do with available memory. On a similar vein, was O_LARGEFILE specified to open() and _LARGEFILE64_SOURCE defined? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.