Review + pull request: update FJP

Aleksey Shipilev aleksey.shipilev at
Tue Oct 30 04:44:11 PDT 2012

Sure, but I think lambda/lambda is already ahead, and for a reason:
performance investigations for lambdas require latest and greatest code.
In this particular case, this involves more changes in lambda code itself.

The jsr166 -> jdk8 -> lambda turnaround is longer than bearable for
active development.


On 10/30/2012 03:41 PM, David Holmes wrote:
> Aleksey,
> There are plans to sync up jdk8 with latest jsr166 changes. Once that
> happens they can appear in the lambda repos too.
> David
> On 30/10/2012 8:50 PM, Aleksey Shipilev wrote:
>> Hi,
>> Please consider pulling up the update for new ForkJoinPool from jsr166.
>> Doug had implemented a few features which are to provide much better
>> wakeup performance. (Brian, this is the same patch I've cc'ed you
>> before).
>> Here's the patch against JDK:
>> Testing:
>>   - custom builds on Linux x86_64;
>>   - decomposition performance benchmarks;
>>   - fjp-trace logs
>> I could generate the webrev, if that is more appropriate.
>> -Aleksey

More information about the lambda-dev mailing list