Lines Matching full:socket
21 applications to use a single socket to talk to any other process in the
23 to N*N if you use a connection-oriented socket transport like TCP.
34 the end point of a connection. All socket operations that involve
46 * Socket interface
49 socket. The next section will cover the details. At any rate,
50 all I/O is performed through the standard BSD socket API.
57 attaches it to the socket. Once bound, the transport assignment
67 Socket Interface
71 AF_RDS and PF_RDS are the domain type to be used with socket(2)
72 to create RDS sockets. SOL_RDS is the socket-level to be used
73 with setsockopt(2) and getsockopt(2) for RDS specific socket
76 fd = socket(PF_RDS, SOCK_SEQPACKET, 0);
77 This creates a new, unbound RDS socket.
80 RDS honors the send and receive buffer size socket options.
82 a socket. A message is queued when sendmsg is called, and
95 This binds the socket to a local IP address and port, and a
97 SO_RDS_TRANSPORT socket option
115 Receives a message that was queued to this socket. The sockets
132 incoming message queued to the socket, or a pending notification,
149 specific destination on this particular socket.
161 socket. When setting the option, integer argument may be
163 value, RDS_TRANS_NONE will be returned on an unbound socket.
164 This socket option may only be set exactly once on the socket,
166 set SO_RDS_TRANSPORT on a socket for which the transport has
250 Messages waiting in the receive queue on the receiving socket
253 number of bytes queued equals or exceeds rcvbuf then the socket
254 is congested. All sends attempted to this socket's address
282 The general layer handles the socket API, congestion handling,
295 be sent and sets header fields as needed, based on the socket API.
302 while the socket is awoken. It is then passed back to the transport
306 per-socket information
326 The first time an attempt is made by an RDS socket to send data to
399 port]) over a single TCP socket between the 2 IP addresses involved. This
410 socket will be sent over the attached path using TCP to segment/reassemble
417 TCP socket per rds_conn_path, and this is managed by the transport via
424 local address and port that the PF_RDS socket is bound to.