Re: [PATCH] nbd/server: Advertise MULTI_CONN for shared writable exports

2021-10-29 Thread Eric Blake
On Thu, Oct 28, 2021 at 04:37:36PM +0200, Kevin Wolf wrote: > Am 27.08.2021 um 17:09 hat Eric Blake geschrieben: > > According to the NBD spec, a server advertising > > NBD_FLAG_CAN_MULTI_CONN promises that multiple client connections will > > not see any cache inconsistencies: when properly

Re: [PATCH] nbd/server: Advertise MULTI_CONN for shared writable exports

2021-10-28 Thread Kevin Wolf
Am 27.08.2021 um 17:09 hat Eric Blake geschrieben: > According to the NBD spec, a server advertising > NBD_FLAG_CAN_MULTI_CONN promises that multiple client connections will > not see any cache inconsistencies: when properly separated by a single > flush, actions performed by one client will be

Re: [PATCH] nbd/server: Advertise MULTI_CONN for shared writable exports

2021-09-01 Thread Vladimir Sementsov-Ogievskiy
27.08.2021 21:45, Eric Blake wrote: On Fri, Aug 27, 2021 at 07:58:10PM +0300, Vladimir Sementsov-Ogievskiy wrote: 27.08.2021 18:09, Eric Blake wrote: According to the NBD spec, a server advertising NBD_FLAG_CAN_MULTI_CONN promises that multiple client connections will not see any cache

Re: [PATCH] nbd/server: Advertise MULTI_CONN for shared writable exports

2021-09-01 Thread Vladimir Sementsov-Ogievskiy
27.08.2021 18:09, Eric Blake wrote: According to the NBD spec, a server advertising NBD_FLAG_CAN_MULTI_CONN promises that multiple client connections will not see any cache inconsistencies: when properly separated by a single flush, actions performed by one client will be visible to another

Re: [PATCH] nbd/server: Advertise MULTI_CONN for shared writable exports

2021-08-27 Thread Eric Blake
On Fri, Aug 27, 2021 at 07:58:10PM +0300, Vladimir Sementsov-Ogievskiy wrote: > 27.08.2021 18:09, Eric Blake wrote: > > According to the NBD spec, a server advertising > > NBD_FLAG_CAN_MULTI_CONN promises that multiple client connections will > > not see any cache inconsistencies: when properly

Re: [PATCH] nbd/server: Advertise MULTI_CONN for shared writable exports

2021-08-27 Thread Eric Blake
On Fri, Aug 27, 2021 at 05:48:10PM +0100, Richard W.M. Jones wrote: > On Fri, Aug 27, 2021 at 10:09:16AM -0500, Eric Blake wrote: > > +# Parallel client connections are easier with libnbd than qemu-io: > > +if ! (nbdsh --version) >/dev/null 2>&1; then > > I'm curious why the parentheses are

Re: [PATCH] nbd/server: Advertise MULTI_CONN for shared writable exports

2021-08-27 Thread Vladimir Sementsov-Ogievskiy
27.08.2021 18:09, Eric Blake wrote: According to the NBD spec, a server advertising NBD_FLAG_CAN_MULTI_CONN promises that multiple client connections will not see any cache inconsistencies: when properly separated by a single flush, actions performed by one client will be visible to another

Re: [PATCH] nbd/server: Advertise MULTI_CONN for shared writable exports

2021-08-27 Thread Richard W.M. Jones
On Fri, Aug 27, 2021 at 10:09:16AM -0500, Eric Blake wrote: > +# Parallel client connections are easier with libnbd than qemu-io: > +if ! (nbdsh --version) >/dev/null 2>&1; then I'm curious why the parentheses are needed here? > +export nbd_unix_socket > +nbdsh -c ' > +import os > +sock =

[PATCH] nbd/server: Advertise MULTI_CONN for shared writable exports

2021-08-27 Thread Eric Blake
According to the NBD spec, a server advertising NBD_FLAG_CAN_MULTI_CONN promises that multiple client connections will not see any cache inconsistencies: when properly separated by a single flush, actions performed by one client will be visible to another client, regardless of which client did the