On 08/12/2009 11:22 AM, Pierre Ossman wrote:
Will it still trigger the OOM killer with this patch, or will things
behave slightly more gracefully?
I don't think you mentioned the OOM killer in your original report? Did
it trigger?
I might have things backwards here, but I though the OOM killer started
doing its dirty business once you got that memory allocation failure
dump.
I don't think the oom killer should trigger on GFP_ATOMIC failures, but
don't know for sure. If you don't have a trace saying it picked a task
to kill, it probably didn't.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
