M4: Reusable Components, Security Hardening, and Performance Optimization

Aperta
#766 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
15/100
Tipo di issue
Refactoring
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
linux, rust

Direzione di ricerca

This is a multi-part milestone with no specific files named, so start by reading the existing realtime_core libraries and the M1–M3 evaluation tests and datasets the issue refers to. Agree on one small behavior-preserving extraction with maintainers before writing code. Done means the extracted core builds without Awkernel-specific dependencies and the relevant M1–M3 comparison tests still pass within their tolerances.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Refactor the sensing and localization components into reusable, platform-independent libraries that can run on Awkernel and other environments. Improve security, robustness, and performance while preserving validated behavior and reusing the evaluation infrastructure established in M1–M3.

Scope:

  • Build on the existing realtime_core libraries and consolidate reusable functionality without duplicating implementations
  • Separate algorithmic cores from platform-specific scheduling, communication, timing, logging, and synchronization adapters
  • Define APIs, ownership rules, initialization and reset behavior, and memory and resource contracts
  • Demonstrate reuse on Awkernel and a Linux-hosted test application
  • Harden input validation, resource limits, and unsafe or FFI boundaries
  • Add fuzz testing, property-based testing, and regression cases for malformed and extreme inputs
  • Optimize measured bottlenecks such as copying, allocation, data layout, and synchronization
  • Establish shared regression tests and CI coverage for supported environments

Completion criteria:

  • Shared cores can be built and used without Awkernel-specific dependencies, with documented platform requirements and feature configurations.
  • The same core implementations are exercised through Awkernel and Linux adapters using shared test datasets.
  • Behavior-preserving extraction passes the applicable M1–M3 comparison and regression tests within predefined tolerances.
  • Input-validation rules, resource bounds, and unsafe or FFI assumptions are documented and tested against a defined threat model.
  • Security findings are resolved or explicitly documented with their impact and mitigation.
  • Performance changes are evaluated against a fixed baseline, reporting accuracy, tail latency, maximum observed execution time, allocation and copy counts, and peak memory usage where applicable.
  • Optimization targets and permitted regressions are defined before evaluation; trade-offs are explicitly reported.
  • APIs, integration examples, build configurations, and reproduction steps are documented.

Implementation approach:

Separate behavior-preserving extraction from optimization and intentional behavior changes. Architecture work may begin before M3 is complete, but final acceptance must use the relevant M1–M3 validation assets. Essential input safety and known vulnerability fixes must not be deferred until M4.

Out of scope:

New perception or planning functionality, mandatory ROS 2 runtime dependencies in shared cores, kernel-level fault isolation, formal security certification, and formal worst-case execution-time guarantees.

Lingua principale
Rust
Stelle
282
Fork
12
Merge medio
2g 9h
PR unite (30g)
28

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di tier4/awkernel

Tutte le issue di tier4/awkernel

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.