Designing a thread-safe routine

A thread safe routine should be careful of the following:

  • Keep routine non-reentrant
  • Avoid using “static” variables. If not protected, you might find unwanted results
  • Use atomic variables for things like states, shared variables (locks such as mutex, semaphore, spinlock are expensive)
  • Always allocate big local variable (> 10k) on heap
Advertisements

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s