Large Page allocation strategy only for 2003?

[Azeem Jiva]

Yeah the UseLargePagesIndividualAllocation was meant as a fix for 
Windows2003 where pages would migrate if you allocated the whole area.  
This was fixed in subsequent Windows versions, but the workaround 
remains in the JVM.


On 10/02/2012 01:10 AM, Jon Masamitsu wrote:
>
>
> On 10/1/2012 5:03 PM, Bernd Eckenfels wrote:
>> Hello,
>>
>> While investigating the risks of using/recommending large pages I 
>> noticed that there are two different allocations strategies. One 
>> requests the whole area (I guess thats part of the heap in NUMA?) 
>> with a single malloc or with multiple 
>> (+UseLargePagesIndividualAllocation). The option for this defaults to 
>> single on all platforms but Windows 2003.
>>
>> I wonder if this is really a 2003 thing only. or if the code should 
>> be updated to default to on on Win7,8,2008 and 2008R2 as well.
>
> I believe that it was a workaround for a problem on windows 2003.
> I don't recall anymore details.
>
> Jon
>
>>
>> I asume, that not the whole heap will be allocated in case of NUMA, 
>> right? Because otherwise I could see use for the 
>> IndividulaAllocations in that case as well, otherwise a single 
>> locality might get exhausted?
>>
>> Greetings
>> Bernd

-- 
Azeem Jiva
@javawithjiva