> -----Original Message----- > From: David Miller [mailto:davem@xxxxxxxxxxxxx] > Sent: Monday, August 29, 2011 6:04 PM > To: bharrosh@xxxxxxxxxxx > Cc: Myklebust, Trond; joe@xxxxxxxxxxx; bfields@xxxxxxxxxxxx; > neilb@xxxxxxx; linux-nfs@xxxxxxxxxxxxxxx; netdev@xxxxxxxxxxxxxxx; > linux-kernel@xxxxxxxxxxxxxxx > Subject: Re: [PATCH 19/24] sunrpc: Remove unnecessary OOM logging > messages > > From: Boaz Harrosh <bharrosh@xxxxxxxxxxx> > Date: Mon, 29 Aug 2011 14:54:59 -0700 > > > I have a question about that. Are the dprints going to show the stack > backtrace? > > Yes, OOMs give full stack backtraces. > > > 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? > > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
