java.jsr.166-concurrency (thread)

Summer School on Concurrency, jv
how expensive contextswitch blocked thread., Peter Veentjer
- Re: how expensive contextswitch blocked thread., Brian Goetz
- Re: how expensive contextswitch blocked thread., Greg Gagne
best way to figure out how long lock acquisition took., Peter Veentjer
- Re: best way to figure out how long lock acquisition took., Tim Peierls
backport issue: second opinion needed, Dawid Kurzyniec
- backport issue: second opinion needed (cont.), Dawid Kurzyniec
- RE: backport issue: second opinion needed, David Holmes
  - Re: backport issue: second opinion needed, Dawid Kurzyniec
    - RE: backport issue: second opinion needed, David Holmes
    - Re: backport issue: second opinion needed, Dawid Kurzyniec
Then the Whos down in Whoville..., Craig Mattocks
- Re: Then the Whos down in Whoville..., Brian Goetz
  - Then the Whos down in Whoville..., Ian Griffiths
Volatile Creature, Hanson Char
- Re: Volatile Creature, Jeremy Manson
  - Re: Volatile Creature, Hanson Char
- Re: Volatile Creature, Tim Peierls
BACKPORT - Deadlocks and FixedThreadPool executors..., Mark Derricutt
- Re: BACKPORT - Deadlocks and FixedThreadPool executors..., Gregg Wonderly
- Re: BACKPORT - Deadlocks and FixedThreadPoolexecutors..., Dawid Kurzyniec
Future cancel(true) vs. channels/streams, Andrew Lentvorski
- Re: Future cancel(true) vs. channels/streams, Dawid Kurzyniec
navigating enums, Kevin Bourrillion
- Re: navigating enums, Joshua Bloch
  - Re: navigating enums, Rémi Forax
    - RE: navigating enums, Mike Skells
Confusing API: ScheduledThreadPoolExecutor vs. remove(), Holger Hoffstätte
- Re: Confusing API: ScheduledThreadPoolExecutor vs. remove(), Tim Peierls
  - Re: Confusing API: ScheduledThreadPoolExecutor vs. remove(), Holger Hoffstätte
    - Re: Confusing API: ScheduledThreadPoolExecutor vs. remove(), Tim Peierls
    - Re: Confusing API: ScheduledThreadPoolExecutor vs. remove(), Holger Hoffstätte
    - Re: Confusing API: ScheduledThreadPoolExecutor vs. remove(), Tim Peierls
    - Re: Confusing API: ScheduledThreadPoolExecutor vs. remove(), Holger Hoffstätte
    - Re: Confusing API: ScheduledThreadPoolExecutorvs.remove(), Dawid Kurzyniec
    - Re: Confusing API: ScheduledThreadPoolExecutor vs. remove(), Tim Peierls
    - Re: Confusing API: ScheduledThreadPoolExecutor vs. remove(), Doug Lea
new threading structure., Peter Veentjer - Anchor Men
- RE: new threading structure., Peter Veentjer - Anchor Men
SetFromMap and AsLIFOQueue micro suggestions, Jason Mehrens
Timeouts and Executors..., Travis Tabbal
- Re: Timeouts and Executors..., Holger Hoffstätte
- RE: Timeouts and Executors..., Peter Veentjer - Anchor Men
- RE: Timeouts and Executors..., Peter Veentjer - Anchor Men
toc : Java Concurrency in Practice?, Peter Veentjer - Anchor Men
- Re: toc : Java Concurrency in Practice?, Brian Goetz
- RE: toc : Java Concurrency in Practice?, Peter Veentjer - Anchor Men
Question about ThreadPoolExecutor.execute implementation, Peter Veentjer - Anchor Men
- Re: Question about ThreadPoolExecutor.execute implementation, Moran Avigdor
- RE: Question about ThreadPoolExecutor.execute implementation, Peter Veentjer - Anchor Men
Re: backport: AtomicLongFieldUpdater support, Moran Or Avigdor
- Re: backport: AtomicLongFieldUpdater support, Dawid Kurzyniec
  - Re: backport: AtomicLongFieldUpdater support, Moran Or Avigdor
    - Re: backport: AtomicLongFieldUpdater support, Dawid Kurzyniec
    - Re: backport: AtomicLongFieldUpdater support, Moran Avigdor
re: documentation on nested transactions (DSTM Java code), Mark Moir
runtime performance statistics in java.util.concurrent, peterspaz
documentation on nested transactions (DSTM Java code), Kenworthy, John C
J2SE 5.0 Update 6 is Released, Martin Buchholz
Why can signals only be sent from within locks?, Tezhe Moolenschot
- Re: Why can signals only be sent from within locks?, Brian Goetz
- Re: Why can signals only be sent from within locks?, David Holmes
RE: when to use lock and when to uselockInterruptibly, Peter Veentjer - Anchor Men
- Re: when to use lock and when touselockInterruptibly, Dawid Kurzyniec
- RE: when to use lock and when touselockInterruptibly, David Holmes
  - Re: when to use lock and whentouselockInterruptibly, Dawid Kurzyniec