it would be cool if diod had native support for vsock
I'm hoping it could improve performance when diod is mounted in virtual machines
currently I notice ~10 times performance degradation when vsock is setup through socat/tcp (tested with fio)
which is still better than ~100 times losses over ssh port forwarding, but still I'm wondering if we could approach virtiofs performance (which is close to native)
current setup with socat/tcp
host:
diod --listen 127.0.0.1:9564 --export /home/user/share --no-auth
socat VSOCK-LISTEN:9564,fork TCP:127.0.0.1:9564 &
qemu-system-x86_64 ... -device vhost-vsock-pci,guest-cid=3 ...
guest:
socat TCP-LISTEN:9564,fork,reuseaddr VSOCK-CONNECT:2:9564
sudo mount -t 9p -o trans=tcp,port=9564,uname=user,access=any,aname=/home/user/share 127.0.0.1 /home/user/share
correct me if I'm wrong, but diod doesn't have any virtio transport support? I'm aware that it exists builtin in qemu, but I'd rather avoid it due to security considerations
it would be cool if diod had native support for vsock
I'm hoping it could improve performance when diod is mounted in virtual machines
currently I notice ~10 times performance degradation when vsock is setup through socat/tcp (tested with fio)
which is still better than ~100 times losses over ssh port forwarding, but still I'm wondering if we could approach virtiofs performance (which is close to native)
current setup with socat/tcp
host:
diod --listen 127.0.0.1:9564 --export /home/user/share --no-auth
socat VSOCK-LISTEN:9564,fork TCP:127.0.0.1:9564 &
qemu-system-x86_64 ... -device vhost-vsock-pci,guest-cid=3 ...
guest:
socat TCP-LISTEN:9564,fork,reuseaddr VSOCK-CONNECT:2:9564
sudo mount -t 9p -o trans=tcp,port=9564,uname=user,access=any,aname=/home/user/share 127.0.0.1 /home/user/share
correct me if I'm wrong, but diod doesn't have any virtio transport support? I'm aware that it exists builtin in qemu, but I'd rather avoid it due to security considerations