By: Anon (no.delete@this.spam.com), April 6, 2021 9:43 am
Room: Moderated Discussions
sr (nobody.delete@this.nowhere.com) on April 6, 2021 7:12 am wrote:
> Why so afraid of aborts? Your CPU speculate and aborts all
> the time, TM just expands that feature to coherent memory.
The problem is that current implementation is only useful for a very limited scenario, the mostly reads scenario.
> And traditional software version to do atomic memory operations to coherent memory is to lock memory
> regions - and that sucks, firstly by that it's not protected by hardware. And because of that it
> makes multithreading so complicated that almost nobody can do it to anything but the most simplest
> things. Any real problems needs to rely on third-party locking libraries and so on.
Or MVCC.
And I think it may outperform HTM in the mostly reads case.
> Why so afraid of aborts? Your CPU speculate and aborts all
> the time, TM just expands that feature to coherent memory.
The problem is that current implementation is only useful for a very limited scenario, the mostly reads scenario.
> And traditional software version to do atomic memory operations to coherent memory is to lock memory
> regions - and that sucks, firstly by that it's not protected by hardware. And because of that it
> makes multithreading so complicated that almost nobody can do it to anything but the most simplest
> things. Any real problems needs to rely on third-party locking libraries and so on.
Or MVCC.
And I think it may outperform HTM in the mostly reads case.
