Messages in this thread | | | Date | Mon, 28 Jul 2008 15:56:51 -0700 (PDT) | Subject | Re: combinatorial explosion in lockdep | From | David Miller <> |
| |
From: Jeremy Fitzhardinge <jeremy@goop.org> Date: Mon, 28 Jul 2008 15:50:04 -0700
> 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?
I could check that, but it won't keep this from happening and being triggerable by a trivial userland program setting scheduler affinities.
| |