It may well be borderline but its certainly interesting the rmap vm thinks
it is out of memory first. Whats the overcommitted_AS value just before it
reports that it cannot allocate memory.
I'm also interested to know if it occurs with a lot more swap. It might be
a false report coming from a bug in the vm accounting changes too
-
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/