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

<!-- filename to begin with "Intel-Linux64-Platform" -->
<filename>Intel-Linux64-Platform.xml</filename>

<title>SPEC CPU2006 Flag Description for the Intel(R) C++ and Fortran Compiler 10.1
for IA32 and Intel 64 applications </title>
<header>
<![CDATA[
<p style="text-align: left; color: red; font-size: larger; background-color: black">
 Copyright &copy; 2006 Intel Corporation.  All Rights Reserved.</p>
]]>
</header>
<platform_settings>
 <![CDATA[ 
	 <p><b>Platform settings</b></p>

         <p>One or more of the following settings may have been set.  If so, the "General Notes" section of the
         report will say so; and you can read below to find out more about what these settings mean.</p>
   
         <p><b>KMP_STACKSIZE </b></p>
         <p>
         Specify stack size to be allocated for each thread. 
	 </p>

         <p><b>KMP_AFFINITY </b></p>
         <p>
         KMP_AFFINITY  =  &lt; physical | logical &gt;, starting-core-id <br/>
         specifies the static mapping of user threads to physical cores. For example, 
         if you have a system configured with 8 cores, OMP_NUM_THREADS=8 and 
         KMP_AFFINITY=physical,0 then thread 0 will mapped to core 0, thread 1 will be mapped to core 1, and 
         so on in a round-robin fashion.   
         </p>

         <p><b>OMP_NUM_THREADS </b></p>
         <p>
	  Sets the maximum number of threads to use for OpenMP* parallel regions if no 
          other value is specified in the application. This environment variable 
          applies to both -openmp and -parallel (Linux and Mac OS X) or /Qopenmp and /Qparallel (Windows).
          Example syntax on a Linux system with 8 cores:
          export OMP_NUM_THREADS=8
          /p>

	 <p><b>Hardware Prefetch:</b></p> 
	 <p>
	 This BIOS option allows the enabling/disabling of a processor mechanism to                 
	 prefetch data into the cache according to a pattern-recognition algorithm.
	 </p>
	 <p>                
	 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>

	 <p><b>Adjacent Sector Prefetch:</b></p> 
	 <p>
	 This BIOS option allows the enabling/disabling of a processor mechanism to                 
	 fetch the adjacent cache line within an 128-byte sector that contains 
	 the data needed due to a cache line miss.
	 </p>
	 <p>                
	 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>
         
	 <p><b>High Bandwidth:</b></p> 
	 <p>
	 Enabling this option allows the chipset to defer memory transactions and process them out of order for optimal performance. 
	 </p>


         <p><b>ulimit -s &lt;n&gt; </b></p>
	 <p>
         Sets the stack size to <b>n</b> kbytes, or <b>unlimited</b> to allow the stack size 
         to grow without limit.
         </p>
         
         <p><b>submit= MYMASK=`printf '0x%x' $((1&lt;&lt;$SPECCOPYNUM))`; /usr/bin/taskset $MYMASK $command </b></p>
	 <p>When running multiple copies of benchmarks, the SPEC config file feature 
	 <b>submit</b> is sometimes used to cause individual jobs to be bound to 
	 specific processors. This specific submit command is used for Linux. 
	 The description of the elements of the command are:</p>
	 <ul>
	 <li><b>/usr/bin/taskset [options] [mask] [pid | command [arg] ... ]</b>: <br/>
       	 taskset is used to set or retreive the CPU affinity of a running 
         process given its PID or to launch a new COMMAND with a given CPU 
         affinity. The CPU affinity is represented as a bitmask, with the 
         lowest order bit corresponding to the first logical CPU and highest
         order bit corresponding to the last logical CPU. When the taskset 
         returns, it is guaranteed that the given program has been scheduled
         to a legal CPU.<br/>
         The default behaviour of taskset is to run a new command with a 
         given affinity mask: <br/>
         taskset [mask] [command] [arguments]</li>
	 <li><b>$MYMASK</b>: The bitmask (in hexadecimal) corresponding to a specific
         SPECCOPYNUM. For example, $MYMASK value for the first copy of a 
         rate run will be 0x00000001, for the second copy of the rate will 
         be 0x00000002 etc. Thus, the first copy of the rate run will have a
         CPU affinity of CPU0, the second copy will have the affinity CPU1 
         etc.</li>
	 <li><b>$command</b>: Program to be started, in this case, the benchmark instance 
         to be started.</li>
	 </ul>

         <p><b>submit= $[top]/mysubmit.pl $SPECCOPYNUM "$command" </b></p>
         <p> On Xeon 74xx series processors, some benchmarks at peak will run n/2 copies on a system with n logical processors. 
         The mysubmit.pl script assigns each copy in such a way that no two copies will share an L2 cache, for optimal performance. 
         The script looks in /proc/cpuinfo to come up with the list of cores that will satisfy this requirement.  		 
         </p>

  ]]> 
  </platform_settings>

</flagsdescription>