Messages in this thread |  | | Date | Wed, 31 Oct 2001 17:55:25 -0800 | From | Ben Smith <> | Subject | Re: Google's mm problem - not reproduced on 2.4.13 |
| |
>>>*Just in case* it's oom-related I've asked Ben to try it with one less than >>>the maximum number of memory blocks he can allocate. >>> >>I've run this test with my 3.5G machine, 3 blocks instead of 4 blocks, >>and it has the same behavior (my app gets killed, 0-order allocation >>failures, and the system stays up. >> > > If you still have swap free at the point where the process > gets killed, or if the memory is file-backed, then we are > positive it's a kernel bug.
This machine is configured without a swap file. The memory is file backed,
though (read-only mmap, followed by a mlock).
- Ben
Ben Smith Google, Inc
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |