Path: ...!weretis.net!feeder9.news.weretis.net!news.quux.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: comp.arch Subject: Re: Is Parallel Programming Hard, And, If So, What Can You Do About It? Date: Tue, 20 May 2025 16:06:13 -0400 Organization: A noiseless patient Spider Lines: 10 Message-ID: References: <27492f8028a0d40eff5071e85214fc36@www.novabbs.com> <100gj7t$1sbnn$11@dont-email.me> <100iher$2b7vi$2@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain Injection-Date: Tue, 20 May 2025 22:06:13 +0200 (CEST) Injection-Info: dont-email.me; posting-host="4b6cf13ad1bb0241891e30045998d363"; logging-data="2527864"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19D5Xqh/Hfod6/oBSxfCr67d2VUWzW2fNM=" User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:3G/WnO/LysPlcXHy5U29Um3zFq4= sha1:ti/xGJ4YuDd2aQxEOk75Kzey5/Q= Bytes: 1570 > Personally, I rarely use multi-threading, and when I do, it is usually in > the form of using mutex locks over shared buffers. > You lock the mutex if needed to copy data from one thread to another; or > when doing a task that depends on the data being consistent. FWIW, I think these kinds of things usually fall in the scope of concurrency rather than parallelism. Stefan