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

<flagsdescription>

<filename>xFusion-Platform-Settings-GNR-V1.0</filename>

<title>SPEC CPU2017 software OS and BIOS Settings Descriptions for xFusion Platform systems</title>

<os_tuning>
  <![CDATA[ 

    <dl>

	<dt><b>cpupower frequency-set</b></dt>
	<dd>
	cpupower utility is a collection of tools for power efficiency of processor.
	frequency-set sub-command controls settings for processor frequency.
	"-g [governor]" specifies a policy to select processor frequency.
	The performance governor statically sets frequency of the processor cores specified
	by "-c" option to the highest possible for maximum performance.
	</dd>

	<dt><b>cpupower idle-set</b></dt>
	<dd>
	idle-set sub-command of cpupower utility controls a processor idle state (C-state) of
	the kernel.  "-d [state_no]>" option disables a specific processor idle state.
	Disabling idle state can reduce the idle-wakeup delay, but it results in substantially
	higher power consumption.  By default, processor idle states of all CPU cores are set.
	</dd>

	<dt><b>irqbalance</b></dt>
        <dd>
        Disabled through "service irqbalance stop". Depending on the workload involved, the
        irqbalance service reassigns various IRQ's to system CPUs. Though this service might help
        in some situations, disabling it can also help environments which need to minimize or
        eliminate latency to more quickly respond to events.
        </dd>

	<dt><b>isolcpus</b></dt> 
	<dd>
	This kernel option excludes a specified processor from load balancing by the kernel
	scheduler.  This prevents the scheduler from scheduling any user-space threads on
	this processor. 
	</dd>

	<dt><b>nohz_full</b></dt> 
	<dd>
	This kernel option sets adaptive tick mode (NOHZ_FULL) to specified processors.
	Since the number of interrupts is reduced to ones per second, latency-sensitive
	applications can take advantage of it.
	</dd>

	<dt><b>numa_balancing</b></dt> 
	<dd>
	This OS setting controls automatic NUMA balancing on memory mapping and process placement.
	Setting 0 disables this feature.  It is enabled by default (1).
	</dd>

	<dt><b>sched_latency_ns</b></dt> 
	<dd>
	This OS setting configures targeted preemption latency for CPU bound tasks. 
 	The default value is 24000000 (ns).
	</dd>

	<dt><b>sched_migration_cost_ns</b></dt> 
	<dd>
	Amount of time after the last execution that a task is considered to be "cache hot" 
 	in migration decisions. A "hot" task is less likely to be migrated to another CPU, 
	so increasing this variable reduces task migrations. The default value is 500000 (ns).
	</dd>

	<dt><b>sched_min_granularity_ns</b></dt> 
	<dd>
	This OS setting controls the minimal preemption granularity for CPU bound tasks.
	As the number of runnable tasks increases, CFS(Complete Fair Scheduler), the scheduler
	of the Linux kernel, decreases the timeslices of tasks. If the number of runnable
	tasks exceeds sched_latency_ns/sched_min_granularity_ns, the timeslice becomes
	number_of_running_tasks * sched_min_granularity_ns.  The default value is 10000000(ns). 
	</dd>

	<dt><b>sched_wakeup_granularity_ns</b></dt> 
	<dd>
	This OS setting controls the wake-up preemption granularity. Increasing this variable
	reduces wake-up preemption, reducing disturbance of compute bound tasks.
	Lowering it improves wake-up latency and throughput for latency critical tasks,
	particularly when a short duty cycle load component must compete with CPU bound components. 
	The default value is 15000000 (ns). 
	</dd>

    </dl>	
 
  ]]> 
</os_tuning>

<firmware>
<![CDATA[

<dl>
<dt><b>Hardware Prefetcher (Default = Enabled)</b></dt> 
        <dd>
         <p>This BIOS option allows the enabling/disabling of a processor mechanism 
         to prefetch data into the cache according to a pattern-recognition algorithm
         In some cases, setting this option to Disabled may improve performance. 
         Users should only disable this option after performing application benchmarking 
         to verify improved performance in their environment.
         </p>
         </dd>

<dt><b>Turbo Mode (Default = Enabled)</b></dt> 
	 <dd>
	 <p>Intel Turbo boost Technology, Enabling this option allows the processor cores to automatically increase its frequency and increasing 
       performance if it is running below power, temperature.
       </p>
       </dd>       
	 
<dt><b>Enable LP [Global] (Default = Enabled)</b></dt> 
	 <dd>
	 <p>The Intel Hyper-Threading knob has been renamed Enable LP [Global] to represent the number of logical processors (LP). 
	    Enabling this option allows to use processor resources more efficiently, enabling multiple threads to run 
        on each core and increases processor throughput, improving overall performance on threaded software.	   
       </p>
	 <p> ALL LPs: Hyper-Threading is enabled, each physical processor core functions as two logical processor cores.</p>
	 <p> Single LP: Run a single logical processor per core.</p>
       </dd>
                       
<dt><b>Performance Profile (Default = Custom)</b></dt>
         <dd>
         <p>Values for this BIOS setting can be:</p>
         <p> Custom: Allows the user to setup all of the BIOS options according to their requirement.</p>
	 <p> Performance: Maximize the performance of the server.</p>
	 <p> Efficiency: Maximize the power efficiency of the server.</p>
	 <p> Load Balance: The system's performance and power consumption will be adjusted automatically according to the loading. </p>
	 </dd>

<dt><b>CPU C6 Report (Default = Disabled)</b></dt>
      <dd>
        <p>Enable or disable reporting of the CPU C6 State (ACPI C3) to the OS. </p>
      </dd>

<dt><b>Enhanced Halt State (C1E) (Default = Disabled)</b></dt>
      <dd>
        <p>When set to Enabled, the processor is allowed to switch to nimimum performance and save power when idle. </p>
      </dd>  
  
<dt><b>Sub NUMA Cluster（SNC）(Default = Disabled)</b></dt>
      <dd>
	    <p>Sub NUMA Clustering (SNC) is a feature for breaking up the LLC into disjoint clusters based on address range,with each cluster bound to a subset of the memory controllers in the system.It improves average latency to the LLC.</p>
	    <p>  Values for this BIOS option can be: </p>
		<p>  Enabled: "Enabled" means to Enable SNC mode.</p>
	    <p>  Disabled: "Disabled" means to Disable SNC mode. SNC disabled will support 1-cluster.</p>		
		<p>  SNC2: supports 2-way clustering. Utilizes LLC capacity efficiently and reduces latency due to core/IMC proximity. This may provide performance improvement on NUMA-aware operating systems. </p>
		<p>  SNC3: supports 3-way clustering. Utilizes LLC capacity efficiently and reduces latency due to core/IMC proximity. This may provide performance improvement on NUMA-aware operating systems. </p>
		<p>  SNC4: supports 4-way clustering. Utilizes LLC capacity more efficiently and reduces latency due to core/IMC proximity. This may provide performance improvement on NUMA-aware operating systems. </p>		
	  </dd> 				
  
<dt><b>Last Level Cache (LLC) Prefetch (Default = Enabled)</b></dt> 
	   <dd>
	    <p>The last level cache (LLC) prefetch is a prefetcher added to the Intel Xeon Scalable processor family as a result of the non-inclusive cache architecture.
           The LLC prefetcher is an additional prefetch mechanism on top of the existing prefetchers that prefetch data into the core Data Cache Unit (DCU) and Mid-Level Cache (MLC or second-level cache (L2)). 
           Enabling LLC prefetch gives the core prefetcher the ability to prefetch data directly into the LLC without necessarily filling into the L1 and L2 cache. 
           In some cases, setting this option to disabled can improve performance.  </p>
	    <p>  Values for this BIOS option can be: </p>		
		<p>  Disabled: Disables the LLC prefetcher. The other core prefetchers are unaffected. </p>
		<p>  Enabled: Gives the core prefetcher the ability to prefetch data directly to the LLC. </p>
	  </dd> 
 
<dt><b>Adaptive Double Device Data Correction (ADDDC) Sparing (Default = Enabled)</b></dt> 
	   <dd>
	    <p>Adaptive Double Device Data Correction (ADDDC), which is an enhanced feature to DDDC. This function is used to correct data errors on two memory particles, ADDDC still has single-particle multi-bit error correction capability after the first particle failure occurs and is replaced.</p>
        <p>Values for this BIOS option can be: </p>
        <p>Enabled: Enable the ADDDC Sparing function.</p>
        <p>Disabled: Disable the ADDDC Sparing function.</p>	
	  </dd> 		

<dt><b>LLC dead line alloc (Default = Enabled)</b></dt>
           <dd>
            <p>LLC dead line allocation. The processor marks the row replaced by the MLC as dead, indicating that the row will not be read again. This function is used to set the allocation policy for the data marked as dead in the LLC. </p>
        <p>Values for this BIOS option can be: </p>
        <p>Enabled: Allows the LLC to fill dead lines into the LLC if there is free space.</p>
        <p>Disabled: The dead lines are dropped and are never filled into the LLC, saving the LLC space.</p>
          </dd>

<dt><b>Stale AtoS (Default = Auto)</b></dt>
           <dd>
            <p>The in-memory directory has three states: invalid (I), snoopAll (A), and shared (S). Invalid (I) state means the data is clean and does not exist in any other socket`s cache. The snoopAll (A) state means the data may exist in another socket in exclusive or modified state. Shared (S) state means the data is clean and may be shared across one or more socket`s caches. When doing a read to memory, if the directory line is in the A state we must snoop all the other sockets because another socket may have the line in modified state. If this is the case, the snoop will return the modified data. However, it may be the case that a line is read in A state and all the snoops come back a miss. This can happen if another socket read the line earlier and then silently dropped it from its cache without modifying it.</p>
        <p>Values for this BIOS option can be: </p>
        <p>Auto: The SnoopAll (A) state is used by default. During uncore post MRC, the state is reconfigured based on the setup knob, number of sockets, and BPS memory.</p>
        <p>Enabled: The SnoopAll (A) state is changed to the Shared (S) state.</p>
        <p>Disabled: The SnoopAll (A) state is used.</p>
          </dd>
          	 	 
</dl>

]]>
</firmware>
     
         
</flagsdescription>
