anchor.diff:  To work around this problem, fork the repository, and override the `<version>` tag
   for the artifacts `jna` and `jna-platform` in the project's `pom` file.
   
  -### Installing JNA on Ubuntu
  +==== Installing JNA on Ubuntu
   
       sudo apt-get install libjna-java
   
  -### Installing JNA on CentOS
  +==== Installing JNA on CentOS
   
       sudo yum install jna
   
  -## How does CPU allocation work?
  +=== How does CPU allocation work?
   The library will read your `/proc/cpuinfo` if you have one or provide one and it will determine your CPU layout.  If you don't have one it will assume every CPU is on one CPU socket.
   
   The library looks for isolated CPUs determined by looking at the CPUs you are not running on by default. 
  
positive.code:    long currentAffinity = AffinitySupport.getAffinity();
     AffinitySupport.setAffinity(1L << 5); // lock to CPU 5.
     
  ## Debugging affinity state
  
  For a detailed of view of the current affinity state (as seen by the library),
  execute the following script on Linux systems:
  
  ```
  # change to the affinity lock-file directory (defaults to system property java.io.tmpdir)
  $ cd /tmp
  
  
negative.code: 
  http://vanillajava.blogspot.co.uk/2013/07/micro-jitter-busy-waiting-and-binding.html
  
  === isolcpus
  
  Java-Thread-Affinity requires that you first isolate some CPU's.
  
  