Re: [Qemu-devel] [PATCH v2] block: avoid creating too large iovecs in multiwrite_merge

2010-02-01 Thread Christoph Hellwig
On Tue, Jan 26, 2010 at 06:07:45PM -0600, Anthony Liguori wrote: > On 01/26/2010 07:49 AM, Christoph Hellwig wrote: > >If we go over the maximum number of iovecs support by syscall we get > >back EINVAL from the kernel which translate to I/O errors for the guest. > > > >Add a MAX_IOV defintion for

Re: [Qemu-devel] [PATCH v2] block: avoid creating too large iovecs in multiwrite_merge

2010-01-26 Thread Anthony Liguori
On 01/26/2010 07:49 AM, Christoph Hellwig wrote: If we go over the maximum number of iovecs support by syscall we get back EINVAL from the kernel which translate to I/O errors for the guest. Add a MAX_IOV defintion for platforms that don't have it. For now we use the same 1024 define that's use

[Qemu-devel] [PATCH v2] block: avoid creating too large iovecs in multiwrite_merge

2010-01-26 Thread Christoph Hellwig
If we go over the maximum number of iovecs support by syscall we get back EINVAL from the kernel which translate to I/O errors for the guest. Add a MAX_IOV defintion for platforms that don't have it. For now we use the same 1024 define that's used on Linux and various other platforms, but until t