Search results

Jump to: navigation, search

Page title matches

  • ... no deadlock occurs if two threads create a Lock2 object if they lock same mutexes but in different order. * [[Important Mutexes]]
    2 KB (245 words) - 11:45, 4 November 2013
  • In the code of Yate there are some noteworthy mutexes that have program-wide implications. *[[Mutexes and locking]]
    2 KB (251 words) - 11:46, 4 November 2013

Page text matches

  • ...ame=engine,type=system,version=0.8.7;plugins=9,inuse=2,threads=5,workers=1,mutexes=13,locks=0
    1 KB (158 words) - 15:58, 18 January 2013
  • ... no deadlock occurs if two threads create a Lock2 object if they lock same mutexes but in different order. * [[Important Mutexes]]
    2 KB (245 words) - 11:45, 4 November 2013
  • ...ne or more threads are trying to acquire two or more [[Mutexes and locking|Mutexes]] waiting for each other to finish. Since each is trying to acquire other's ...uire one will issue a [[Debug Output#Debugging_levels|DebugFail]] message. Mutexes hold the name and address of the thread that acquired them, provided the th
    2 KB (356 words) - 11:46, 4 November 2013
  • In the code of Yate there are some noteworthy mutexes that have program-wide implications. *[[Mutexes and locking]]
    2 KB (251 words) - 11:46, 4 November 2013
  • * [[Mutexes and locking]] * [[Important Mutexes]]
    4 KB (524 words) - 09:01, 10 March 2016
  • ; Use a prime number to make sure transaction mutexes are properly distributed
    43 KB (6,355 words) - 13:27, 1 October 2019
  • YATE-MIB::mutexes.0 = Counter32: 267
    9 KB (1,268 words) - 15:48, 31 October 2013

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)

Personal tools
Namespaces

Variants
Views
Actions
Preface
Configuration
Administrators
Developers