From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:34086)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pradeepkiruvale@gmail.com>) id 1auzDI-0006kK-Dj
	for qemu-devel@nongnu.org; Tue, 26 Apr 2016 05:23:25 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pradeepkiruvale@gmail.com>) id 1auzDH-0003RI-El
	for qemu-devel@nongnu.org; Tue, 26 Apr 2016 05:23:24 -0400
MIME-Version: 1.0
In-Reply-To: <20160426092116.GC10650@stefanha-x1.localdomain>
References: <CAJ2SuLk8kL3nT-jcQ8Af3Xg0OT9kB=vR-n6cS0uxUB=6AWd1HQ@mail.gmail.com>
	<20160426092116.GC10650@stefanha-x1.localdomain>
Date: Tue, 26 Apr 2016 11:23:16 +0200
Message-ID: <CAJ2SuLn37NRBnd_Nb183Y_Jvmwvy91Ptw8y9WPijtYj4iG-+xQ@mail.gmail.com>
From: Pradeep Kiruvale <pradeepkiruvale@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b86c664db942305315fd779
Subject: Re: [Qemu-devel] iolimits for virtio-9p
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: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org, "qemu-discuss@nongnu.org" <qemu-discuss@nongnu.org>, Alberto Garcia <berto@igalia.com>

--047d7b86c664db942305315fd779
Content-Type: text/plain; charset=UTF-8

Hi Stefan,

Thanks for the reply and adding Alberto.

I am going through those APIs already.

Thanks & Regards,
Pradeep

On 26 April 2016 at 11:21, Stefan Hajnoczi <stefanha@gmail.com> wrote:

> On Tue, Apr 19, 2016 at 02:09:24PM +0200, Pradeep Kiruvale wrote:
> > We are planning to implement the io-limits for the virtio-9p driver i.e
> for
> > fsdev devices.
> > So, I am looking into the code base and how it has done for the block io
> > devices.
> >
> > I would like to know how difficult is this and is there some one out
> there
> > who has any plan to do this?
>
> CCing Alberto Garcia, QEMU I/O throttling maintainer.
>
> Take a look at include/qemu/throttle.h.  That is the common throttling
> API.
>
> Stefan
>

--047d7b86c664db942305315fd779
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Stefan,<div><br></div><div>Thanks for the reply and add=
ing Alberto.</div><div><br></div><div>I am going through those APIs already=
.</div><div><br></div><div>Thanks &amp; Regards,</div><div>Pradeep</div></d=
iv><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On 26 April 20=
16 at 11:21, Stefan Hajnoczi <span dir=3D"ltr">&lt;<a href=3D"mailto:stefan=
ha@gmail.com" target=3D"_blank">stefanha@gmail.com</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex"><span class=3D"">On Tue, Apr 19, 2016 at 02=
:09:24PM +0200, Pradeep Kiruvale wrote:<br>
&gt; We are planning to implement the io-limits for the virtio-9p driver i.=
e for<br>
&gt; fsdev devices.<br>
&gt; So, I am looking into the code base and how it has done for the block =
io<br>
&gt; devices.<br>
&gt;<br>
&gt; I would like to know how difficult is this and is there some one out t=
here<br>
&gt; who has any plan to do this?<br>
<br>
</span>CCing Alberto Garcia, QEMU I/O throttling maintainer.<br>
<br>
Take a look at include/qemu/throttle.h.=C2=A0 That is the common throttling=
<br>
API.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Stefan<br>
</font></span></blockquote></div><br></div>

--047d7b86c664db942305315fd779--