Re: [PATCH v3] lockdep: Make MAX_STACK_TRACE_ENTRIES configurable.

[Peter Zijlstra]

On Wed, 2010-04-21 at 14:12 +0200, John Kacur wrote:
> 
>  lock-classes:                         1330 [max: 8191]
>  direct dependencies:                 12754 [max: 16384]
>  indirect dependencies:               33245
>  all direct dependencies:             49074
>  dependency chains:                   19641 [max: 32768]

Right, so each dependency also gets a stack trace, see
add_lock_to_list().

>  dependency chain hlocks:             73246 [max: 163840]
>  in-hardirq chains:                      25
>  in-softirq chains:                       0
>  in-process chains:                   19616
>  stack-trace entries:                262144 [max: 262144]
> 
> 
> I'm looking at more details in /proc/lockdep and friends to see if
> I can find any more details, or something that looks amiss.
> 
It might be useful to add a counter that simply counts all save_trace()
invocations, and maybe split them out according to new_bit in
mark_lock().

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/