From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42812) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zz45B-00016e-G8 for qemu-devel@nongnu.org; Wed, 18 Nov 2015 09:51:38 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zz45A-0003tn-Lw for qemu-devel@nongnu.org; Wed, 18 Nov 2015 09:51:37 -0500 Date: Wed, 18 Nov 2015 15:51:29 +0100 From: Kevin Wolf Message-ID: <20151118145129.GD4817@noname.str.redhat.com> References: <1436435807-29422-1-git-send-email-stefanha@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1436435807-29422-1-git-send-email-stefanha@redhat.com> Subject: Re: [Qemu-devel] [PATCH for-2.5 v2 0/4] block: replace IOV_MAX with BlockLimits.max_iov List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org 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 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