Lines Matching refs:socket
175 connections are handled transparently. One client socket may be used to
176 make multiple simultaneous calls to the same service. One server socket
186 (*) Each internal UDP socket is retained [tunable] for a certain amount of
207 Interaction with the user of the RxRPC socket:
209 (*) A socket is made into a server socket by binding an address with a
220 socket. This may be overridden by supplying an alternate address to the
226 (*) A server socket may also be used to make client calls. To do this, the
272 (*) The server application has to provide the server socket with a keyring of
280 nominated by a socket option.
395 AF_RXRPC sockets support a few socket options at the SOL_RXRPC level:
414 made subsequently on this socket. optval should be NULL and optlen 0.
419 this socket. optval must point to an int containing one of the following
474 A keyring is passed to the server socket by naming it in a sockopt. The server
475 socket then looks the server secret keys up in this keyring when secure
488 (1) An RxRPC socket is set up by:
490 client = socket(AF_RXRPC, SOCK_DGRAM, PF_INET);
493 socket used - usually IPv4 but it can also be IPv6 [TODO].
500 .transport_type = SOCK_DGRAM, /* type of transport socket */
530 .transport_type = SOCK_DGRAM, /* type of transport socket */
537 (5) The request data should then be posted to the server socket using a series
549 (6) The reply data will then be posted to the server socket for recvmsg() to
569 (1) An RxRPC socket is created by:
571 server = socket(AF_RXRPC, SOCK_DGRAM, PF_INET);
574 socket used - usually IPv4.
576 (2) Security is set up if desired by giving the socket a keyring with server
588 The keyring can be manipulated after it has been given to the socket. This
596 .transport_type = SOCK_DGRAM, /* type of transport socket */
609 socket. It has no data, and has a single dataless control message
625 (6) The first request data packet will then be posted to the server socket for
629 Subsequent request data will be posted to the server socket for recvmsg()
637 (8) The reply data should then be posted to the server socket using a series
662 Any packets waiting in the socket's receive queue will be discarded if
666 the one server socket, using control messages on sendmsg() and recvmsg() to
677 (1) Use different keys directly on individual client calls on one socket
682 opening of a socket. Instead the utility is responsible for requesting a
690 intercepted before they get put into the socket Rx queue and the socket
693 To use the RxRPC facility, a kernel utility must still open an AF_RXRPC socket,
694 bind an address as appropriate and listen if it's to be a server socket, but
702 rxrpc_kernel_begin_call(struct socket *sock,
710 the socket is bound to. The call will go to the destination address of a
711 connected client socket unless an alternative is supplied (srx is
715 the key bound to the socket with the RXRPC_SECURITY_KEY sockopt. Calls
762 rxrpc_kernel_intercept_rx_messages(struct socket *sock,
765 This installs an interceptor function on the specified AF_RXRPC socket.
766 All messages that would otherwise wind up in the socket's Rx queue are
770 The interceptor function itself is provided with the address of the socket
772 to the call and the socket buffer containing the message.
791 socket buffer manipulation functions. A data message can be determined to
804 rxrpc_kernel_accept_call(struct socket *sock,
817 int rxrpc_kernel_reject_call(struct socket *sock);
819 This is used to reject the first incoming call on the socket's queue with
829 update the ACK state for the call. The socket buffer will be freed.
835 This is used to free a non-DATA socket buffer intercepted from an AF_RXRPC
836 socket.
842 This is used to determine if a socket buffer holds the last data message