Migrate from Dokany/DokanNet to WinFsp#43
Draft
Copilot wants to merge 4 commits into
Draft
Conversation
…Tests Replace all references to the renamed class across 10 endurance test files to fix build errors. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: hooyao <659145+hooyao@users.noreply.github.com>
Replace all remaining Dokan/DokanNet references with their WinFsp equivalents: - DokanFileSystemAdapter → WinFspFileSystemAdapter - DokanHostedService → WinFspHostedService - DokanTelemetry → FileSystemTelemetry (meter: ZipDrive.FileSystem) - IDokanOperations2 → Fsp.FileSystemBase - Dokany driver → WinFsp driver - dokan2.dll → winfsp-x64.dll Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: hooyao <659145+hooyao@users.noreply.github.com>
Agent-Logs-Url: https://github.com/hooyao/ZipDrive/sessions/ebb752f8-8a92-4f40-9a50-611a452cf0e8 Co-authored-by: hooyao <659145+hooyao@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Plan migration from Dokany to WinFsp with zero heap location
Migrate from Dokany/DokanNet to WinFsp
Apr 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replace DokanNet driver layer with WinFsp (
winfsp.net). Includes a comprehensive migration plan for future zero-heap read path usingIMemoryOwner<byte>and memory-mapped files.Driver swap
DokanNet2.3.0.3 →winfsp.net2.1.25156 inDirectory.Packages.propsWinFspFileSystemAdapterextendsFsp.FileSystemBase— mapsOpen/Read/ReadDirectoryEntry/GetFileInfo/GetVolumeInfotoIVirtualFileSystem, all write ops →STATUS_ACCESS_DENIEDWinFspHostedServicemanagesFileSystemHostmount lifecycle — FileSystemWatcher/ArchiveChangeConsolidator/reconciliation logic ported unchangedFileContextcarries per-handle path + isDirectory through WinFsp'sFileNode/FileDescpatternTelemetry
DokanTelemetry→FileSystemTelemetry, meterZipDrive.Dokan→ZipDrive.FileSystemMigration plan (
src/Docs/WINFSP_MIGRATION_PLAN.md)Documents future phases:
IBufferHandle/ReadFileDirectAsyncfor zero-copy read path throughIVirtualFileSystemMmapStorageStrategyreplacingMemoryStorageStrategy'sbyte[]with anonymousMemoryMappedFile+MmapMemoryManagerfor pointer-backedMemory<byte>— eliminates per-read GC allocationTarget read path (cache hit):
mmap pointer → Unsafe.CopyBlock → WinFsp IntPtr— zero managed heap allocations.Removed
DokanFileSystemAdapter.cs,DokanHostedService.cs,DokanTelemetry.csDokanreferences in source comments,CLAUDE.md, test files