Introduction
Since its launch, WSL 2 has revolutionized how developers interact with Windows and Linux file systems. In May 2026, a significant enhancement was made to speed up this access, which is excellent news for those whose workflow involves frequent interactions between these two environments.
From DrvFs to virtiofs
WSL 1, launched in 2016, used DrvFs to manage Windows drive access through a custom filesystem driver. It was efficient for file-heavy workloads, allowing almost direct NTFS access through a compatibility layer in the Windows NT kernel.
With WSL 2, introduced in May 2019, Microsoft opted for a full Linux kernel in a lightweight Hyper-V VM, improving native Linux workload execution. However, for cross-OS access, a new model was needed. Microsoft then integrated a Plan 9 (9P) file server into the Windows-side WSL service, enabling communication via a Hyper-V socket.
The Limits of the 9P Protocol
Though functional, the 9P protocol carries protocol overhead, with each operation bound by a message size parameter (msize=65536, 64 KB). This limitation is particularly noticeable for workloads involving many small files, where each interaction bears this overhead.
The Rise of virtiofs
In 2021, virtiofs emerged as an experimental opt-in, using VirtIO transport for shared-memory file access, reducing serialization overhead compared to 9P. Enabling virtiofs is done in the [wsl2] section of your .wslconfig with virtiofs=true. Since then, Microsoft has continuously improved this technology: device reuse improvements (PR #40298), shared mmap support without DAX (PR #40426), and now the DMA layer fix.
DMA Pool Management
Virtual machines on Hyper-V use bounce buffers for DMA I/O, a reserved memory region below the 4 GB DMA boundary directly addressable by hardware. Until recently, all virtio devices in a WSL 2 session shared a single global pool, creating contention during heavy I/O.
Thanks to PR #40654, each virtio device now has its own dedicated DMA pool, merged on May 27, 2026. This allows the allocation of a contiguous physical range below 4 GB at boot, published via sysfs.
Impact and Future Outlook
This improvement significantly reduces contention, enhancing performance for users with I/O-intensive workloads. For developers, this means better productivity and a smoother workflow between Windows and Linux.
Conclusion
WSL 2 continues to advance, making hybrid development environments more efficient than ever. For those looking to optimize their workflow between these two worlds, these enhancements are a blessing.
Let's discuss your project in 15 minutes.