Visit The New, Modern Unix Linux Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #39
Difficulty: Easy
IC chips for computer systems are usually made of silicone.
True or False?
Linux & Unix Commands - Search Man Pages

dat_ep_get_status(3dat) [opensolaris man page]

dat_ep_get_status(3DAT) 			     Direct Access Transport Library Functions				   dat_ep_get_status(3DAT)

NAME
dat_ep_get_status - provide a quick snapshot of the Endpoint SYNOPSIS
cc [ flag... ] file... -ldat [ library... ] #include <dat/udat.h> DAT_RETURN dat_ep_get_status ( IN DAT_EP_HANDLE ep_handle, OUT DAT_EP_STATE *ep_state, OUT DAT_BOOLEAN *recv_idle, OUT DAT_BOOLEAN *request_idle ) PARAMETERS
ep_handle Handle for an instance of the Endpoint. ep_state Current state of the Endpoint. recv_idle Status of the incoming DTOs on the Endpoint. request_idle Status of the outgoing DTOs and RMR Bind operations on the Endpoint. DESCRIPTION
the dat_ep_get_status() function provides the Consumer a quick snapshot of the Endpoint. The snapshot consists of the Endpoint state and whether there are outstanding or in-progress, incoming or outgoing DTOs. Incoming DTOs consist of Receives. Outgoing DTOs consist of the Requests, Send, RDMA Read, RDMA Write, and RMR Bind. The ep_state parameter returns the value of the current state of the Endpoint ep_handle. State value is one of the following: DAT_EP_STATE_UNCONNECTED, DAT_EP_STATE_RESERVED, DAT_EP_STATE_PASSIVE_CONNECTION_PENDING, DAT_EP_STATE_ACTIVE_CONNECTION_PENDING, DAT_EP_STATE_TENTATIVE_CONNECTION_PENDING, DAT_EP_STATE_CONNECTED, DAT_EP_STATE_DISCONNECT_PENDING, or DAT_EP_STATE_DISCONNECTED. A recv_idle value of DAT_TRUE specifies that there are no outstanding or in-progress Receive DTOs at the Endpoint, and DAT_FALSE otherwise. A request_idle value of DAT_TRUE specifies that there are no outstanding or in-progress Send, RDMA Read, and RDMA Write DTOs, and RMR Binds at the Endpoint, and DAT_FALSE otherwise. This call provides a snapshot of the Endpoint status only. No heroic synchronization with DTO queuing or processing is implied. RETURN VALUES
DAT_SUCCESS The operation was successful. DAT_INVALID_HANDLE The ep_handle parameter is invalid. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Standard: uDAPL, 1.1, 1.2 | +-----------------------------+-----------------------------+ |MT-Level |Safe | +-----------------------------+-----------------------------+ SEE ALSO
libdat(3LIB), attributes(5) SunOS 5.11 16 Jul 2004 dat_ep_get_status(3DAT)

Check Out this Related Man Page

dat_ep_free(3DAT)				     Direct Access Transport Library Functions					 dat_ep_free(3DAT)

NAME
dat_ep_free - destroy an instance of the Endpoint SYNOPSIS
cc [ flag... ] file... -ldat [ library... ] #include <dat/udat.h> DAT_RETURN dat_ep_free ( IN DAT_EP_HANDLE ep_handle ) PARAMETERS
ep_handle Handle for an instance of the Endpoint. DESCRIPTION
The dat_ep_free() function destroys an instance of the Endpoint. The Endpoint can be destroyed in any Endpoint state except Reserved, Passive Connection Pending, and Tentative Connection Pending. The destruction of the Endpoint can also cause the destruction of DTOs and RMRs posted to the Endpoint and not dequeued yet. This includes com- pletions for all outstanding and in-progress DTOs/RMRs. The Consumer must be ready for all completions that are not dequeued yet either still being on the Endpoint recv_evd_handle and request_evd_handle or not being there. The destruction of the Endpoint during connection setup aborts connection establishment. If the Endpoint is in the Reserved state, the Consumer shall first destroy the associated Reserved Service Point that transitions the End- point into the Unconnected state where the Endpoint can be destroyed. If the Endpoint is in the Passive Connection Pending state, the Con- sumer shall first reject the associated Connection Request that transitions the Endpoint into the Unconnected state where the Endpoint can be destroyed. If the Endpoint is in the Tentative Connection Pending state, the Consumer shall reject the associated Connection Request that transitions the Endpoint back to Provider control, and the Endpoint is destroyed as far as the Consumer is concerned. The freeing of an Endpoint also destroys an Event Stream for each of the associated Event Dispatchers. Use of the handle of the destroyed Endpoint in any subsequent operation except for the dat_ep_free() fails. RETURN VALUES
DAT_SUCCESS The operation was successful. DAT_INVALID_HANDLE The ep_handle parameter is invalid. DAT_INVALID_STATE Parameter in an invalid state. The Endpoint is in DAT_EP_STATE_RESERVED, DAT_EP_STATE_PASSIVE_CONNECTION_PENDING, or DAT_EP_STATE_TENTATIVE_CONNECTION_PENDING. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Standard: uDAPL, 1.1, 1.2 | +-----------------------------+-----------------------------+ |MT-Level |Unsafe | +-----------------------------+-----------------------------+ SEE ALSO
libdat(3LIB), attributes(5) SunOS 5.11 16 Jul 2004 dat_ep_free(3DAT)

Featured Tech Videos