From: Greg Kurz <groug@kaod.org>
To: Pradeep Kiruvale <pradeepkiruvale@gmail.com>
Cc: Alberto Garcia <berto@igalia.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Markus Armbruster <armbru@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH] throttle: move throttling cmdline options to a separate header file
Date: Wed, 23 Nov 2016 13:13:43 +0100 [thread overview]
Message-ID: <20161123131343.5b047061@bahia> (raw)
In-Reply-To: <CAJ2SuLmWg29m07ynVMNi2DrnChGpdDwtUknhDb1NKrRMVUeQJA@mail.gmail.com>
On Tue, 22 Nov 2016 16:02:12 +0100
Pradeep Kiruvale <pradeepkiruvale@gmail.com> wrote:
> On 22 November 2016 at 14:55, Greg Kurz <groug@kaod.org> wrote:
>
> > On Tue, 22 Nov 2016 14:51:12 +0100
> > Alberto Garcia <berto@igalia.com> wrote:
> >
> > > On Tue 22 Nov 2016 01:49:51 PM CET, Greg Kurz wrote:
> > >
> > > > This will allow other subsystems (i.e. fsdev) to implement throttling
> > > > without duplicating the command line options.
> > > >
> > > > Signed-off-by: Greg Kurz <groug@kaod.org>
> > >
> > > Did you check if it's possible / easy to do defining a normal array
> > > instead of a macro and using qemu_opts_append() or something similar?
> > >
> > > Berto
> >
> > No I didn't due to lack of time but maybe Pradeep may have a look in this
> > direction ?
> >
>
> Only may be next year :)
>
Ok, and also, it will be the occasion to add the throttling options to
the legacy -virtfs command line option as well.
Cheers.
--
Greg
> -Pradeep
>
>
> >
> > Cheers.
> >
> > --
> > Greg
> >
next prev parent reply other threads:[~2016-11-23 12:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 12:49 [Qemu-devel] [RFC PATCH] throttle: move throttling cmdline options to a separate header file Greg Kurz
2016-11-22 12:55 ` no-reply
2017-01-18 10:38 ` Pradeep Kiruvale
2016-11-22 13:51 ` Alberto Garcia
2016-11-22 13:55 ` Greg Kurz
2016-11-22 15:02 ` Pradeep Kiruvale
2016-11-23 12:13 ` Greg Kurz [this message]
2016-11-23 12:22 ` 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=20161123131343.5b047061@bahia \
--to=groug@kaod.org \
--cc=armbru@redhat.com \
--cc=berto@igalia.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pradeepkiruvale@gmail.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@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).