Lines Matching full:calls

65      to speed up subsequent calls.
123      billion calls, but only up to four calls may be in progress on a
126  (#) Calls are two-phase and asymmetric: the client sends its request data,
141      set for the lifetime of that connection, and all subsequent calls made
146  (#) Calls use ACK packets to handle reliability.  Data packets are also
175      make multiple simultaneous calls to the same service.  One server socket
176      may handle calls from many clients.
179      concurrent calls, up to a tunable limit.
189  (#) A client-side connection is only shared between calls if they have
190      the same key struct describing their security (and assuming the calls
191      would otherwise share the connection).  Non-secured calls would also be
202  (#) If an ICMP error is received, all calls affected by that error will be
225  (#) A server socket may also be used to make client calls.  To do this, the
261      (#) Notifications of incoming calls.
326 calls, to invoke certain actions and to report certain conditions.  These are:
467      This is used to specify the minimum security level required for calls on
599      of sendmsg() calls, each with the following control message attached:
636 any more calls (further calls to the same destination will be blocked until the
694  (5) The server is then set to listen out for incoming calls::
734      of sendmsg() calls, each with the following control messages attached:
778  (1) Use different keys directly on individual client calls on one socket
821      the key bound to the socket with the RXRPC_SECURITY_KEY sockopt.  Calls
993      function is similar to rxrpc_kernel_begin_call() and calls accepted must
1005      a BUSY message.  -ENODATA is returned if there were no incoming calls.
1052      on the server).  The caller should compare the numbers of two calls to see
1095      This specifies the minimum security level required for calls on this
1141      list.  Dead calls are kept around for a little while for the purpose of