All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kurz <gkurz@linux.vnet.ibm.com>
To: Pradeep Kiruvale <pradeepkiruvale@gmail.com>
Cc: Alberto Garcia <berto@igalia.com>,
	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 19:12:15 +0200	[thread overview]
Message-ID: <20160427191215.037c4c5c@bahia.huguette.org> (raw)
In-Reply-To: <CAJ2SuL=f6OZDG-GAy53pLr1W1cuF9-qbTpo1h_qPYjBvB+qgFw@mail.gmail.com>

On Wed, 27 Apr 2016 16:39:58 +0200
Pradeep Kiruvale <pradeepkiruvale@gmail.com> wrote:

> 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

9p is mostly aimed at sharing files... why would you want to use it for
block io instead of a true block device ? And how would you do that ?

> 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.
> 

Indeed.

> As a work around we are doing the throttling using cgroup. It has its own
> costs.

Can you elaborate ?

> 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.
> 

I still don't clearly understand what you are trying to do... maybe provide
a more detailed scenario.

> 
> -Pradeep

Cheers.

--
Greg

  reply	other threads:[~2016-04-27 17:12 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
2016-04-27 17:12         ` Greg Kurz [this message]
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=20160427191215.037c4c5c@bahia.huguette.org \
    --to=gkurz@linux.vnet.ibm.com \
    --cc=berto@igalia.com \
    --cc=pradeepkiruvale@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.