Lines Matching refs:ID

72 left to the application.  AF_RXRPC only deals in blobs.  Even the operation ID
119 Connection ID
120 Service ID
135 (#) The first four bytes of the request data are the service operation ID.
209 non-zero service ID.
329 MESSAGE ID SRT DATA MEANING
331 RXRPC_USER_CALL_ID sr- User ID App's call specifier
348 This is used to indicate the application's call ID. It's an unsigned long
360 will be returned if there is no call with that user ID.
393 arrived and is awaiting acceptance. No user ID is associated with this,
394 as a user ID must subsequently be assigned by doing an RXRPC_ACCEPT.
399 assign it a user ID. It should be associated with an RXRPC_USER_CALL_ID
400 to indicate the user ID to be assigned. If there is no call to be
402 return error ENODATA. If the user ID is already in use by another call,
412 This is used to make a client call to probe if the specified service ID
414 recvmsg() for the service ID actually in use. The operation probed must
418 thereof) of the server, the service ID returned should be used for all
490 service ID to upgrade from and the second the service ID to upgrade to.
602 RXRPC_USER_CALL_ID specifies the user ID for this call
622 RXRPC_USER_CALL_ID - specifies the user ID for this call
628 A client may ask for a service ID it knows and ask that this be upgraded to a
633 the service - otherwise it will be altered to indicate the service ID the
634 server upgraded to. Note that the upgraded service ID is chosen by the server.
635 The caller has to wait until it sees the service ID in the reply before sending
671 .srx_service = VL_SERVICE_ID, /* RxRPC service ID */
679 More than one service ID may be bound to a socket, provided the transport
715 RXRPC_USER_CALL_ID specify user ID for this call
730 RXRPC_USER_CALL_ID specifies the user ID for this call
737 RXRPC_USER_CALL_ID specifies the user ID for this call
748 RXRPC_USER_CALL_ID specifies the user ID for this call
760 RXRPC_USER_CALL_ID specifies the user ID for this call
837 the server upgrade the service to a better one. The resultant service ID
844 debug_id is the call debugging ID to be used for tracing. This can be
918 The service ID that the call ended up with is returned into *_service.
948 and handling the incoming message, the ID assigned by the kernel utility
985 This is used to accept an incoming call and to assign it a call ID. This
1159 serves to anchor the peer data and keeps the connection ID counter.