• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: pthread_cond_signal and priority inversion
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: pthread_cond_signal and priority inversion


  • Subject: Re: pthread_cond_signal and priority inversion
  • From: Ross Bencina <email@hidden>
  • Date: Tue, 24 May 2016 18:24:50 +1000

I don't see how that could block for very long.

The number of instructions in the critical section is not relevant if the thread holding the lock gets pre-empted. That's the definition of priority inversion.

Of course the shorter the critical section, the less likely priority inversion will ever happen.

@Michael, I guess you need to also consider whether lock contention is actually possible. A spinlock on a never-contended lock would be safe for example.

Ross.

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


References: 
 >Re: pthread_cond_signal and priority inversion (From: Kyle Neideck <email@hidden>)
 >Re: pthread_cond_signal and priority inversion (From: Paul Davis <email@hidden>)
 >Re: pthread_cond_signal and priority inversion (From: Ross Bencina <email@hidden>)
 >Re: pthread_cond_signal and priority inversion (From: Brian Willoughby <email@hidden>)

  • Prev by Date: Re: pthread_cond_signal and priority inversion
  • Next by Date: Re: pthread_cond_signal and priority inversion
  • Previous by thread: Re: pthread_cond_signal and priority inversion
  • Next by thread: Re: pthread_cond_signal and priority inversion
  • Index(es):
    • Date
    • Thread