configure: Summarise version and features

[rwmjones]

In ./configure output summarise the version of ubdsrv and the features which have been enabled.

Signed-off-by: Richard W.M. Jones [email protected]

[ming1]

Hello Richard,

The Summary log is very nice, but not sure if it is good to add the two nbd specific features log here.

Thanks,

[rwmjones]

My intent was to list all optional features (but actually I missed SDP). The reason for showing them is it makes it easy to see if you're building a full-featured package -- is "yes" present on every line.

[rwmjones]

BTW why does ublk even have an NBD client? We've written one already using the much more featureful libnbd: https://gitlab.com/nbdkit/libnbd/-/tree/master/ublk

[ming1]

BTW why does ublk even have an NBD client? We've written one already using the much more featureful libnbd: https://gitlab.com/nbdkit/libnbd/-/tree/master/ublk

Because nbd is very simple network storage and as you see, the implementation is easy(new added code is just tgt_nbd.c, which
just replaces kernel nbd driver).

And ublk-nbd is totally based on io_uring, so we can evaluate ublk/io_uring net handling performance.

Also last time, when I compare nbdublk with nbd-client & nbd
driver, nbdublk performs a bit wore than nbd driver.

Thanks,

[rwmjones]

I'd like to make a more coherent NBD ecosystem, and one part of that is supporting NBD URIs as much as possible. In libnbd's nbdublk you can do for example:

nbdublk /dev/ublkb0 nbd://server
nbdublk /dev/ublkb0 nbds://server:1234
nbdublk /dev/ublkb0 nbd+unix:///exportname?socket=/tmp/sock

This is one of the advantages of using a single library everywhere (although you could also consider adding URI support to ublk by following the spec).

[ming1]

I'd like to make a more coherent NBD ecosystem, and one part of that is supporting NBD URIs as much as possible. In libnbd's nbdublk you can do for example:

nbdublk /dev/ublkb0 nbd://server
nbdublk /dev/ublkb0 nbds://server:1234
nbdublk /dev/ublkb0 nbd+unix:///exportname?socket=/tmp/sock

OK, the URI interface looks one good idea.

This is one of the advantages of using a single library everywhere (although you could also consider adding URI support to ublk by following the spec).