IPC Mechanisms

Communication is the lifeline of a microkernel. VayuOS features CapBus, a revolutionary IPC engine that delivers sub-microsecond latency through hardware-direct messaging and cryptographically secured entitlements.

Speed Metrics How CapBus Works
SYNCHRONOUS LATENCY
0.35µs

Near-native speed on modern high-frequency silicon.

MSG THROUGHPUT
12.5M

Messages per second per core at peak load.

INTERNAL OVERHEAD
< 85ns

Fixed kernel-path overhead for capability validation.

The CapBus Engine

VayuOS doesn't just copy bytes; it transfers **Capabilities**. This allows for zero-copy data exchange with hardware-enforced security.

Zero-Copy Direct Mapping

Large data blocks are transferred by mapping the sender's physical memory pages directly into the receiver's address space via Capability Tokens.

Forwarding Entitlements

A service can safely delegate its permissions to another service for a single transaction, enabling complex service-mesh topologies at the OS level.

// Transfer read capability for a memory buffer
let buffer_cap = mem::grant_access(target_pid, Region::Shared, Rights::READ);
ipc::send(target_pid, Msg::Data(buffer_cap));

Communication Primitives

Cryptographic Isolation

Token Fingerprinting

Every IPC token is unique and cannot be forged or guessed, preventing "Confused Deputy" attacks common in legacy OS IPC.

Rate Limiting

The kernel enforces hard quotas on IPC frequency per domain, mitigating internal denial-of-service attempts by rogue processes.

Domain Revocation

Capabilities can be revoked instantly system-wide, allowing the OS to neutralize a compromised service in sub-milliseconds.