qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pradeep Kiruvale <pradeepkiruvale@gmail.com>
To: Alberto Garcia <berto@igalia.com>
Cc: qemu-devel@nongnu.org,
	"qemu-discuss@nongnu.org" <qemu-discuss@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-discuss] iolimits for virtio-9p
Date: Wed, 27 Apr 2016 16:39:58 +0200	[thread overview]
Message-ID: <CAJ2SuL=f6OZDG-GAy53pLr1W1cuF9-qbTpo1h_qPYjBvB+qgFw@mail.gmail.com> (raw)
In-Reply-To: <20160427083840.GA27160@igalia.com>

[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]

On 27 April 2016 at 10:38, Alberto Garcia <berto@igalia.com> wrote:

> On Wed, Apr 27, 2016 at 09:29:02AM +0200, Pradeep Kiruvale wrote:
>
> > Thanks for the reply. I am still in the early phase, I will let you
> > know if any changes are needed for the APIs.
> >
> > We might also have to implement throttle-group.c for 9p devices, if
> > we want to apply throttle for group of devices.
>
> Fair enough, but again please note that:
>
> - throttle-group.c is not meant to be generic, but it's tied to
>   BlockDriverState / BlockBackend.
> - it is currently being rewritten:
>   https://lists.gnu.org/archive/html/qemu-block/2016-04/msg00645.html
>
> If you can explain your use case with a bit more detail we can try to
> see what can be done about it.
>
>
We want to use  virtio-9p for block io instead of virtio-blk-pci. But in
case of
virtio-9p we can just use fsdev devices, so we want to apply throttling
(QoS)
on these devices and as of now the io throttling only possible with the
-drive option.

As a work around we are doing the throttling using cgroup. It has its own
costs.
So, we want to have throttling for fsdev devices inside the qemu itself. I
am just
trying to understand and estimate time required for implementing it for the
fsdevices.


-Pradeep

[-- Attachment #2: Type: text/html, Size: 1931 bytes --]

  reply	other threads:[~2016-04-27 14:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19 12:09 [Qemu-devel] iolimits for virtio-9p Pradeep Kiruvale
2016-04-26  9:21 ` Stefan Hajnoczi
2016-04-26  9:23   ` Pradeep Kiruvale
2016-04-26 12:08 ` [Qemu-devel] [Qemu-discuss] " Alberto Garcia
2016-04-27  7:29   ` Pradeep Kiruvale
2016-04-27  8:38     ` Alberto Garcia
2016-04-27 14:39       ` Pradeep Kiruvale [this message]
2016-04-27 17:12         ` Greg Kurz
2016-04-28  9:45           ` Pradeep Kiruvale
2016-05-02 12:57             ` Greg Kurz
2016-05-02 15:49               ` Pradeep Kiruvale
2016-05-04 15:40                 ` Greg Kurz
2016-05-06  6:01                   ` Pradeep Kiruvale
2016-05-06  7:02                     ` Greg Kurz
2016-05-06  7:39                       ` Pradeep Kiruvale
2016-05-06 12:16                         ` Alberto Garcia
2016-06-01 10:06                           ` Pradeep Kiruvale

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ2SuL=f6OZDG-GAy53pLr1W1cuF9-qbTpo1h_qPYjBvB+qgFw@mail.gmail.com' \
    --to=pradeepkiruvale@gmail.com \
    --cc=berto@igalia.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-discuss@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).