Using the holidays for a 2-week coding session. Writing a new transactional memory manager that’s O(1) for all operations, completely non-blocking and progress-guaranteeing, and uses atomics only for writes.
-
Show this thread
-
Replying to @TimSweeneyEpic
How did your project go? Would love to read more about it.
1 reply 0 retweets 0 likes -
Replying to @kccqzy
The core idea works. It’s too slow but within the range that it may be viable with optimization.
1 reply 0 retweets 1 like
Replying to @TimSweeneyEpic @kccqzy
Will say more about it later, but the interrelations of transactions, memory management, and speculative execution constructs are interesting and need to be explained as a whole.
4:13 PM - 13 Jan 2020
0 replies
0 retweets
1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.