On Wed, Aug 15, 2012 at 3:34 PM, Ezequiel Garcia <elezegarcia@xxxxxxxxx> wrote: > As you can see this patch prevents to trace a kmem event if the allocation > fails. > > I'm still unsure about tracing or not this ones, and I'm considering tracing > failures, perhaps with return=0 and allocated size=0. > > In this case, it would be nice to have SLxB all do the same. > Right now, this is not the case. > > You can see how slob::kmem_cache_alloc_node traces independently > of the allocation succeeding. > I have no problem trying a fix for this, but I don't now how to trace > this cases. > > Although it is a corner case, I think it's important to define a clear > and consistent behaviour to make tracing reliable. Agreed on consistency. I think it's valuable to be able to trace allocation failures and let userspace filter them out if they don't need them. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>