Level triggered flag was not set correctly

Signed-off-by: Eyal Salomon <esalomon@mellanox.com>
1. using Level triggered events for rdmacm file descriptor
2. releasing the transport outside the connection handlers
3. lowering the log level for library

Signed-off-by: Eyal Salomon <esalomon@mellanox.com>
raio example update

Signed-off-by: Eyal Salomon <esalomon@mellanox.com>
introducing xio_poll_completions

attempts to read at least min_nr events and up to nr events
from the completion queue assiociated with connection

Signed-off-by: Eyal Salomon <esalomon@mellanox.com>
removing messages from raio_server

Signed-off-by: Eyal Salomon <esalomon@mellanox.com>
fail ./configure with error message if 'numactl-devel' package is missing on machine

Signed-off-by: Alex Rosenbaum <Alexr@mellanox.com>
removing unneccessary messages from get_clock

Signed-off-by: Eyal Salomon <esalomon@mellanox.com>
in xio_alloc, if memeory allocation and registration in
one call is not supported. fallback to do the allocation and
register the memory

Signed-off-by: Eyal Salomon <esalomon@mellanox.com>
fixed invalid pointer assignment

Signed-off-by: Eyal Salomon <esalomon@mellanox.com>
New option added: disable huge memory allocations

Signed-off-by: Eyal Salomon <esalomon@mellanox.com>
Modify log level of messages according to:
FATAL	application need to die
ERROR	general error which is wrong input values or just a general failure
WARNING	nothing big happened, but application might work better if warning is handled (update OFED, tune parameters, ...)
INFO	as library there should be nothing we have to say to use/application (maybe just 'hello, I`m libXYZ, version 1.2.3')
DEBUG	control path logging
TRACE	fast path logging