3 ms·
Concurrency does not necessary mean parallelism; you can have have threads interacting in a time-shared manner on the same processor. Parallelism implies concu
by scott_s 16y ago
Concurrency does not necessary mean parallelism; you can have have threads interacting in a time-shared manner on the same processor.
Parallelism implies concurrency; a parallel program has threads of execution (which may not actually be shared-memory software threads) that are executing simultaneously.
The author's definition of parallelism is wrong - at least, it's different from the one myself and everyone else I know in the high performance computing and systems research community use. Many interesting problems are not embarrassingly parallel, and figuring out how, exactly, such problems can be solved efficiently in parallel is hard. (And efficiency is a solution requirement, since it's not worth the parallelization effort if you don't achieve it.)
I think the point the author is trying to arrive at is parallelism does not necessarily mean shared-state across threads. Which is true, and I share his sentiment that we should probably not reach for shared-state threads to solve our parallel problems.