On Tue 31-10-17 15:52:47, Peter Zijlstra wrote: [...] > If we want to save those stacks; we have to save a stacktrace on _every_ > lock acquire, simply because we never know ahead of time if there will > be a new link. Doing this is _expensive_. > > Furthermore, the space into which we store stacktraces is limited; > since memory allocators use locks we can't very well use dynamic memory > for lockdep -- that would give recursive and robustness issues. Wouldn't stackdepot help here? Sure the first stack unwind will be costly but then you amortize that over time. It is quite likely that locks are held from same addresses. -- Michal Hocko SUSE Labs -- 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>
