Rust atomics and locks : low-level concurrency in practice / Mara Bos.
Material type:
- text
- unmediated
- volume
- 9781098119447 (paperback)
- QA76.73.R87 BOS

Item type | Current library | Collection | Call number | Copy number | Status | Date due | Barcode | |
---|---|---|---|---|---|---|---|---|
![]() |
GSU Library Epoch General Stacks | NFIC | QA76.73.R87 BOS (Browse shelf(Opens below)) | 1 | Available | 50000006121 |
Browsing GSU Library Epoch shelves, Shelving location: General Stacks Close shelf browser (Hides shelf browser)
Includes index.
1. Basics of Rust Concurrency -- 2. Atomics -- 3. Memory Ordering -- 4. Building Our Own Spin Lock -- 5. Building Our Own Channels -- 6. Building Our Own "Arc" -- 7. Understanding the Processor -- 8. Operating System Primitives -- 9. Building Our Own Locks -- 10. Ideas and Inspiration.
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 very difficult. Even in the most well-used libraries, memory ordering bugs are not uncommon. In this practical book, Mara Bos, leader 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.
There are no comments on this title.