qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Alberto Garcia <berto@igalia.com>
Cc: Manos Pitsidianakis <el13635@mail.ntua.gr>,
	Kevin Wolf <kwolf@redhat.com>, qemu-devel <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [Proposal] I/O throttling through new -object interface
Date: Tue, 13 Jun 2017 11:16:00 +0100	[thread overview]
Message-ID: <20170613101600.GC29273@stefanha-x1.localdomain> (raw)
In-Reply-To: <w51wp8hpek1.fsf@maestria.local.igalia.com>

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

On Mon, Jun 12, 2017 at 02:37:34PM +0200, Alberto Garcia wrote:
> On Fri 09 Jun 2017 06:06:09 PM CEST, Manos Pitsidianakis wrote:
> 
> >>>     -drive file=foo.qcow2,throttling.group=bar \
> >>>     -object throttle-group,iops-total=100,id=bar
> >>
> >>, and I guess the name would be throttling-group?
> >
> > Hm, I thought throttle-group would be nicer because it's shorter, but
> > I can change it, of course. I am not certain if there's a semantic
> > difference (because I am not a native speaker).
> 
> I'm not a native speaker either, I was pointing out that we would have
> throttling.group for -drive and then the throttle-group object.

I prefer "throttling-group" but it's not a big deal either way.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

  reply	other threads:[~2017-06-13 10:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-08 18:21 [Qemu-devel] [Proposal] I/O throttling through new -object interface Manos Pitsidianakis
2017-06-09 13:42 ` Alberto Garcia
2017-06-09 16:06   ` Manos Pitsidianakis
2017-06-12 12:37     ` Alberto Garcia
2017-06-13 10:16       ` Stefan Hajnoczi [this message]
2017-06-12 11:15 ` Kevin Wolf
2017-06-13 17:35   ` Manos Pitsidianakis
2017-06-12 13:59 ` Stefan Hajnoczi
2017-06-12 14:04 ` Stefan Hajnoczi

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=20170613101600.GC29273@stefanha-x1.localdomain \
    --to=stefanha@gmail.com \
    --cc=berto@igalia.com \
    --cc=el13635@mail.ntua.gr \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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).