applesvsoranges

This post took me back to my school days as well (Raleigh, NC). It was my go-to place whenever an assignment kept me late at the library, whenever I was bored of cooking but could only afford to spend as much and whenever I craved my usual scrambled eggs with cheese, toast and chocolate waffles. Waffle House was always open and always welcoming. Fond memories.

This fun thing happened there as well : https://abcnews.go.com/US/north-carolina-state-university-st...

Thanks, this adds a whole new perspective for me wrt mutexes. I wasn't aware of all these other usage patterns for them at all.

Most of my work is in the OS, drivers and low level space, and I'm a beginner there as well, hence the short critical sections under a single owner are the only places I had encountered them before.

>> With a normal mutex we would be fine, since you only one lock can exist and it doesn’t matter if we unlock it on a thread other than the one we locked it from.

Sorry if this is a dumb question, but I'm confused. Aren't mutexes always supposed to have ownership which implies that only the locking thread can unlock them?

Yeah. I used TI-RTOS a couple of years ago for some work and the whole experience was very different. The most unique part was that the RTOS came bundled with a development GUI integrated into the IDE where you could create threads, mailboxes and other such RTOS primitives. I don't think I liked using it very much though.

Surprised to see that they killed the project.