On Wed, Feb 22, 2012 at 03:17:23PM +0200, Pekka Enberg wrote:

On Wed, Feb 22, 2012 at 1:53 PM, Rafael Aquini [off-list ref] wrote:

quoted

This, alongside with all other data dumped in OOM events, is very helpful
information in diagnosing why there was an OOM condition specially when
kernel code is under investigation.

Signed-off-by: Rafael Aquini <redacted>

Makes sense. Do you have an example how an out-of-memory slab cache
dump looks like?

Yes I do have a couple of dumps taken from some dabbler testing I was
performing. Would it be interesting to introduce a sample at the commit message, or
among the Documentation paragraphs?

Minor style nit: just define the zeroed variables in this block.

I will adjust those.

Thanks for your feedback!
-- 
Rafael Aquini [off-list ref]
Software Maintenance Engineer
Red Hat, Inc.
+55 51 4063.9436 / 8426138 (ext)

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>