I spent Friday night and most of Saturday writing a term paper on the use
of mutex semaphores to manage access to critical code sections in priority
scheduled embedded real-time systems. Got that?
He likes to pop out these phrases every once in a while to ruffle his geeky knowledge feathers. I think he also enjoys the blank look he causes on everyone's face when he says stuff like this. I like the fact that I can get right back at him by regaling him with celebrity gossip or the newest plot twist on The O.C.
3 comments:
My face would look like this for either subject... :|
well he could be putting some of his nerdiness in action, which i find is much scarier with engineers (how do they take something apart, and put it back together, but without all the pieces?)
If it helps any, a mutex semaphore is a lock to make sure that only one process can execute a block of code at a time, with signals to let other processes know when it's locked and when it's clear.
Like, imagine it's December, and you (a process) had to share your winter coat (the code block) with five strangers (other processes) you didn't know. You all need the coat, but you can't all use it at one time, because the coat will be destroyed (program crash) if five people try to wear it at once. And you can't hand it off to each other, because you're all strangers. But there's a coat check girl (the semaphore) that keeps track of the coat. When you want the coat, you go ask her for it, and if it's available, she'll give it to you. If it's not available, she'll call you when it becomes available. So you get the coat from her, and when you're done with it, you give it back to her, so the next person can use it.
Post a Comment