An io_uring-based user-space block driver

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com
netapp-public

InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured

  • BUSE

    A block device in user space for Linux

    • I wonder if this could replace most uses of NBD (network block devices), and/or help get iSCSI into userspace where more flexible load-balancing policy can be implemented.

    It also reminds me of attempts to define BUSE[0][1][2], which would have been a block device equivalent of FUSE. IIRC it was abandoned for performance reasons -- the FUSE protocol isn't well designed and is only barely acceptable for VFS.

    If io_uring (+ careful use of zero-copy) has fixed the performance issues with userspace block devices, maybe it would be applicable to FUSE (or FUSE-v2)? I've tried using io_uring with the current FUSE protocol to reduce syscall overhead and it kinda works, but a protocol designed to operate in that mode from the beginning would be even better.

    [0] https://github.com/acozzette/BUSE

    [1] https://dspace.cuni.cz/bitstream/handle/20.500.11956/148791/...

    [2] https://dl.acm.org/doi/10.1145/3456727.3463768

  • freebsd-src

    The FreeBSD src tree publish-only repository. Experimenting with 'simple' pull requests....

    • FreeBSD has a /dev/cuse device, and a libcuse reimplemented on top of it, but it uses a different protocol from Linux's CUSE. You can see the FreeBSD implementation at https://github.com/freebsd/freebsd-src/blob/release/13.1.0/s... -- note how cuse_server_read() and cuse_server_write() are stubs.

    I am somewhat familiar with this because I wrote a FUSE/CUSE server library in Rust, and tried porting it to FreeBSD. The FUSE bits worked with only minor issues[0][1], but the CUSE bits were completely different so I had to turn off that part of the library for FreeBSD targets.

    [0] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253411

    [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253500

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo

  • trident

    Storage orchestrator for containers

    • I am amazed there isn't a built-in iSCSI volume driver for docker, podman, et al. There are third party things (netapp trident[1], etc.) but no generic driver. One would think -- given the ubiquity of SAN boxes populating racks outside of "cloud" operators -- you could "-v iscsi::/mountpoint" a network block device into a container out of the box. I suppose it's difficult to deal with in cross platform way. When you read the golang source for trident you see they're just exec-ing iscsiadm on linux container hosts.

    [1] https://github.com/NetApp/trident

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts

  • OpenShift Container Registry Storage on vSphere?

    3 projects | /r/redhat | 5 May 2022