kuco · research · also KucoFS

Kuco

Kuco is a research persistent-memory file-system architecture that offloads lookup and concurrency work to userspace while retaining trusted kernel metadata updates.

Related Observatory article: Kuco on hesela.com

KucoFS implements Kuco. Userspace supplies located metadata addresses, but Kfs validates them and resolves the pathname itself when validation fails. [1]

Copy-on-write data persistence precedes the metadata log. Read protection is partition-grained, not full POSIX ACL support; atomic-mmap uses private copies and msync, not unrestricted in-place DAX stores. [1]

Relations

related
Persistent memory, Direct Access, Aerie, SplitFS

Citations

  1. Youmin Chen et al. Scalable Persistent Memory File System with Kernel-Userspace Collaboration. FAST 2021, pp. 81-95, sections 3.2-3.4, 4.2-4.5 and 5.1. (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/kuco.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

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