RESOURCE device

The device resource. More...

Collaboration diagram for RESOURCE device:

Classes
class	lci::device_t
	The actual implementation for RESOURCE device. More...

Detailed Description

The device resource.

Parameters

[in,out]	net_max_sends	of type size_t; The maximum number of sends that can be posted to the underlying network queue at the same time.
[in,out]	net_max_recvs	of type size_t; The maximum number of receives that can be posted to the underlying network queue at the same time.
[in,out]	net_max_cqes	of type size_t; The maximum number of CQEs that can reside in the underlying network queue at the same time.
[in,out]	net_send_reserved_pct	of type double; Fraction of send queue slots reserved for high-priority operations (0.0-1.0).
[in,out]	ofi_lock_mode	of type uint64_t; For the OFI backend: the lock mode for the device.
[in,out]	alloc_default_endpoint	of type bool; Whether to allocate the default endpoint.
[in,out]	alloc_progress_endpoint	of type bool; Whether to allocate another endpoint for communication invoked by the progress function.
[in,out]	use_reg_cache	of type bool; Whether to use the memory registration cache (if compiled).
[in,out]	shm_enable	of type bool; Whether to enable the experimental intra-node shared-memory small-message transport.
[in,out]	shm_ring_size	of type size_t; Maximum shared-memory inbound slot-array size in bytes; the effective slot count is rounded down to a power of two.
[in,out]	shm_slot_size	of type size_t; Shared-memory fixed slot size in bytes.
[in,out]	shm_producer_cas_attempts	of type size_t; Maximum compare-and-swap attempts for each shared-memory ring producer reservation.
[in,out]	shm_consumer_cas_attempts	of type size_t; Maximum compare-and-swap attempts for each shared-memory ring consumer claim.
[in,out]	shm_max_polls	of type size_t; Maximum shared-memory receive slots progressed after each network completion poll.
[out]	uid	of type int; A unique device id across the entire process.
[in,out]	ibv_td_strategy	of type attr_ibv_td_strategy_t; For the IBV backend: the thread domain strategy.
[in,out]	name	of type const char*; Name of the resource.
[in,out]	user_context	of type void*; User context for the resource.