Hi,
I too tested to stress the new VM
Quintelas mmap002 "deadlocks" for me.
PPro, 96 MB, UP
active: 22337 (I think this varies, have too lock a 2nd time)
inactive_dirty: 324 varies
inactive_clean: 0
free: 288
... 1x 512 = 512 kB
... 2 x 16 + 1 x 32 + 1 x 64 = 640 kB
My feeling when looking at
On Tue, 19 Sep 2000, Anton Petrusevich wrote:
> please, check carefully Rik's VM patch, it definitly contains a
> deadlock, which can be seen on low-memory computers. Try mem=8m. I
> wasn't able to use any Rik patch since against -test8 (-t8-vmpatch{2,4},
> -test9-pre{1,2}). It boots fine(mem=16m
On Tue, 19 Sep 2000, Anton Petrusevich wrote:
> Hi Linus,
>
> please, check carefully Rik's VM patch, it definitly contains a
> deadlock, which can be seen on low-memory computers. Try mem=8m. I
> wasn't able to use any Rik patch since against -test8 (-t8-vmpatch{2,4},
> -test9-pre{1,2}). It boo
Hi Linus,
please, check carefully Rik's VM patch, it definitly contains a
deadlock, which can be seen on low-memory computers. Try mem=8m. I
wasn't able to use any Rik patch since against -test8 (-t8-vmpatch{2,4},
-test9-pre{1,2}). It boots fine(mem=16m), but then stalls begin for some
time and f
4 matches
Mail list logo