Re: [Qemu-devel] [PATCH 0/3] drive-mirror: limit niov to MAX_IOV

2016-06-28 Thread Jeff Cody
On Wed, Jun 22, 2016 at 03:51:01PM -0400, John Snow wrote: > e5b43573 caused a regression in the preparation of our IO vectors, such > that if a small granularity but a large buffer size is chosen, we may > accidentally exceed MAX_IOV and the request will fail. > > This has been fixed before in ca

Re: [Qemu-devel] [PATCH 0/3] drive-mirror: limit niov to MAX_IOV

2016-06-28 Thread John Snow
Ping, all good? Jeff Cody, I think this is yours? On 06/22/2016 03:51 PM, John Snow wrote: > e5b43573 caused a regression in the preparation of our IO vectors, such > that if a small granularity but a large buffer size is chosen, we may > accidentally exceed MAX_IOV and the request will fail. >

[Qemu-devel] [PATCH 0/3] drive-mirror: limit niov to MAX_IOV

2016-06-22 Thread John Snow
e5b43573 caused a regression in the preparation of our IO vectors, such that if a small granularity but a large buffer size is chosen, we may accidentally exceed MAX_IOV and the request will fail. This has been fixed before in cae98cb8, and now we'll fix it again. To keep it fixed, we'll add an io