Anton wrote:
> We've had customer situations where that information would have been
> very useful.
I haven't looked closely, but when I provoked the oom killer last week
a few times while working on something else, I did notice that the
printk's that came out were a page or two, per kill. Apparently it
is the arch-specific show_mem() routine that was so verbose - this
was on an ia64 SN2.
Do we really need that lengthy an oom printk? If the other arch's
tend to be a little more terse, then I guess you could catalog my
complaint as a "personal problem" or at least an "arch problem."
In support of this ratelimiting, the other call from main line kernel
code to show_mem(), after the __alloc_pages() message:
page allocation failure. order:%d, mode:0x%x
is already ratelimited. Seems like a good idea.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[EMAIL PROTECTED]> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
