linux-kernel - Re: [ANNOUNCE] DAXFS: A zero-copy, dmabuf-friendly filesystem for shared memory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <55e3d9f6-50d2-48c0-b7e3-fb1c144cf3e8@linux.alibaba.com>
Date: Mon, 26 Jan 2026 12:04:06 +0800
From: Gao Xiang <hsiangkao@...ux.alibaba.com>
To: Cong Wang <cwang@...tikernel.io>, linux-fsdevel@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, Cong Wang <xiyou.wangcong@...il.com>
Subject: Re: [ANNOUNCE] DAXFS: A zero-copy, dmabuf-friendly filesystem for
 shared memory

Hi Cong,

On 2026/1/25 01:10, Cong Wang wrote:
> Hello,
> 
> I would like to introduce DAXFS, a simple read-only filesystem
> designed to operate directly on shared physical memory via the DAX
> (Direct Access).
> 
> Unlike ramfs or tmpfs, which operate within the kernel’s page cache
> and result in fragmented, per-instance memory allocation, DAXFS
> provides a mechanism for zero-copy reads from contiguous memory
> regions. It bypasses the traditional block I/O stack, buffer heads,
> and page cache entirely.
> 
> Key Features
> - Zero-Copy Efficiency: File reads resolve to direct memory loads,
> eliminating page cache duplication and CPU-driven copies.
> - True Physical Sharing: By mapping a contiguous physical address or a
> dma-buf, multiple kernel instances or containers can share the same
> physical pages.
> - Hardware Integration: Supports mounting memory exported by GPUs,
> FPGAs, or CXL devices via the dma-buf API.
> - Simplicity: Uses a self-contained, read-only image format with no
> runtime allocation or complex device management.
> 
> Primary Use Cases
> - Multikernel Environments: Sharing a common Docker image across
> independent kernel instances via shared memory.
> - CXL Memory Pooling: Accessing read-only data across multiple hosts
> without network I/O.
> - Container Rootfs Sharing: Using a single DAXFS base image for
> multiple containers (via OverlayFS) to save physical RAM.
> - Accelerator Data: Zero-copy access to model weights or lookup tables
> stored in device memory.

Actually, EROFS DAX is already used for this way for various users,
including all the usage above.

Could you explain why EROFS doesn't suit for your use cases?

Thanks,
Gao Xiang


> 
> The source includes a kernel module and a mkdaxfs user-space tool for
> image creation, it is available here:
> https://github.com/multikernel/daxfs
> 
> I am looking forward to your feedback on the architecture and its
> potential integration to the upstream Linux kernel.
> 
> Best regards,
> Cong Wang