Two more additional data points,
1) partially kernel-unrelated. MDK's "make" macro didn't support
alpha's /proc/cpuinfo output, "make -j$numprocs" became "make -j" and
fun ensued.
2) I agree that 200MB into swap and 200MB into cache isn't bad per se,
but when it triggers the OOM killer it is bad.
Alan suggested that I insert the following into the OOM killer code, as
the last test before returning 1.
cnt++;
if ((cnt % 5000) != 0)
return 0;
I did this, and while watching "vmstat 3", the cache was indeed being
trimmed, whereas it was not before.
So, the OOM killer appears to be getting triggered early, but the rest
of the report was my screwup not the kernel.
-- Jeff Garzik | A recent study has shown that too much soup Building 1024 | can cause malaise in laboratory mice. MandrakeSoft | - 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/