Thread (48 messages) 48 messages, 12 authors, 2011-10-11

Re: [PATCH 19/24] sunrpc: Remove unnecessary OOM logging messages

From: Boaz Harrosh <hidden>
Date: 2011-08-29 22:02:20
Also in: linux-nfs, lkml

On 08/29/2011 02:37 PM, David Miller wrote:
From: "Myklebust, Trond" <redacted>
Date: Mon, 29 Aug 2011 14:36:17 -0700
quoted
Big NACK...

By whose standard are those "not useful"?
By mine, that's for sure.  It's duplicating something that the allocation
layers are already going to print.
I have a question about that. Are the dprints going to show the stack backtrace?
Otherwise how can I see which exact allocation failed and was not properly handled?

If yes above? then I'm not sure I like it either, because am I'll be getting a full
stack backtrace for every failed allocation?

But I might like it if I try. How do I turn on allocation failures prints?
Can I filter out to print only GFP_KERNEL failures and or other GFP combinations?

Thanks 
Boaz
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help