aboutsummaryrefslogtreecommitdiffstats
path: root/cdr
diff options
context:
space:
mode:
authorrussell <russell@f38db490-d61c-443f-a65b-d21fe96a405b>2008-07-02 12:08:33 +0000
committerrussell <russell@f38db490-d61c-443f-a65b-d21fe96a405b>2008-07-02 12:08:33 +0000
commitffd283a966286925b2400133d317714793e657fe (patch)
tree9c4f5c42e3abf5a60c90f0efa5fc1c0cba8e12e8 /cdr
parent6d96663d29a18c187c17af46fed162cad9024726 (diff)
Add a locking section to the coding guidelines document.
This section covers some locking fundamentals, as well as some information on locking as it is used in Asterisk. It describes some of the ways that are used and could be used to achieve deadlock avoidance. It also demonstrates the unfortunate conclusion that with the use of recursive locks, none of the constructs in use today are failsafe from deadlocks. Finally, it makes some recommendations for new code being written. As proper locking strategies is a complex subject, this section still has room for expansion and improvement. This is a result of collaboration between Luigi Rizzo and myself on the asterisk-dev mailing list. git-svn-id: http://svn.digium.com/svn/asterisk/trunk@127363 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'cdr')
0 files changed, 0 insertions, 0 deletions