Re: locking hierarchy based on lockdep

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



 > i like your idea of using lockdep to document locking hierarchies.

Yes, it's definitely a cool idea.  I think the current implementation
is not that useful, since it jams all the unrelated kernel locks into
a single ordered list, when in fact many locks simply have no ordering
relationship at all because they're never both taken.  This makes the
list hard to read and in fact loses the information of which locks
have been taken together.

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

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux