-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
This page answers common questions about OSAI.
No. OSAI is not a Linux distribution.
No. OSAI is not a BSD fork.
No GPU is required. OSAI targets CPU-only AI and has no CUDA, Metal, or GPU acceleration dependency.
CPU-only AI is deployable on ordinary servers and appliances, avoids vendor GPU runtime dependency, and lets the OS control cores, memory placement, networking, and build/test work in one resource model.
Only measured results can answer that. OSAI has design targets for a narrow workload: CPU-only embedded app agents with explicit core ownership, memory arenas, and low-latency networking. It should not claim broad superiority over Linux/BSD.
It means hot AI workers should remain on their leased cores unless the service explicitly changes placement.
QEMU on macOS gives a reproducible correctness target for boot, memory, devices, and kernel basics. It is not a performance target.
Intel Desktop is accessible and exposes real P-core/E-core, NVMe, NIC, and sustained-performance behavior before the complexity of NUMA servers.
ARM/NVIDIA N1X-compatible work needs the OS architecture to be stable before AArch64 boot, GIC, SMMU, and cluster policies are added.
Early kernel code should be freestanding C99 plus minimal architecture assembly. C++ is allowed in userspace, runtime, and AI components.
Yes. OSAI should support static C/C++ services early.
Yes. This is the same policy as above: C and C++ are expected for early userspace, runtime, and application services.
Possibly, but Swift is not an early kernel or bring-up requirement.
Through explicit permissions, scoped workspaces, build/test sandboxes, diff review, signed updates, audit logs, and rollback.
This page defines the GitHub Wiki navigation sidebar.
- Architecture
- AI Cells
- CPU AI Runtime
- App Agents
- Memory System
- Networking
- Scheduler and Core Isolation
- Filesystem and Storage
- Driver Model
- Security Model
- Build System
- Build System
- Project Tracker
- Implementation Plan
- QEMU Full OS Core Workdown
- QEMU 100 Completion Plan
- Example Apps
- Codex Work Packages
- Testing and Benchmarking