Rust Atomics and Locks by Mara Bos

cross-posted from: https://discuss.online/post/5803977

About this Book

The Rust programming language is extremely well suited for concurrency, and its ecosystem has many libraries that include lots of concurrent data structures, locks, and more. But implementing those structures correctly can be difficult. Even in the most well-used libraries, memory ordering bugs are not uncommon.

In this practical book, Mara Bos, team lead of the Rust library team, helps Rust programmers of all levels gain a clear understanding of low-level concurrency. You’ll learn everything about atomics and memory ordering and how they’re combined with basic operating system APIs to build common primitives like mutexes and condition variables. Once you’re done, you’ll have a firm grasp of how Rust’s memory model, the processor, and the role of the operating system all fit together.

With this guide, you’ll learn:

How Rust’s type system works exceptionally well for programming concurrency correctly

All about mutexes, condition variables, atomics, and memory ordering

What happens in practice with atomic operations on Intel and ARM processors

How locks are implemented with support from the operating system

How to write correct code that includes concurrency, atomics, and locks

How to build your own locking and synchronization primitives correctly

Available free of charge. But I doubt I’ll ever read it. Never enough time and energy for everything.

Welcome

A collaborative space for people to work together on learning Rust, learning about the Lemmy code base, discussing whatever confusions or difficulties we’re having in these endeavours, and solving problems, including, hopefully, some contributions back to the Lemmy code base.

Rules TL;DR: Be nice, constructive, and focus on learning and working together on understanding Rust and Lemmy.

Policies and Purposes

This is a place to learn and work together.

Questions and curiosity is welcome and encouraged.

This isn’t a technical support community. Those with technical knowledge and experienced aren’t obliged to help, though such is very welcome. This is closer to a library of study groups than stackoverflow. Though, forming a repository of useful information would be a good side effect.

This isn’t an issue tracker for Lemmy (or Rust) or a place for suggestions. Instead, it’s where the nature of an issue, what possible solutions might exist and how they could be or were implemented can be discussed, or, where the means by which a particular suggestion could be implemented is discussed.