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

<!-- filename to begin with "RX900S2_Platform.xml" -->
<filename>RX900S2_Platform.xml</filename>

<title>RX900S2 Platform Flag file </title>


<platform_settings>
 <![CDATA[ 

	 <p><b>echo 1 > /proc/sys/vm/zone_reclaim_modee</b></p>

	<p>Zone_reclaim_mode allows someone to set more or less aggressive approaches to
	reclaim memory when a zone runs out of memory. If it is set to zero then no
	zone reclaim occurs. Allocations will be satisfied from other zones / nodes
	in the system.</p>
	
	<p>This is value ORed together of</p>
	
	<p>1       = Zone reclaim on<br />
	2       = Zone reclaim writes dirty pages out<br />
	4       = Zone reclaim swaps pages<br /></p>
	
	<p>zone_reclaim_mode is set during bootup to 1 if it is determined that pages
	from remote zones will cause a measurable performance reduction. The
	page allocator will then reclaim easily reusable pages (those page
	cache pages that are currently not used) before allocating off node pages.</p>
	
	<p>It may be beneficial to switch off zone reclaim if the system is
	used for a file server and all of memory should be used for caching files
	from disk. In that case the caching effect is more important than
	data locality.</p>

	<p>Allowing zone reclaim to write out pages stops processes that are
	writing large amounts of data from dirtying pages on other nodes. Zone
	reclaim will write out dirty pages if a zone fills up and so effectively
	throttle the process. This may decrease the performance of a single process
	since it cannot use all of system memory to buffer the outgoing writes
	anymore but it preserve the memory on other nodes so that the performance
	of other processes running on other nodes will not be affected.</p>

	<p>Allowing regular swap effectively restricts allocations to the local
	node unless explicitly overridden by memory policies or cpuset
	configurations.</p>


  ]]> 
</platform_settings>


</flagsdescription>

