<?xml version="1.0"?>
<!DOCTYPE flagsdescription SYSTEM "http://www.spec.org/dtd/cpuflags2.dtd">

<flagsdescription>

<filename>IBM-Platform-Flags-V1.2-WSM-C.xml</filename>

<title>SPEC CPU2006 Platform Settings for IBM Systems</title>

<os_tuning>
<![CDATA[
<dl>

 <dt><b>Zone Reclaim:</b></dt>
 <dd>
  Zone reclaim allows the reclaiming of pages from a zone if the number of free pages 
  falls below a watermark even if other zones still have enough pages available. 
  Reclaiming a page can be more beneficial than taking the performance penalties that 
  are associated with allocating a page on a remote zone, especially for NUMA machines. 
 </dd> 
       
</dl>
]]>
</os_tuning>

<firmware>
<![CDATA[ 
<dl>

 <dt><b>Operating Modes (Default=Custom Mode):</b></dt>
 <dd>
  Operating Mode is a BIOS setting which allows you to select the appropriate mode of operation based on
  the specific user environment. This menu option is provided to allow optimization of the system for 
  minimum power usage, maximum efficiency, or maximum performance.
	
 <ul>
  <li><b>Acoustic/minimum power mode</b>: Strives to minimize the absolute power consumption of the system while it is operating.
  </li> 
  <li><b>Efficiency mode</b>: Maximizes the performance/watt efficiency as measured by power benchmarks. It provides
         the best features for reducing power and increasing performance without a detrimental effect on either one.
  </li> 
  <li><b>Performance mode</b>: Maximizes the absolute performance of the system by setting all programmable bus speeds to their 
         maximum rated frequencies without regard for power.
  </li> 
  <li><b>Custom mode</b>: A combination of Efficiency mode and Performance mode.
  </li> 
 </ul>
 </dd> 

 <dt><b>Turbo Boost:</b></dt> 
 <dd> This BIOS option can be set to Power Optimized or Traditional. When Power 
 Optimized is selected, Intel Turbo Boost Technology engages after Performance state 
 P0 is sustained for longer than two seconds. When Traditional is selected, Intel 
 Turbo Boost Technology is engaged even for P0 requests less than two seconds. </dd> 

</dl>
]]> 
</firmware>

</flagsdescription>