There are two correct ways to write lock-free code: 1. Carefully study existing literature and the memory model of your lang/platform, verify your approach and solution with 10x the rigour you normally would. 2. Find someone who will do the above and pay them to do it.
-
-
"The business we're in is more sociological than technological, more dependent on workers' abilities to communicate with each other than their abilities to communicate with machines." — Tom DeMarco, Peoplewarehttps://twitter.com/TartanLlama/status/1220057649527623680?s=19 …
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
People being taught: "Copy is Expensive! Avoid copy when you can!" People working: "I wanna give this thread data, guess I'll just lock while they use it" Copy isn't that expensive. Doesn't apply to every situation of course. But it definitely is a mentality.pic.twitter.com/JHfaIj8lin
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Why didn't you stop me Sy, why didn't you stop me!? *Cries in atomic::compare_and_swap*
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
lock free also does not mean ‘faster’ eg https://www.cs.bgu.ac.il/~hendlerd/papers/flat-combining.pdf …
-
Nice paper! Lock-free is definitely not always faster, but non-lock-free also doesn’t mean the naive “using a lock”.
Kraj razgovora
Novi razgovor -
-
- Još 1 odgovor
Novi razgovor
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.