2 ms·
Oh, I agree, it is all tradeoffs. Losing the ability to cheaply share objects, including closures, is a big tradeoff though. BTW lock free queues and data str
by gpderetta 6y ago
Oh, I agree, it is all tradeoffs.
Losing the ability to cheaply share objects, including closures, is a big tradeoff though.
BTW lock free queues and data structures are pretty much required for interprocess sharing, unless you really want to deal with robust mutexes (and you don't!)
- ncmncm 6y agoI do it. Without mutexes. I don't count single-writer ring buffers among the ordinary lock-free queues, because there is no competition for access, and cache lines never change ownership. So, none of the overheads show up. And, they are very easy to get right, so pose none of the risk of subtle heisenbugs. Being able to kill and add downstream clients at random is worth a lot of architectural rejiggery.