The initialization and shutdown interface functions can be found from the starneig/node.h header file. The library provides separate header files for shared memory (starneig/sep_sm.h, starneig/gep_sm.h) and distributed memory (starneig/sep_dm.h, starneig/gep_dm.h). However, a user may simply include all header files as follows:

#include <starneig/starneig.h>

Certain header files and interface functions exist only when the library is compiled with MPI and ScaLAPACK / BLACS support. The configuration of the installed library can be found from the starneig/configuration.h header file. See module Library configuration for further information.

Each node must call the starneig_node_init() interface function to initialize the library and the starneig_node_finalize() interface function to shutdown the library:

starneig_node_init(cores, gpus, flags);
...
starneig_node_finalize();

The starneig_node_init() interface function initializes StarPU (and cuBLAS) and pauses all worker threads. The cores argument specifies the total number of used CPU cores. In distributed memory mode, one of these CPU cores is automatically allocated for the StarPU-MPI communication thread. The gpus argument specifies the total number of used GPUs. One or more CPU cores are automatically allocated for GPU devices. The flags (starneig_flag_t) argument can provide additional configuration information.

A node can also be configured with default values:

starneig_node_init(-1, -1, STARNEIG_DEFAULT);

This tells the library to use all available CPU cores and GPUs. See module Intra-node execution environment for further information.

Most interface functions return one of the following values:

STARNEIG_SUCCESS (0): The interface function was executed successfully.
A negative number -i: The i'th interface function argument was invalid.
A positive number i: The interface function encountered an error or a warning was raised. See module Error codes for further information.

All return values (starneig_error_t) are defined in the starneig/error.h header file.

Remarks: The library may call the exit() and abort() functions if an interface function encounters a fatal error from which it cannot recover.; The StarPU performance models must be calibrated before the software can function efficiently on heterogeneous platforms (CPUs + GPUs). The calibration is triggered automatically if the models are not calibrated well enough for a given problem size. This may impact the execution time negatively during the first run. Please see the StarPU handbook for further information: http://starpu.gforge.inria.fr/doc/html/Scheduling.html