aerie · research

Aerie

Aerie is a research storage-class-memory architecture that combines direct user-space file access with a trusted service for metadata updates and coordination.

Related Observatory article: Aerie on hesela.com

Aerie separates libFS, a trusted user-space file-system service and a kernel mapping/protection manager. Direct access does not authorize clients to modify shared metadata. [1]

Unshipped metadata can leave newly written data unlinked after a client crash; libfs_sync ships those updates. Write-only files use the trusted service because ordinary page permissions are insufficient. [1]

Relations

related
Persistent memory, Direct Access, Kuco, SplitFS

Citations

  1. Haris Volos et al. Aerie: Flexible File-System Interfaces to Storage-Class Memory. EuroSys 2014, sections 4.2-4.3, 5.3 and 7.1. DOI: 10.1145/2592798.2592810. (accessed 2026-11-13)

Further reading

  1. Hesela. Direct access does not transfer authority. (accessed 2026-11-13)
Sources & caveats
  • Primary-source design synthesis, not a reproduced prototype, hardware measurement or current deployment recommendation.

JSON: /data/terms/aerie.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Aerie. Hesela. 2026-11-13. https://hesela.dev/terms/aerie/