designs/mctp/mctp-kernel.md

253 #### `sendto()`, `sendmsg()`, `send()` & `write()`: transmit an MCTP message
255 An MCTP message is transmitted using one of the `sendto()`, `sendmsg()`,
256 `send()` or `write()` syscalls. Using `sendto()` as the primary example:
274     len = sendto(sd, buf, sizeof(buf), 0,
286 message buffer passed to `sendto()`. If a message integrity check is to be
298 Using `sendto()` or `sendmsg()` on a connected socket may override the remote
301 allocated through a call to `sendto()` or `sendmsg()` on a connected socket is
303 expired either by timeout or by a subsequent `sendto()`.
379 an expanded `struct sockaddr` to the `recvfrom()` and `sendto()` system calls.
396 If the `addrlen` specified to `sendto()` or `recvfrom()` is sufficient to
494             rc = sendto(sd, &msg, sizeof(msg), 0,
498                     err(EXIT_FAILURE, "sendto");
567                     rc = sendto(sd, &msg, rc, 0,
570                             err(EXIT_FAILURE, "sendto");
603             /* We're doing a sendto() to a broadcast address here. If we were
605              * doing connect(); sendto();, in order to retain the tag
610             rc = sendto(sd, buf, 2, 0, (struct sockaddr *)&txaddr,
613                     err(EXIT_FAILURE, "sendto");
659 Transmitted messages (through `sendto()` and related system calls) specify their
699 To allow this, a `sendto()` with the `MCTP_TAG_OWNER` bit set in the `smctp_tag`
710 allocate a unique tag for the outgoing message. In this case, the `sendto()`
726 In particular, calling `sendto()` with a different address does not release the
733 `sendto()` to a broadcast address. Additionally, this reservation is not cleared