anchor.diff:  [[setup-configuration-memory]]
   ==== Memory Settings
   
  -The Linux kernel tries to use as much memory as possible for file system
  -caches and eagerly swaps out unused application memory, possibly resulting
  +Most operating systems try to use as much memory as possible for file system
  +caches and eagerly swap out unused application memory, possibly resulting
   in the elasticsearch process being swapped. Swapping is very bad for
   performance and for node stability, so it should be avoided at all costs.
   
  
positive.code: * **`mlockall`**
  +
  --
  The third option on Linux/Unix systems only, is to use
  http://opengroup.org/onlinepubs/007908799/xsh/mlockall.html[mlockall] to
  try to lock the process address space into RAM, preventing any Elasticsearch
  memory from being swapped out.  This can be done, by adding this line
  to the `config/elasticsearch.yml` file:
  
negative.code: --------------
  
  If you see that `mlockall` is `false`, then it means that the the `mlockall`
  request has failed.  The most probable reason, on Linux/Unix systems, is that
  the user running Elasticsearch doesn't have permission to lock memory.  This can 
  be granted by running `ulimit -l unlimited` as `root` before starting Elasticsearch.
  
  Another possible reason why `mlockall` can fail is that the temporary directory
  (usually `/tmp`) is mounted with the `noexec` option. This can be solved by
  