Modules§
Macros§
Structs§
- A control message, metadata about the message type, followed by bytes of data, this struct can be thought of as a protocol for an array of bytes, the control-message itself is functionally a variable length array of bytes, this should never go on the stack, since the actual payload would go outside of the bounds of this struct. Allocating bytes [
[u8; N]
] on the stack, then constructing a cmsg-pointer to that is alright though, use with caution. - A control message, metadata about the message type, followed by bytes of data, this struct can be thought of as a protocol for an array of bytes, the control-message itself is functionally a variable length array of bytes, this should never go on the stack, since the actual payload would go outside of the bounds of this struct. Allocating bytes [
[u8; N]
] on the stack, then constructing a cmsg-pointer to that is alright though, use with caution. - A set of signals
__kernel_timespec
is the type going over the syscall layer
Enums§
Constants§
Functions§
Type Aliases§
- Shared typedefs for 64 bit systems (GNU source)