Safe API Framework 0.1.0 build 384e6ae
Layered API framework for safety-related applications (ERTMS RBC reference targeting CENELEC EN 50128 SIL 4)
Loading...
Searching...
No Matches
rte_safechannel_t Struct Reference

Caller-owned storage for one rte_safechannel_t instance. Every field is private - reach it only through the functions below. No dynamic allocation (REQ-SAFECHANNEL-002): sized to hold up to RTE_SAFECHANNEL_MAX_LINKS opened netlink links plus whichever of rte_dual_channel_t/rte_channel_t is in use. More...

#include <rte_safechannel.h>

Data Structures

union  [union].impl

Data Fields

rte_safechannel_type_t type
bool is_open
rte_netlink_storage_t links [RTE_SAFECHANNEL_MAX_LINKS]
rte_netlink_handle_t link_handles [RTE_SAFECHANNEL_MAX_LINKS]
uint32_t link_count
union  impl

Detailed Description

Caller-owned storage for one rte_safechannel_t instance. Every field is private - reach it only through the functions below. No dynamic allocation (REQ-SAFECHANNEL-002): sized to hold up to RTE_SAFECHANNEL_MAX_LINKS opened netlink links plus whichever of rte_dual_channel_t/rte_channel_t is in use.

Definition at line 160 of file rte_safechannel.h.

Field Documentation

◆ type

rte_safechannel_type_t rte_safechannel_t::type

Definition at line 162 of file rte_safechannel.h.

◆ is_open

bool rte_safechannel_t::is_open

Definition at line 163 of file rte_safechannel.h.

◆ links

rte_netlink_storage_t rte_safechannel_t::links[RTE_SAFECHANNEL_MAX_LINKS]

Endpoints opened by this instance; ownership (closing them) stays with this module, not the caller (unlike rte_dual_channel_t, which takes already-opened handles it does not own).

Definition at line 168 of file rte_safechannel.h.

◆ link_handles

rte_netlink_handle_t rte_safechannel_t::link_handles[RTE_SAFECHANNEL_MAX_LINKS]

Definition at line 169 of file rte_safechannel.h.

◆ link_count

uint32_t rte_safechannel_t::link_count

Definition at line 170 of file rte_safechannel.h.


The documentation for this struct was generated from the following file: