home.social

#atomics — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #atomics, aggregated by home.social.

fetched live
  1. osdev-libstdc: реализация std::atomic и spin_lock

    Приветствую! В моей библиотеке ядра уже есть аллокатор , семейство vsnprintf , ctype, string.h, strings.h. Остались только атомики и спинлок, и тогда можно будет доделать семейство malloc в блокировками как того требует стандарт.

    habr.com/ru/articles/1051320/

    #atomic #atomicity #atomics #gcc #builtins #concurrency #multithreading

  2. osdev-libstdc: реализация std::atomic и spin_lock

    Приветствую! В моей библиотеке ядра уже есть аллокатор , семейство vsnprintf , ctype, string.h, strings.h. Остались только атомики и спинлок, и тогда можно будет доделать семейство malloc в блокировками как того требует стандарт.

    habr.com/ru/articles/1051320/

    #atomic #atomicity #atomics #gcc #builtins #concurrency #multithreading

  3. osdev-libstdc: реализация std::atomic и spin_lock

    Приветствую! В моей библиотеке ядра уже есть аллокатор , семейство vsnprintf , ctype, string.h, strings.h. Остались только атомики и спинлок, и тогда можно будет доделать семейство malloc в блокировками как того требует стандарт.

    habr.com/ru/articles/1051320/

    #atomic #atomicity #atomics #gcc #builtins #concurrency #multithreading

  4. Деконструкция GO: CPU, RAM и что там происходит. Reordering, atomics, locks, fences. Часть 1.3

    С постановкой проблем в прошлой статье мы почти закончили и вывели самое важное – природу состояния гонки и состязания за кэш. В этой статье мы также разберем оптимизацию, порождающую часть проблем синхронизации – instructions reordering , а также механизмы решения вышеуказанных проблем. В этот раз снова будет Go Assembler, а также снова будут примеры на Go. В прошлый раз это было необходимое зло во имя соответствия реальности Напоминаю, что эта статья – часть большого цикла разбора языка программирования Golang End 2 End. Но если вы уверены, что понимаете природу многозадачности, многопоточности, проблемы оных, а также то, как выполняются инструкции и пришли разбираться в самых примитивных механизмах синхронизации, то велком Instructions reordering Обычно мы считаем, что CPU добросовестно выполняет свои инструкции последовательно. Ровно так, как мы ему сказали. Но это не всегда верно! Допустим есть код

    habr.com/ru/articles/1025292/

    #go #assembly #cpu #atomics #memory #memorybarrier #reordering #data_race #cache_contention

  5. Деконструкция GO: CPU, RAM и что там происходит. Reordering, atomics, locks, fences. Часть 1.3

    С постановкой проблем в прошлой статье мы почти закончили и вывели самое важное – природу состояния гонки и состязания за кэш. В этой статье мы также разберем оптимизацию, порождающую часть проблем синхронизации – instructions reordering , а также механизмы решения вышеуказанных проблем. В этот раз снова будет Go Assembler, а также снова будут примеры на Go. В прошлый раз это было необходимое зло во имя соответствия реальности Напоминаю, что эта статья – часть большого цикла разбора языка программирования Golang End 2 End. Но если вы уверены, что понимаете природу многозадачности, многопоточности, проблемы оных, а также то, как выполняются инструкции и пришли разбираться в самых примитивных механизмах синхронизации, то велком Instructions reordering Обычно мы считаем, что CPU добросовестно выполняет свои инструкции последовательно. Ровно так, как мы ему сказали. Но это не всегда верно! Допустим есть код

    habr.com/ru/articles/1025292/

    #go #assembly #cpu #atomics #memory #memorybarrier #reordering #data_race #cache_contention

  6. Деконструкция GO: CPU, RAM и что там происходит. Reordering, atomics, locks, fences. Часть 1.3

    С постановкой проблем в прошлой статье мы почти закончили и вывели самое важное – природу состояния гонки и состязания за кэш. В этой статье мы также разберем оптимизацию, порождающую часть проблем синхронизации – instructions reordering , а также механизмы решения вышеуказанных проблем. В этот раз снова будет Go Assembler, а также снова будут примеры на Go. В прошлый раз это было необходимое зло во имя соответствия реальности Напоминаю, что эта статья – часть большого цикла разбора языка программирования Golang End 2 End. Но если вы уверены, что понимаете природу многозадачности, многопоточности, проблемы оных, а также то, как выполняются инструкции и пришли разбираться в самых примитивных механизмах синхронизации, то велком Instructions reordering Обычно мы считаем, что CPU добросовестно выполняет свои инструкции последовательно. Ровно так, как мы ему сказали. Но это не всегда верно! Допустим есть код

    habr.com/ru/articles/1025292/

    #go #assembly #cpu #atomics #memory #memorybarrier #reordering #data_race #cache_contention

  7. Edit: solved, thanks Paul!

    Any bored #RustLang atomics enthusiast around? I'm trying to write a kind of global unique id allocator using fetch_add and compare_exchange but now I'm not even sure if it's possible with the right orderings or if I should just do the simple thing and wrap it in a mutex ...

    play.rust-lang.org/?version=st

    #rust #atomics

  8. Edit: solved, thanks Paul!

    Any bored #RustLang atomics enthusiast around? I'm trying to write a kind of global unique id allocator using fetch_add and compare_exchange but now I'm not even sure if it's possible with the right orderings or if I should just do the simple thing and wrap it in a mutex ...

    play.rust-lang.org/?version=st

    #rust #atomics

  9. Edit: solved, thanks Paul!

    Any bored #RustLang atomics enthusiast around? I'm trying to write a kind of global unique id allocator using fetch_add and compare_exchange but now I'm not even sure if it's possible with the right orderings or if I should just do the simple thing and wrap it in a mutex ...

    play.rust-lang.org/?version=st

    #rust #atomics

  10. Edit: solved, thanks Paul!

    Any bored #RustLang atomics enthusiast around? I'm trying to write a kind of global unique id allocator using fetch_add and compare_exchange but now I'm not even sure if it's possible with the right orderings or if I should just do the simple thing and wrap it in a mutex ...

    play.rust-lang.org/?version=st

    #rust #atomics

  11. Edit: solved, thanks Paul!

    Any bored #RustLang atomics enthusiast around? I'm trying to write a kind of global unique id allocator using fetch_add and compare_exchange but now I'm not even sure if it's possible with the right orderings or if I should just do the simple thing and wrap it in a mutex ...

    play.rust-lang.org/?version=st

    #rust #atomics

  12. 🤓 Ah yes, the brave soul who attempts to explain 'Atomics and Concurrency' while sounding like they're deciphering the Rosetta Stone of tech. 📜 Don’t worry, just enable the ⚠️ #TSan flag and enjoy the thrilling life of a data race spectator! 🎢
    redixhumayun.github.io/systems #Atomics #Concurrency #DataRace #TechHumor #HackerNews #ngated

  13. 🤓 Ah yes, the brave soul who attempts to explain 'Atomics and Concurrency' while sounding like they're deciphering the Rosetta Stone of tech. 📜 Don’t worry, just enable the ⚠️ #TSan flag and enjoy the thrilling life of a data race spectator! 🎢
    redixhumayun.github.io/systems #Atomics #Concurrency #DataRace #TechHumor #HackerNews #ngated

  14. 🤓 Ah yes, the brave soul who attempts to explain 'Atomics and Concurrency' while sounding like they're deciphering the Rosetta Stone of tech. 📜 Don’t worry, just enable the ⚠️ #TSan flag and enjoy the thrilling life of a data race spectator! 🎢
    redixhumayun.github.io/systems #Atomics #Concurrency #DataRace #TechHumor #HackerNews #ngated

  15. 🤓 Ah yes, the brave soul who attempts to explain 'Atomics and Concurrency' while sounding like they're deciphering the Rosetta Stone of tech. 📜 Don’t worry, just enable the ⚠️ #TSan flag and enjoy the thrilling life of a data race spectator! 🎢
    redixhumayun.github.io/systems #Atomics #Concurrency #DataRace #TechHumor #HackerNews #ngated

  16. Programming Ada: Atomics and Other Low-Level Details - Especially within the world of multi-threaded programming does atomic access becom... - hackaday.com/2025/01/02/progra #softwaredevelopment #hackadaycolumns #atomics #ada

  17. Programming Ada: Atomics and Other Low-Level Details - Especially within the world of multi-threaded programming does atomic access becom... - hackaday.com/2025/01/02/progra #softwaredevelopment #hackadaycolumns #atomics #ada

  18. Programming Ada: Atomics and Other Low-Level Details - Especially within the world of multi-threaded programming does atomic access becom... - hackaday.com/2025/01/02/progra #softwaredevelopment #hackadaycolumns #atomics #ada

  19. Programming Ada: Atomics and Other Low-Level Details - Especially within the world of multi-threaded programming does atomic access becom... - hackaday.com/2025/01/02/progra #softwaredevelopment #hackadaycolumns #atomics #ada

  20. Programming Ada: Atomics and Other Low-Level Details - Especially within the world of multi-threaded programming does atomic access becom... - hackaday.com/2025/01/02/progra #softwaredevelopment #hackadaycolumns #atomics #ada

  21. 🚀 Excited to announce @tlhunter & @bengl as #NodeConfEU speakers! They'll dive into Node.js multithreading with Atomics, Workers & SharedArrayBuffers. Are the trade-offs worth it? Find out! 📊
    Get tickets: ti.to/nearform/nodeconf-eu-24 #JavaScript #NodeJS #atomics #waterfordcastle

  22. 🚀 Excited to announce @tlhunter & @bengl as #NodeConfEU speakers! They'll dive into Node.js multithreading with Atomics, Workers & SharedArrayBuffers. Are the trade-offs worth it? Find out! 📊
    Get tickets: ti.to/nearform/nodeconf-eu-24 #JavaScript #NodeJS #atomics #waterfordcastle

  23. 🚀 Excited to announce @tlhunter & @bengl as #NodeConfEU speakers! They'll dive into Node.js multithreading with Atomics, Workers & SharedArrayBuffers. Are the trade-offs worth it? Find out! 📊
    Get tickets: ti.to/nearform/nodeconf-eu-24 #JavaScript #NodeJS #atomics #waterfordcastle

  24. 🚀 Excited to announce @tlhunter & @bengl as #NodeConfEU speakers! They'll dive into Node.js multithreading with Atomics, Workers & SharedArrayBuffers. Are the trade-offs worth it? Find out! 📊
    Get tickets: ti.to/nearform/nodeconf-eu-24 #JavaScript #NodeJS #atomics #waterfordcastle

  25. 🚀 Excited to announce @tlhunter & @bengl as #NodeConfEU speakers! They'll dive into Node.js multithreading with Atomics, Workers & SharedArrayBuffers. Are the trade-offs worth it? Find out! 📊
    Get tickets: ti.to/nearform/nodeconf-eu-24 #JavaScript #NodeJS #atomics #waterfordcastle

  26. did something change about += becoming more threadsafe between Python 3.7 and Python 3.10? I have some vague memory that it did but can't find any documentation, and running a few test programs seems to suggest so?

    #Python #Threads #Atomics

  27. did something change about += becoming more threadsafe between Python 3.7 and Python 3.10? I have some vague memory that it did but can't find any documentation, and running a few test programs seems to suggest so?

    #Python #Threads #Atomics

  28. did something change about += becoming more threadsafe between Python 3.7 and Python 3.10? I have some vague memory that it did but can't find any documentation, and running a few test programs seems to suggest so?

    #Python #Threads #Atomics

  29. did something change about += becoming more threadsafe between Python 3.7 and Python 3.10? I have some vague memory that it did but can't find any documentation, and running a few test programs seems to suggest so?

    #Python #Threads #Atomics

  30. did something change about += becoming more threadsafe between Python 3.7 and Python 3.10? I have some vague memory that it did but can't find any documentation, and running a few test programs seems to suggest so?

    #Python #Threads #Atomics

  31. I wrote a few words about what I learned about Atomics in Rust after reading the book "Rust Atomics and Locks" by @Mara

    You should definitely buy that book! It's very approachable and well written.

    In the meantime here's my little blog post zkc.se/blog/rust-atomics-and-l

    Please let me know if there are any inaccuracies 🤗 My biggest fear is that I've contributed to confusion or misrepresented the source material.

    #rustlang #programming #atomics #rust

  32. I wrote a few words about what I learned about Atomics in Rust after reading the book "Rust Atomics and Locks" by @Mara

    You should definitely buy that book! It's very approachable and well written.

    In the meantime here's my little blog post zkc.se/blog/rust-atomics-and-l

    It has a little guest spot filled by @jonasdn

    Please let me know if there are any inaccuracies 🤗 My biggest fear is that I've contributed to confusion or misrepresented the source material.

    #rustlang #programming #atomics #rust

  33. I wrote a few words about what I learned about Atomics in Rust after reading the book "Rust Atomics and Locks" by @Mara

    You should definitely buy that book! It's very approachable and well written.

    In the meantime here's my little blog post zkc.se/blog/rust-atomics-and-l

    It has a little guest spot filled by @jonasdn

    Please let me know if there are any inaccuracies 🤗 My biggest fear is that I've contributed to confusion or misrepresented the source material.

    #rustlang #programming #atomics #rust

  34. I wrote a few words about what I learned about Atomics in Rust after reading the book "Rust Atomics and Locks" by @Mara

    You should definitely buy that book! It's very approachable and well written.

    In the meantime here's my little blog post zkc.se/blog/rust-atomics-and-l

    It has a little guest spot filled by @jonasdn

    Please let me know if there are any inaccuracies 🤗 My biggest fear is that I've contributed to confusion or misrepresented the source material.

    #rustlang #programming #atomics #rust

  35. I’m not quite getting the idea of #SeqCst ordering, can someone explain it to me in less #rust specific terms? How do the CPUs know to group the pairs?

    #multithreading #atomics

  36. I’m not quite getting the idea of #SeqCst ordering, can someone explain it to me in less #rust specific terms? How do the CPUs know to group the pairs?

    #multithreading #atomics

  37. I’m not quite getting the idea of #SeqCst ordering, can someone explain it to me in less #rust specific terms? How do the CPUs know to group the pairs?

    #multithreading #atomics

  38. I’m not quite getting the idea of #SeqCst ordering, can someone explain it to me in less #rust specific terms? How do the CPUs know to group the pairs?

    #multithreading #atomics