From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:44372)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1X8NWl-0001DC-PH
	for qemu-devel@nongnu.org; Sat, 19 Jul 2014 01:49:56 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1X8NWc-0007P4-Kw
	for qemu-devel@nongnu.org; Sat, 19 Jul 2014 01:49:47 -0400
Received: from mail-we0-x236.google.com ([2a00:1450:400c:c03::236]:61331)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1X8NWc-0007P0-D2
	for qemu-devel@nongnu.org; Sat, 19 Jul 2014 01:49:38 -0400
Received: by mail-we0-f182.google.com with SMTP id k48so4198757wev.13
	for <qemu-devel@nongnu.org>; Fri, 18 Jul 2014 22:49:37 -0700 (PDT)
Sender: Paolo Bonzini <paolo.bonzini@gmail.com>
Message-ID: <53CA06ED.1090102@redhat.com>
Date: Sat, 19 Jul 2014 07:49:33 +0200
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
References: <53C9362C.8040507@windriver.com>
	<53C93C34.7030403@redhat.com>	<53C949BA.9040204@windriver.com>
	<53C97FEB.9060208@redhat.com> <53C9A440.7020306@windriver.com>
In-Reply-To: <53C9A440.7020306@windriver.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] is there a limit on the number of in-flight I/O
	operations?
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Chris Friesen <chris.friesen@windriver.com>, qemu-devel@nongnu.org

Il 19/07/2014 00:48, Chris Friesen ha scritto:
>>>
>>
>> I forgot about "-drive ...,iops_max=NNN". :)
> 
> I'm not sure it's actually useful though, since it specifies the max IO
> operations per second, not the maximum number of in-flight operations.

No, that's "-drive iops=NNN".  QEMU implements a leaky bucket algorithm,
where "iops_max" gives the size of the bucket and "iops" gives the
refill rate.

Paolo

> If the far end can't keep up with the requested rate of operations, then
> the number of in-flight operations is going to grow even if you throttle
> the number of operations per second.