xprt_register_transport(9) [centos man page]

XPRT_REGISTER_TRANSP(9) 					 Linux Networking					   XPRT_REGISTER_TRANSP(9)

NAME

       xprt_register_transport - register a transport implementation

SYNOPSIS

       int xprt_register_transport(struct xprt_class * transport);

ARGUMENTS

       transport
	   transport to register

DESCRIPTION

       If a transport implementation is loaded as a kernel module, it can call this interface to make itself known to the RPC client.

0
       transport successfully registered -EEXIST: transport already registered -EINVAL: transport module being unloaded

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014						   XPRT_REGISTER_TRANSP(9)

t_sndrel(3xti)															    t_sndrel(3xti)

Name
       t_sndrel - initiate an orderly release

Syntax
       #include <xti.h>

       int t_sndrel(fd)
       int fd;

Arguments
       fd	 Identifies the local transport endpoint where the connection exists.

Description
       This  function  is used to initiate an orderly release of a transport connection and indicates to the transport provider that the transport
       user has no more data to send. After issuing the user can not send any more data over the connection.  However,	a  user  can  continue	to
       receive data if an orderly indication has not been received.

       This  function  is  an  optional  service  of  the transport provider and is only supported if the transport provider returned service type
       T_COTS_ORD on or

       --------------------------------------
       Parameters   Before Call   After Call
       --------------------------------------
       fd	    x		  /
       --------------------------------------

Return Values
       Upon successful completion, a value of 0 is returned. On failure, a value of -1 is returned, and t_errno is set to indicate the error.

Diagnostics
       On failure, t_errno is set to one of the following:

       [TBADF]		   The specified file descriptor does not refer to a transport endpoint.

       [TOUTSTATE]	   The function was issued in the wrong sequence on the transport endpoint referenced by fd.

       [TFLOW]		   O_NONBLOCK was set, but the flow control mechanism prevented the transport provider from accepting the function at this
			   time.

       [TLOOK]		   An asynchronous event has occurred on the transport endpoint referenced by fd and requires immediate attention.

       [TNOTSUPPORT]	   This function is not supported by the underlying transport provider.

       [TSYSERR]	   A system error has occurred during execution of this function.

See Also
       t_getinfo(3xti), t_open(3xti), t_rcvrel(3xti)

																    t_sndrel(3xti)