Lines Matching refs:may

102  (*) Each connection goes to a particular "service".  A connection may not go
103      to multiple services.  A service may be considered the RxRPC equivalent of
110  (*) Up to a billion connections may be supported concurrently between one
122  (*) Each RxRPC operation is a "call".  A connection may make up to four
123      billion calls, but only up to four calls may be in progress on a
131      flag in the packet.  The number of packets of data making up one blob may
152      been received but may yet be discarded and re-requested.  The sender may
162  (*) An call may be aborted by either end at any time up to its completion.
175      connections are handled transparently.  One client socket may be used to
177      may handle calls from many clients.
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
248  (*) A call may be aborted by adding an abort control message to the control
386      accepted (it may have timed out, been aborted, etc.), then sendmsg will
508      non-privileged port will be used.  A UDP port may be shared between
543      the request.  Multiple requests may be made simultaneously.
615      ignored since the call for which the message was posted may have gone by
741      data buffers to be used.  msg_iov may not be NULL and must point
742      exclusively to in-kernel virtual addresses.  msg.msg_flags may be given
798      freeing, but this may pin the state of a call until the message is finally
821      Other errors may be returned if the call had been aborted (-ECONNABORTED)
908      The maximum amount of time in seconds that a call may be in progress
947      may not exceed rxrpc_rx_mtu in size.