Re: [Qemu-block] [PATCH for-2.5 v2 0/4] block: replace IOV_MAX with BlockLimits.max_iov

[Kevin Wolf]

Am 09.07.2015 um 11:56 hat Stefan Hajnoczi geschrieben:
> v2:
>  * Default to IOV_MAX instead of INT_MAX [Peter Lieven]
> 
> This series depends on "[PATCH] block/mirror: limit qiov to IOV_MAX elements".
> 
> IOV_MAX has been hardcoded in several places since preadv()/pwritev()/etc
> refuse to take more iovecs per call.  That's actually an implementation detail
> of raw-posix and we shouldn't spread that across the codebase.
> 
> This series adds BlockLimits.max_iov (similar to BlockLimits.max_transfer_len
> and other fields).  Current IOV_MAX users are converted to blk_get_max_iov().
> 
> By the way, the IOV_MAX vs BlockLimits.max_iov naming is slightly confusing 
> but
> follows the BlockLimits field naming convention.  Once IOV_MAX is banished no
> one will be bothered by the reverse naming anymore.
> 
> Suggested-by: Kevin Wolf <address@hidden>

I was just looking for patches marked as for-2.5 and found this one...
Is there a reason it wasn't applied or did we just forget about it?

Kevin