Linux Kernel
3.7.1
|
The error codes returned by NetIO functions. More...
Enumerations | |
enum | netio_error_t { NETIO_NO_ERROR = 0, NETIO_PKT = 0, NETIO_ERR_MAX = -701, NETIO_NOT_REGISTERED = -701, NETIO_NOPKT = -702, NETIO_NOT_IMPLEMENTED = -703, NETIO_QUEUE_FULL = -704, NETIO_BAD_AFFINITY = -705, NETIO_CANNOT_HOME = -706, NETIO_BAD_CONFIG = -707, NETIO_TOOMANY_XMIT = -708, NETIO_UNREG_XMIT = -709, NETIO_ALREADY_REGISTERED = -710, NETIO_LINK_DOWN = -711, NETIO_FAULT = -712, NETIO_BAD_CACHE_CONFIG = -713, NETIO_ERR_MIN = -713, NETIO_NO_RESPONSE = 1 } |
The error codes returned by NetIO functions.
Error codes returned from NetIO routines.
NetIO functions return 0 (defined as NETIO_NO_ERROR) on success, and a negative value if an error occurs.
In cases where a NetIO function failed due to a error reported by system libraries, the error code will be the negation of the system errno at the time of failure. The netio_strerror() function will deliver error strings for both NetIO and system error codes.
enum netio_error_t |
The set of all NetIO errors.
NETIO_NO_ERROR |
Operation successfully completed. |
NETIO_PKT |
A packet was successfully retrieved from an input queue. |
NETIO_ERR_MAX |
Largest NetIO error number. |
NETIO_NOT_REGISTERED | |
NETIO_NOPKT |
No packet was available to retrieve from the input queue. |
NETIO_NOT_IMPLEMENTED |
The requested function is not implemented. |
NETIO_QUEUE_FULL |
On a registration operation, the target queue already has the maximum number of tiles registered for it, and no more may be added. On a packet send operation, the output queue is full and nothing more can be queued until some of the queued packets are actually transmitted. |
NETIO_BAD_AFFINITY |
The calling process or thread is not bound to exactly one CPU. |
NETIO_CANNOT_HOME |
Cannot allocate memory on requested controllers. |
NETIO_BAD_CONFIG |
On a registration operation, the IPP specified is not configured to support the options requested; for instance, the application wants a specific type of tagged headers which the configured IPP doesn't support. Or, the supplied configuration information is not self-consistent, or is out of range; for instance, specifying both NETIO_RECV and NETIO_NO_RECV, or asking for more than NETIO_MAX_SEND_BUFFERS to be preallocated. On a VLAN or bucket configure operation, the number of items, or the base item, was out of range. |
NETIO_TOOMANY_XMIT |
Too many tiles have registered to transmit packets. |
NETIO_UNREG_XMIT |
Packet transmission was attempted on a queue which was registered with transmit disabled. |
NETIO_ALREADY_REGISTERED |
This tile is already registered with the IPP. |
NETIO_LINK_DOWN |
The Ethernet link is down. The application should try again later. |
NETIO_FAULT |
An invalid memory buffer has been specified. This may be an unmapped virtual address, or one which does not meet alignment requirements. For netio_input_register(), this error may be returned when multiple processes specify different memory regions to be used for NetIO buffers. That can happen if these processes specify explicit memory regions with the NETIO_FIXED_BUFFER_VA flag, or if tmc_cmem_init() has not been called by a common ancestor of the processes. |
NETIO_BAD_CACHE_CONFIG |
Cannot combine user-managed shared memory and cache coherence. |
NETIO_ERR_MIN |
Smallest NetIO error number. |
NETIO_NO_RESPONSE |
Used internally to mean that no response is needed; never returned to an application. |
Definition at line 40 of file netio_errors.h.