lkml.org 
[lkml]   [2008]   [Jul]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: combinatorial explosion in lockdep
From
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.


\
 
 \ /
  Last update: 2008-07-29 00:59    [W:0.073 / U:0.300 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site