Comments on: Parallel Programming News for Week 29/2007

By: Michael Suess

Michael Suess — Wed, 25 Jul 2007 15:22:45 +0000

@bing: thanks for the link, I will check it out soon.

@ARI: no, I have not played with Terracotta, as my playtime is seriously limited at the moment. I have at least 10 systems that I would like to play with (including Erlang, Intels TBB and others), but unfortunately, nobody pays me to do these things and I have many other things to do in my (few and precious) spare time…

By: bing

bing — Mon, 23 Jul 2007 18:38:49 +0000

A good explanation of Java memory model (and memory models in general) : http://java.sun.com/docs/books/jls/download/langspec-3.0.pdf
Chapter 17 (section 2)

By: ARI ZILKA

ARI ZILKA — Mon, 23 Jul 2007 09:11:38 +0000

Michael,

Have you played with Terracotta for thread-level coordination across JVMs using pure Java constructs like wait() / notify(), etc. java.util.concurrent (or OSWEGO) work on top of the stuff. Take a look. tell me what you think.

I will definitely keep an eye out for your ideas on this blog. Concurrency is VERY important, IMHO.

–Ari

By: Michael Suess

Michael Suess — Sat, 21 Jul 2007 19:38:32 +0000

Saurabh: I am afraid I need more than a couple of lines in a comment for that. But I have already started an article on memory models and will post it in a not so distant future (notice how I avoided any specific timeframe - this stuff is complicated, even more since every parallel programming system has a different memory model)…

By: Wes Felter

Wes Felter — Thu, 19 Jul 2007 22:14:23 +0000

Stanford just released the Sequoia compiler.

By: Saurabh

Saurabh — Thu, 19 Jul 2007 17:37:42 +0000

Could you elaborate about memory model and memory barriers (re the spin buffer article)? I admit that the DDJ article example is a very special-scenario one (only two threads, one must remain consumer all the time, the other must remain producer all the time), but didnt see anything wrong with it per se. Thanks.