pthread_mutex_lock() accepts a single pointer to a mutex to lock. If the mutex already happens to be locked, the caller will go to sleep. When the function returns, the caller will be woken up (obviously), and the caller will also now hold the lock. This call either returns zero on success.

"dead list" that contains all stopped threads and then have a special cleanup thread that simply waits for an item to be added to the list. The cleanup thread calls pthread_join() to merge it with itself. Now your entire cleanup will be handled neatly and efficiently in a single thread.

mutexes are used to serialize access to *shared data*. Don't use them for non-shared data, and don't use them if your program's logic ensures that only one thread is accessing a particular data structure at a single time.

if you are using shared data, use mutexes for both reading and writing. Surround your read and write sections with pthread_mutex_lock() and pthread_mutex_unlock(), or use them any time a program's invariant is temporarily broken.

pthread_mutex_destroy() does not free the memory used to store the pthread_mutex_t. It's up to you to free() your own memory. Also remember that both pthread_mutex_init() and pthread_mutex_destroy() return zero on success.

You should always unlock a mutex that you've locked as soon as safely possible (to increase performance). And you should never unlock a mutex that you don't hold a lock for

When you call pthread_mutex_trylock() you'll attempt to lock the mutex. If the mutex is currently unlocked you'll get the lock, and this function will return zero. However, if the mutex is locked this call won't block. Rather, it will return a non-zero EBUSY error value.

pthread_cond_wait() simultaneously unlock the mutex (so that other threads can modify the linked list) and wait on the condition (so that pthread_cond_wait() will wake up when it is "signalled" by another thread). Now that the mutex is unlocked, other threads can access and modify the linked list, possibly adding items

pthread_cond_wait() call has not yet returned. Unlocking the mutex happens immediately, but waiting on the condition mycond is normally a blocking operation, meaning that our thread will go to sleep, consuming no CPU cycles until it is woken up.

This is exactly what we want to happen. Our thread is sleeping, waiting for a particular condition to become true, without performing any kind of busy polling that would waste CPU time. From our thread's perspective, it's simply waiting for the pthread_cond_wait() call to return.

Immediately after unlocking the mutex, thread 2 calls the function pthread_cond_broadcast(&mycond). By doing so, thread 2 will cause all threads waiting on the mycond condition variable to immediately wake up. This means that our first thread (which is in the middle of a pthread_cond_wait() call) will now wake up.

After thread 2 called pthread_cond_broadcast(&mymutex) you might think that thread 1's pthread_cond_wait() will immediately return. Not so! Instead, pthread_cond_wait() will perform one last operation: relock mymutex. Once pthread_cond_wait() has the lock, it will then return and allow thread 1 to continue execution.

I've been a musician longer than I've been an actor.

I love the flow of the game. There's a certain fluidity to basketball. I don't enjoy watching baseball or football in the same way.

Never forget that to forgive yourself is to release trapped energy that could be doing good work in the world.

Always go with the choice that scares you the most because thats the one that is going to require the most from you.

Me not working hard? Yeah, right - picture that with a Kodak.

We can't command our love, but we can our actions.

We got bigger, much scarier competitors. We ended up with Microsoft, a company with all the money in the world, the way I look at those guys. And IBM, another company that, historically, dwarfed us.

I truly love coming to work every day.

I'd like to work more, but I don't just want to do kind of generic characters. I want to do interesting characters, and I'd like to be cast against type.

In climbing you are always faced with new problems in which you must perform using intuitive movements and then later analyze them to figure out why they work and then learn from them.

You watch 'Whale Rider,' and I defy you to not get teary-eyed at the end there.

Playing 'bop' is like playing Scrabble with all the vowels missing.

Yes, but personally I was never a big acid head.

I know about having days off. They can be helpful sometimes, especially late in the year. It's just key to go out there and establish early, especially in this park where they can put up some crooked numbers early.

Design means being good not just looking good.

The foundation of every state is the education of its youth.

My favorite literature to read is fairly dry history. I like the framework, and my imagination can do the rest.

Microsoft Research has a thing called the Sense Cam that, as you walk around, it's taking photos all the time. And the software will filter and find the ones that are interesting without having to think, 'Let's get out the camera and get that shot.' You just have that, and software helps you pick what you want.

I am the product of living in dictatorships. And someone who's lived in dictatorships and not being allowed to be themselves, it cherishes the ability to be yourself and to have feelings and to speak them when asked. And I am that person.

And I'm not an actress. I don't think I am an actress. I think I've created a brand and a business.

Revolution as an ideal concept always preserves the essential content of the original thought: sudden and lasting betterment.

When you are pursuing your dreams, they will call you CRAZY because they are LAZY. They never know you are a HERO who just jumped away from step ZERO. Stay away from negative people; they will only pollute you.

The function of good software is to make the complex appear to be simple.

Advice? Look at your pay statements.