Re: [Qemu-devel] [PATCH 3/4] nbd/client: Support requests of additional block sizing info

2018-05-23 Thread Eric Blake
On 05/22/2018 10:33 AM, Vladimir Sementsov-Ogievskiy wrote: 02.05.2018 00:13, Eric Blake wrote: The NBD spec is clarifying [1] that a server may want to advertise different limits for READ/WRITE (in our case, 32M) than for TRIM/ZERO (in our case, nearly 4G).  Implement the client side support fo

Re: [Qemu-devel] [PATCH 3/4] nbd/client: Support requests of additional block sizing info

2018-05-22 Thread Vladimir Sementsov-Ogievskiy
02.05.2018 00:13, Eric Blake wrote: The NBD spec is clarifying [1] that a server may want to advertise different limits for READ/WRITE (in our case, 32M) than for TRIM/ZERO (in our case, nearly 4G). Implement the client side support for these alternate limits, by always requesting the new inform

Re: [Qemu-devel] [PATCH 3/4] nbd/client: Support requests of additional block sizing info

2018-05-03 Thread Vladimir Sementsov-Ogievskiy
03.05.2018 17:49, Eric Blake wrote: On 05/03/2018 04:17 AM, Vladimir Sementsov-Ogievskiy wrote: 02.05.2018 00:13, Eric Blake wrote: The NBD spec is clarifying [1] that a server may want to advertise different limits for READ/WRITE (in our case, 32M) than for TRIM/ZERO (in our case, nearly 4G). 

Re: [Qemu-devel] [PATCH 3/4] nbd/client: Support requests of additional block sizing info

2018-05-03 Thread Eric Blake
On 05/03/2018 04:17 AM, Vladimir Sementsov-Ogievskiy wrote: 02.05.2018 00:13, Eric Blake wrote: The NBD spec is clarifying [1] that a server may want to advertise different limits for READ/WRITE (in our case, 32M) than for TRIM/ZERO (in our case, nearly 4G).  Implement the client side support fo

Re: [Qemu-devel] [PATCH 3/4] nbd/client: Support requests of additional block sizing info

2018-05-03 Thread Vladimir Sementsov-Ogievskiy
02.05.2018 00:13, Eric Blake wrote: The NBD spec is clarifying [1] that a server may want to advertise different limits for READ/WRITE (in our case, 32M) than for TRIM/ZERO (in our case, nearly 4G). Implement the client side support for these alternate limits, by always requesting the new inform

[Qemu-devel] [PATCH 3/4] nbd/client: Support requests of additional block sizing info

2018-05-01 Thread Eric Blake
The NBD spec is clarifying [1] that a server may want to advertise different limits for READ/WRITE (in our case, 32M) than for TRIM/ZERO (in our case, nearly 4G). Implement the client side support for these alternate limits, by always requesting the new information (a compliant server must ignore