Cisco Cisco IPICS Release 2.1 Licensing Information

safest to attach them to the start of each source file to most effectively       

convey the exclusion of warranty; and each file should have at least the       

"copyright" line and a pointer to where the full notice is found.       

      

   <one line to give the library's name and a brief idea of what it does.>       

   Copyright (C) <year>  <name of author>       

      

   This library is free software; you can redistribute it and/or       

   modify it under the terms of the GNU Lesser General Public       

   License as published by the Free Software Foundation; either       

   version 2.1 of the License, or (at your option) any later version.       

      

   This library is distributed in the hope that it will be useful,       

   but WITHOUT ANY WARRANTY; without even the implied warranty of       

   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU       

   Lesser General Public License for more details.       

      

   You should have received a copy of the GNU Lesser General Public       

   License along with this library; if not, write to the Free Software       

   Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA       

      

Also add information on how to contact you by electronic and paper mail.       

      

You should also get your employer (if you work as a programmer) or your       

school, if any, to sign a "copyright disclaimer" for the library, if       

necessary.  Here is a sample; alter the names:       

      

 Yoyodyne, Inc., hereby disclaims all copyright interest in the       

 library 'Frob' (a library for tweaking knobs) written by James Random Hacker.       

      

 <signature of Ty Coon>, 1 April 1990       

 Ty Coon, President of Vice       

      

That's all there is to it!

Simple NUMA policy support. It consists of a numactl program to run

other programs with a specific NUMA policy and a libnuma shared library 

("NUMA API") to set NUMA policy in applications.

 

The libnuma binary interface is supposed to stay binary compatible. 

Incompatible changes will use new symbol version numbers.

 

In addition there are various test and utility programs, like

numastat to display NUMA allocation statistics and memhog.

 

In test there is a small regression test suite.

Note that regress assumes a unloaded machine with memory free on each

node. Otherwise you will get spurious failures in the non strict

policies (prefered, interleave)