Messages in this thread | | | Date | Mon, 28 Jul 2008 15:50:04 -0700 | From | Jeremy Fitzhardinge <> | Subject | Re: combinatorial explosion in lockdep |
| |
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
| |