All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alberto Garcia <berto@igalia.com>
To: Pradeep Kiruvale <pradeepkiruvale@gmail.com>,
	Greg Kurz <gkurz@linux.vnet.ibm.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: Fri, 06 May 2016 14:16:05 +0200	[thread overview]
Message-ID: <w51vb2r756i.fsf@maestria.local.igalia.com> (raw)
In-Reply-To: <CAJ2SuLniZ7i1Qz3zWL1Gcn9Qi4+fqp_+vNE_=b=3tLUPSVv+Ew@mail.gmail.com>

On Fri 06 May 2016 09:39:13 AM CEST, Pradeep Kiruvale wrote:

>> The throttling API is currently only used by block devices, and the
>> only documentation out-there is the code itself...
>
> Thanks, I will have a look and get back to you if I have any further
> questions regarding this.

As I said in an earlier e-mail:

1. the common API is in throttle.h.

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

Berto

  reply	other threads:[~2016-05-06 12:17 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
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 [this message]
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=w51vb2r756i.fsf@maestria.local.igalia.com \
    --to=berto@igalia.com \
    --cc=gkurz@linux.vnet.ibm.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.