Add support for NBD_FLAG_CAN_MULTI_CONN to the server about go-nbd HOT 4 CLOSED

That would be very interesting! From an implementation perspective, I def. see this as being possible, and its a minimal enough extension for it to keep being close to the baseline implementation while offering performance improvements IMHO. Currently, we just read messages from a single connection, switch on their option, forward them to the backend and stop when the client sends the disconnect, so switching to this could probably be done by finding a way to track a client and then just spawning this loop for each new connection I suppose.

from go-nbd.

I tried experimenting by just making one line change here and it worked.

- 					TransmissionFlags: 0,
+ 					TransmissionFlags: 0b1000_0001_0000_0000,

First high bit represents NBD_FLAG_HAS_FLAGS
and 8th one represents NBD_FLAG_CAN_MULTI_CONN

We can define those constants and make the flag part of Options struct.

from go-nbd.

That's neat, I'll def. take a look. Having parallelism could def. speed things up - and the backends already need to handle locking themselves since its possible to connect more than one client, so this should be possible in a backwards-compatible way, too.

from go-nbd.

Released in https://github.com/pojntfx/go-nbd/releases/tag/v0.3.0

from go-nbd.