Lines Matching full:incoming

163 Sockets that receive incoming request packets will bind to a local address,
178 This establishes the local address of the socket. Incoming MCTP messages that
180 The reference to 'incoming' is important here; a bound socket will only receive
181 messages with the TO bit set, to indicate an incoming request message, rather
194 incoming packets from any locally-connected network. A specific network value
195 will cause the socket to only receive incoming messages from that network.
202 7 bits of the type is matched on incoming messages (ie., the most-significant IC
346 address of the incoming message, including tag value (this will be needed in
417 socket to continue to receive incoming messages to the old (dest,tag) tuple, in
677 MCTP responders should use the EID and network values of an incoming request to
746 responsible for responding to incoming control protocol messages, any dynamic
752 data on incoming control protocol requests. It would interact with the kernel's
873 model of the message type; sockets are bound to an incoming message type,
928 - forward all incoming messages of a specific message-type to all sockets
935 and then release that allocation after the incoming response to that tag (TO=0)