Re: combinatorial explosion in lockdep

[Jeremy Fitzhardinge]

David Miller wrote:
> The triggering event seems to be kstopmachine as done by the first
> module load.  This seems to create the situation where we do double RQ
> locking on essentially all the run queues, in order to move the
> kstopmachine threads around to their proprer cpus.  I think this is
> what starts to make the lockdep dependency chains huge.
>   

Does Rusty's stop_machine rewrite which puts the threads on the correct 
cpus to start with at least mitigate the symptoms?

   J
--
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/