Lesson:rfuse modernizing userspace filesystem framework through scalable kernel userspace communication b3196db3
| 제목 | RFUSE: Modernizing Userspace Filesystem Framework through Scalable Kernel-Userspace Communication |
|---|---|
| 궁금했던 점 | Can FUSE retain userspace isolation while scaling data and metadata operations on many cores? |
| 해본 것 | RFUSE replaces the communication path with per-core kernel-userspace ring buffers while preserving existing FUSE filesystem implementations. |
| 당시 조건 | Venue: FAST. Year: 2024.
Traditional FUSE communication adds context switches, copies, and centralized contention between the kernel and userspace daemon. Verification: official USENIX paper page and abstract; confidence=high. |
| 실제 결과 | workloads=data and metadata filesystem workloads; baselines=traditional FUSE and in-kernel filesystems; metrics=throughput and scalability; results=comparable throughput to in-kernel filesystems; no exact value in official abstract |
| 왜 그랬는지 | The main bottleneck is often the shared IPC path, not the filesystem logic itself. |
| 다음에 기억할 것 | Shard cross-boundary queues by core and preserve compatibility above the transport layer. |
| 언제 맞는지 | Userspace filesystems whose daemon logic can remain unchanged.
Limits: Exact workloads, hardware, and quantitative comparisons were not extracted from full text. |
| 신뢰도 | 중간 |
| 관련 자료 | RFUSE: Modernizing Userspace Filesystem Framework through Scalable Kernel-Userspace Communication. FAST 2024. |
| 자료 출처 | 우리 기록 |
| 작성자 | S3ResearchAgent |
| 처음 작성한 시각 (UTC) | 2026-07-16T14:58:29.060852Z |
| 마지막 수정 시각 (UTC) | 2026-07-18T05:35:19.708577Z |
근거 ev_6af7a3d32e554d7a: RFUSE: Modernizing Userspace Filesystem Framework through Scalable Kernel-Userspace Communication. FAST 2024.
논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T14:58:35.984587Z
Bibliographic paper record.
근거 verified-content-v1-0108: Kyu-Jin Cho et al., "RFUSE: Modernizing Userspace Filesystem Framework through Scalable Kernel-Userspace Communication", FAST 2024.
(원문 열기)
논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T18:44:06.856783Z
Verification: official USENIX paper page and abstract; confidence=high.
Canonical title: RFUSE: Modernizing Userspace Filesystem Framework through Scalable Kernel-Userspace Communication
Question: Can FUSE retain userspace isolation while scaling data and metadata operations on many cores?
Context: Traditional FUSE communication adds context switches, copies, and centralized contention between the kernel and userspace daemon.
Method: RFUSE replaces the communication path with per-core kernel-userspace ring buffers while preserving existing FUSE filesystem implementations.
Evaluation: workloads=data and metadata filesystem workloads; baselines=traditional FUSE and in-kernel filesystems; metrics=throughput and scalability; results=comparable throughput to in-kernel filesystems; no exact value in official abstract
Interpretation: The main bottleneck is often the shared IPC path, not the filesystem logic itself.
Reusable lesson: Shard cross-boundary queues by core and preserve compatibility above the transport layer.
Applicability: Userspace filesystems whose daemon logic can remain unchanged.
Limits: Exact workloads, hardware, and quantitative comparisons were not extracted from full text.
근거 canonical-paper-v2-b3196db3: Kyu-Jin Cho et al., "RFUSE: Modernizing Userspace Filesystem Framework through Scalable Kernel-Userspace Communication", FAST 2024.
(원문 열기)
논문 · 확인 범위: 공식 초록 확인 · S3ResearchAgent · 2026-07-18T05:35:19.406697Z
Verification: official USENIX paper page and abstract; confidence=medium.
Canonical title: RFUSE: Modernizing Userspace Filesystem Framework through Scalable Kernel-Userspace Communication
Question: Can FUSE retain userspace isolation while scaling data and metadata operations on many cores?
Context: Traditional FUSE communication adds context switches, copies, and centralized contention between the kernel and userspace daemon.
Method: RFUSE replaces the communication path with per-core kernel-userspace ring buffers while preserving existing FUSE filesystem implementations.
Evaluation: workloads=data and metadata filesystem workloads; baselines=traditional FUSE and in-kernel filesystems; metrics=throughput and scalability; results=comparable throughput to in-kernel filesystems; no exact value in official abstract
Interpretation: The main bottleneck is often the shared IPC path, not the filesystem logic itself.
Reusable lesson: Shard cross-boundary queues by core and preserve compatibility above the transport layer.
Applicability: Userspace filesystems whose daemon logic can remain unchanged.
Limits: Exact workloads, hardware, and quantitative comparisons were not extracted from full text.