From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37189) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X8QHe-0001ak-FU for qemu-devel@nongnu.org; Sat, 19 Jul 2014 04:46:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1X8QHY-0007hk-An for qemu-devel@nongnu.org; Sat, 19 Jul 2014 04:46:22 -0400 Received: from lputeaux-656-01-25-125.w80-12.abo.wanadoo.fr ([80.12.84.125]:39202 helo=paradis.irqsave.net) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X8QHY-0007he-49 for qemu-devel@nongnu.org; Sat, 19 Jul 2014 04:46:16 -0400 Date: Sat, 19 Jul 2014 10:45:37 +0200 From: =?iso-8859-1?Q?Beno=EEt?= Canet Message-ID: <20140719084537.GA3058@irqsave.net> References: <53C9362C.8040507@windriver.com> <53C93C34.7030403@redhat.com> <53C949BA.9040204@windriver.com> <53C97FEB.9060208@redhat.com> <53C9A440.7020306@windriver.com> <53CA06ED.1090102@redhat.com> <53CA0FC4.8080802@windriver.com> <53CA1D06.9090601@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <53CA1D06.9090601@redhat.com> Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] is there a limit on the number of in-flight I/O operations? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Chris Friesen , qemu-devel@nongnu.org The Saturday 19 Jul 2014 =E0 09:23:50 (+0200), Paolo Bonzini wrote : > Il 19/07/2014 08:27, Chris Friesen ha scritto: > > Does it track in-flight operations though? Or just how many operatio= ns > > can be requested in a given amount of time? >=20 > It should track in flight operations. However, I'm not sure it support= s > the iops=3D0 case properly, since I do not see anything in > tracked_request_end that ceases the accounting of the current operation= . > Benoit, can you answer? >=20 > Paolo I think in the throttling case the number of in flight operation is limit= ed by the emulated hardware queue. Else request would pile up and throttling wo= uld be inefective. So this number should be around: #define VIRTIO_PCI_QUEUE_MAX 64 or somet= hing like than that. >=20 > > If it tracks how many operations can be requested, then if the "iops" > > parameter is larger than what the server can maintain then the number= of > > in-flight operations could still grow indefinitely. > >=20 > > I suppose I'll have to check the code. :) >=20