Google Tech Talks
March 21, 2007
ABSTRACT
This talk describes the Java Memory Model and how it affects the ways concurrent software should be written. Recent changes to the memory model, which were incorporated into JDK 5, redefined the semantics of threads, synchronization, volatile variables, and final fields. The new memory model provides efficient and provably correct techniques for safely and correctly implementing concurrent operations. These techniques are compatible with existing good programming practice, although care needs to be taken in a couple of corner cases.
Most programmers can avoid depending on low-level details and instead just use the high-level concurrency abstractions...
Thank you for this video and I wish you health and wellness, as well as you can get discounts for organic products International DXN number : 1420-31106 or join my group
flany1960 2 months ago
Pretty useful!
lorrainegardella 2 months ago
@ae6rt - At 47:00 , I could not get the "/tmp/usr" substring attack. Even Java 1.4 String was final. ??
getalifein 4 months ago
interesting point about volatile increments at 38:50
ae6rt 7 months ago
@32:00 is something that happened to me :D
neeraj2608 9 months ago
not advanced...
callmewa1 1 year ago
First I thought he was wearing a white mask.
BringerOfTheTruth 1 year ago
nice once for a starter like me.....
KiranMuddukrishna 1 year ago
@abrocketsfan actually there was an ooo issue such that an instruction re-ordering commonly used in uni-processor compiler idoms that was used in contemporary multi-threading resulting in non-deterministic behaviour in jsr-166
this is said to be fixed, used synchronization primitives routinely as the supposed cost of syncronization is not apparent in most applications if non-blocking synchro is implemented such as to avoid locking on two mutual-exclusion constructs
pzmtuthcvpvl 1 year ago
are out of order operations allowed within a synchronized block?
abrocketsfan 3 years ago