#[repr(C)]pub struct InboxEntry {
pub len: AtomicUsize,
pub seq: AtomicUsize,
pub overflow: AtomicBool,
}Expand description
One ring entry’s bookkeeping: how many bytes of its slot are valid, the reply-correlation token the backend replies against, and whether the request that arrived was larger than the slot.
Per ENTRY, whatever storage the ring is over, and never inline in the per-queryable header – that is the split W1 made and the reason a family can size its own ring without the backend’s table growing a variant.
Fields§
§len: AtomicUsizeValid bytes in this entry’s slot.
seq: AtomicUsizeReply-correlation token. What it means is the backend’s business (the zenoh shim stores a reply-slot index); the ring only carries it from the producer to the consumer.
overflow: AtomicBoolSet when the incoming request exceeded slot_bytes. The payload is
then skipped and the consumer reports it, rather than the ring
truncating a request into a well-formed-looking short one.