FYI: yes, that's the same problem. After some debugging I found the
exact reason of the bug, and as Daniel claimed a few weeks ago it is
really a VM problem, not an mlock problem. And it's one thing that I
didn't noticed while rewriting the VM, so it is reproducible on all 2.4
kernels out there, no matter what VM is in them. The kswapd infinite
loop that can trigger with the -ac VM when all the ZONE_DMA is
unfreeable (now fixed in mainline with classzone) have nothing to do
with this google problem, kswapd is right here to spend cpu time, the
bug is not kswapd activation.
I just sent Ben (at Google) a patch that fixes the problem completly for
me and for him and I'll try to release the real fix in the next days.
(so far it's a dirty workaround, that is just usable fine in their and
my memory configuration but it's not general purpose yet, but it's been
more than enough to proof my theory so far and I've in mind how to fix
it properly, tomorrow I hope I will implement it).
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/