Andrea,
I've tried 2.2.17pre6aa2, and unfortunately it still behaves quite
fragile.
[root@plucky memtest-0.0.3]# free
total used free shared buffers cached
Mem: 7772 7140 632 0 320 1956
-/+ buffers/cache: 4864 2908
Swap: 1759076 2180 1756896
[root@plucky memtest-0.0.3]# ./mmap001
VM: killing process bash
VM: killing process mmap001
(logged in again)
[root@plucky memtest-0.0.3]# ./mmap001
VM: killing process portmap
VM: killing process mmap001
Killed
[root@plucky memtest-0.0.3]# ./mmap001
VM: killing process syslogd
VM: killing process klogd
VM: killing process mmap001
Killed
Now with *32Mb* of RAM:
[root@plucky memtest-0.0.3]# ./mmap001
VM: killing process crond
VM: killing process portmap
VM: killing process syslogd
VM: killing process mmap001
Killed
I perfectly understand your changes in 2.2.17pre6aa2, but as this test
shows, it doenst fix the problem in practice.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jun 26 2000 - 21:00:09 EST