-----Original Message-----
From: David Miller [mailto:davem@davemloft.net]
Sent: Monday, August 29, 2011 6:04 PM
To: bharrosh@panasas.com
Cc: Myklebust, Trond; joe@perches.com; bfields@fieldses.org;
neilb@suse.de; linux-nfs@vger.kernel.org; netdev@vger.kernel.org;
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 19/24] sunrpc: Remove unnecessary OOM logging
messages

From: Boaz Harrosh <redacted>
Date: Mon, 29 Aug 2011 14:54:59 -0700

quoted

I have a question about that. Are the dprints going to show the

stack

backtrace?

Yes, OOMs give full stack backtraces.

quoted

If yes above? then I'm not sure I like it either, because am I'll be

getting a full

quoted

stack backtrace for every failed allocation?

They've been doing this for years, so obviously they haven't bothered
you
enough to care up to this point.

All of this pushback is pure uneducated noise, please stop blocking
progress
with poorly informed objections.

I can see that slub.c has the slab_out_of_memory() function that
(although ratelimited) warns you if the allocation failed. However I
can't find any equivalent for slab.c or slob.c.

Trond