Programming with POSIX threads

What Hacker News says

1. rramadassNov 2023
   Sure. IMO it is important to have an overall picture of the fields of Concurrent/Parallel/Distributed architecture/programming before delving into the details of a language/library implementation. To that end i have found the following books useful;

   1) Foundations of Multithreaded, Parallel, and Distributed Programming by Gregory R. Andrews - This is one of my favourites even though old. You get to learn/compare the different paradigms in one single book.

   2) Parallel Programming: Concepts and Practice by Bertil Schmidt et al. - This is a more recent book with good explanations/coverage including CUDA.

   3) The Art of Multiprocessor Programming by Maurice Herlihy et al. - Well known classic though with a main focus on shared-memory architectures.

   Along with the above you also need more detailed language/library specific implementation books;

   a) C++ Concurrency in Action by Anthony Williams.

   b) Programming with POSIX Threads by David Butenhof.

   c) UNIX Systems Programming: Communication, Concurrency and Threads by Kay Robbins and Steve Robbins.

   Finally; for studying concurrency at the OS level where software meets hardware, i have found nothing better than;

   i) Unix Systems for Modern Architectures: Symmetric Multiprocessing and Caching for Kernel Programmers by Curt Schimmel.

   Show morethread
2. senderistaFeb 2021
   Ditto, via David Butenhof's excellent book _Programming with Posix Threads_. I didn't know what a mutex or condition variable was before I read that book.
   thread
3. planteenJan 2017
   Some books will remain relevant. A quick glance at my bookshelf of old but relevant books: K&R The C Programming Language, Programming with POSIX Threads (it's from the 90s but pthreads really hasn't changed), Algorithms, and Expert C Programming.
   thread
4. adolgertNov 2010
   K&R's _C Programming Language_, because my father saw me start to write Schrodinger's equation in BASIC and said I should take a look.

   Stroustrup's _The C++ Programming Language_, twice in a row, because I didn't want to be left out for not having taken Computer Science.

   Butelhof's _Programming with Posix Threads_, because another book referenced its explanation of why Win32 threading had a bug because it could not, at the time, signal and wait on a mutex in an atomic way. There was something deep to find in those rowboats and bucket stories.

   GoF's _Design Patterns: Elements of Reusable Object-Oriented Software_, because when I complained to a mentor that I was struggling to organize a dozen scientist programmers, he handed it to me, laughing.

   John Robbins, _Debugging Applications_, first edition, because it was the first time for me that code didn't have the disclaimer, "of course you should insert error-handling code here." Basic x86 assembly in one chapter!

   Show morethread
5. bosch_mindFeb 2023
   Most books like k&r, programming with posix threads, Beej confirm this with C.
   thread