[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH for-2.5 v2 0/4] block: replace IOV_MAX with Bloc
From: |
Stefan Hajnoczi |
Subject: |
Re: [Qemu-devel] [PATCH for-2.5 v2 0/4] block: replace IOV_MAX with BlockLimits.max_iov |
Date: |
Mon, 23 Nov 2015 18:08:36 +0800 |
User-agent: |
Mutt/1.5.23 (2015-06-09) |
On Wed, Nov 18, 2015 at 03:51:29PM +0100, Kevin Wolf wrote:
> 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?
This series was forgotten. I have applied it for QEMU 2.6 since it is
not a bug fix.
Stefan
signature.asc
Description: PGP signature