{
  "slug": "aerie",
  "term": "Aerie",
  "aliases": [],
  "definition": "Aerie is a research storage-class-memory architecture that combines direct user-space file access with a trusted service for metadata updates and coordination.",
  "note": "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. [aerie-paper]\n\nUnshipped 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. [aerie-paper]",
  "status": "research",
  "advantages": [],
  "limitations": [],
  "related": [
    "persistent-memory",
    "dax",
    "kuco",
    "splitfs"
  ],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-11-13",
  "citations": [
    {
      "id": "aerie-paper",
      "title": "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.",
      "url": "https://scail.cs.wisc.edu/papers/eurosys14-aerie.pdf",
      "accessed": "2026-11-13"
    },
    {
      "id": "hesela-direct-access",
      "title": "Hesela. Direct access does not transfer authority.",
      "url": "https://hesela.com/analyses/pmem-persistence-domains-dax/#direct-access-authority",
      "accessed": "2026-11-13"
    }
  ],
  "provenance": [
    "Primary-source design synthesis, not a reproduced prototype, hardware measurement or current deployment recommendation."
  ]
}