WinSpd

Infrastructure

virtual disk drivers

SHOW HN2019

WinSpd

create “SCSI disks” as user mode processes on Windows

github.com

#virtual disk#scsi#windows driver#user mode#block device

46points
33comments
#841of 2,195 in 2019
Top 39%of 2019 by points

How HN took it

CuriousMostly questions and neutral comments

2 positive, 10 neutral or asking, 1 mixed, 1 critical, out of 14 comments about the project. Thread score +0.07.

Idea: 1 for, 1 againstDesign: 1 for, 0 against

The thread, comment by comment

Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.

positive neutral or mixed critical about another commenter or something else the maker

What HN said

What people liked

  • Smaller surface area with four fundamental operations

    From 1 comment
    • It has a smaller surface area (4 fundamental operations).
      rzzzt on HN
  • Async I/O and command queues supported by default

    From 1 comment
    • Yes. Async I/O in Windows happens at the file system level, so the answer is yes, by default. Command queues are supported by default as well, as this is a Storport virtual…
      billziss on HN

Objections

  • Kernel driver code may be error prone

    From 1 comment
    • Yep, but all involve Kernel drivers. Is a block-level driver less error prone by its nature?
      rkagerer on HN
  • Stability questioned compared to other projects

    From 1 comment
    • How bug-free is it? I tried Dokan and CBFS (Call Back File System) a long time ago. They were both great, but I ran into bugs fairly quickly with each.
      rkagerer on HN

Requests

  • Support for network shares performance

    From 1 comment
    • Does it work over network shares (SMB or NFS) and how would the performance look like in that case?
      zaarn on HN

Questions

  • How bug-free is it

    From 1 comment
    • How bug-free is it? I tried Dokan and CBFS (Call Back File System) a long time ago. They were both great, but I ran into bugs fairly quickly with each.
      rkagerer on HN
  • Advantage over iSCSI

    From 1 comment
    • What is the advantage of your framework compared to implementing the iSCSI protocol (SCSI over TCP) and using standard tools like Microsoft iSCSI Initiator?
      john_moscow on HN
  • Comparison to ImDisk

    From 1 comment
    • Why this over your own WinFsp? How does it compare to ImDisk?
      voltagex_ on HN

Alternatives named

  • Dokan / Dokany

    From 2 comments
    • How bug-free is it? I tried Dokan and CBFS (Call Back File System) a long time ago. They were both great, but I ran into bugs fairly quickly with each.
      rkagerer on HN
    • Dokany, a fork of Dokan is a very active project these days https://github.com/dokan-dev/dokany
      olavgg on HN
  • CBFS

    From 1 comment
    • How bug-free is it? I tried Dokan and CBFS (Call Back File System) a long time ago. They were both great, but I ran into bugs fairly quickly with each.
      rkagerer on HN
  • ImDisk

    From 2 comments
    • Why this over your own WinFsp? How does it compare to ImDisk?
      voltagex_ on HN
    • Just want to note, that ImDisk, mentioned here in the thread, while technically GPL too, can be stripped of non-GPL code easily, according to its author.
      lostmsu on HN
  • Projected File System

    From 1 comment
    • MS is actually working on their own replacement for Dokan that is called Projected File System [0]. If I understand correctly, they need it internally for handling large git…
      john_moscow on HN
  • iSCSI

    From 1 comment
    • What is the advantage of your framework compared to implementing the iSCSI protocol (SCSI over TCP) and using standard tools like Microsoft iSCSI Initiator?
      john_moscow on HN

Category, keywords, summaries and labels on this page were made by AI (Thread Reader v2) and not checked by hand. Each point links to the comments it came from.

Add a badge to your READMEShown on HackerShow
[![Shown on HackerShow](https://hackershow.org/badge.svg)](https://hackershow.org/show/19424614)