All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alberto Garcia <berto@igalia.com>
To: Pradeep Kiruvale <pradeepkiruvale@gmail.com>,
	qemu-devel@nongnu.org,
	"qemu-discuss@nongnu.org" <qemu-discuss@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-discuss] iolimits for virtio-9p
Date: Tue, 26 Apr 2016 14:08:14 +0200	[thread overview]
Message-ID: <w51y480a7yp.fsf@maestria.local.igalia.com> (raw)
In-Reply-To: <CAJ2SuLk8kL3nT-jcQ8Af3Xg0OT9kB=vR-n6cS0uxUB=6AWd1HQ@mail.gmail.com>

On Tue 19 Apr 2016 02:09:24 PM CEST, 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?

Hi,

as Stefan said already, the common API is in throttle.h.

It should be generic enough to be used in other parts of QEMU, but tell
me if you feel that it needs changes.

Once you configure the throttling settings you essentially only need to
call throttle_schedule_timer() to see if a request needs to be
throttled, and afterwards throttle_account() to register the I/O that
has been peformed.

You'll see that there's also throttle-group.c, but that's specific to
the block layer and not meant to be generic.

Berto

  parent reply	other threads:[~2016-04-26 12:08 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 ` Alberto Garcia [this message]
2016-04-27  7:29   ` [Qemu-devel] [Qemu-discuss] " Pradeep Kiruvale
2016-04-27  8:38     ` Alberto Garcia
2016-04-27 14:39       ` Pradeep Kiruvale
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=w51y480a7yp.fsf@maestria.local.igalia.com \
    --to=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.