qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Zhenyu Ye <yezhenyu2@huawei.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: dgilbert@redhat.com, xiexiangyou@huawei.com,
	qemu-devel@nongnu.org, jiangyiwen <jiangyiwen@huawei.com>,
	pbonzini@redhat.com
Subject: Re: [RFC PATCH] iothread: add set_iothread_poll_* commands
Date: Thu, 24 Oct 2019 21:53:54 +0800	[thread overview]
Message-ID: <5DB1ACF2.9080500@huawei.com> (raw)
In-Reply-To: <20191023151903.GI9574@stefanha-x1.localdomain>



On 2019/10/23 23:19, Stefan Hajnoczi wrote:
> On Tue, Oct 22, 2019 at 04:12:03PM +0800, yezhenyu (A) wrote:
>> Since qemu2.9, QEMU added three AioContext poll parameters to struct
>> IOThread: poll_max_ns, poll_grow and poll_shrink. These properties are
>> used to control iothread polling time.
>>
>> However, there isn't properly hmp commands to adjust them when the VM is
>> alive. It's useful to adjust them online when observing the impact of
>> different property value on performance.
>>
>> This patch add three hmp commands to adjust iothread poll-* properties
>> for special iothread:
>>
>> set_iothread_poll_max_ns: set the maximum polling time in ns;
>> set_iothread_poll_grow: set how many ns will be added to polling time;
>> set_iothread_poll_shrink: set how many ns will be removed from polling
>> time.
>>
>> Signed-off-by: Zhenyu Ye <yezhenyu2@huawei.com>
>> ---
>> hmp-commands.hx | 42 ++++++++++++++++++++
>> hmp.c | 30 +++++++++++++++
>> hmp.h | 3 ++
>> include/sysemu/iothread.h | 6 +++
>> iothread.c | 80 +++++++++++++++++++++++++++++++++++++++
>> qapi/misc.json | 23 +++++++++++
>> 6 files changed, 184 insertions(+)
> 
> poll-max-ns, poll-grow, poll-shrink are properties of IOThread objects.
> They can already be modified at runtime using:
> 
>   $ qemu -object iothread,id=iothread1
>   (qemu) qom-set /objects/iothread1 poll-max-ns 100000
> 
> I think there is no need for a patch.
> 
> Stefan
> 

Thanks for your review. I have considered using the `qom-set` command to modify
IOThread object's properties, however, this command is not friendly to primary
users. The help info for this command is only:

    qom-set path property value -- set QOM property

It's almost impossible to get the correct `path` parameter for primary user.

This patch provides a more convenient and easy-use hmp&qmp interface to modify
these IOThread properties. I think this patch still has a little value.

And I can implement this patch compactly by reusing your code.

Waiting for your reply.



  reply	other threads:[~2019-10-24 14:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-22  8:12 [RFC PATCH] iothread: add set_iothread_poll_* commands yezhenyu (A)
2019-10-22  8:51 ` Dr. David Alan Gilbert
2019-10-22 14:18   ` Zhenyu Ye
2019-10-22 14:27     ` Dr. David Alan Gilbert
2019-10-22 20:40 ` Eric Blake
2019-10-23  2:28   ` Zhenyu Ye
2019-10-23  2:40     ` Eric Blake
2019-10-23 15:19 ` Stefan Hajnoczi
2019-10-24 13:53   ` Zhenyu Ye [this message]
2019-10-24 13:56     ` Dr. David Alan Gilbert
2019-10-24 14:34       ` Zhenyu Ye
2019-10-24 14:38         ` Dr. David Alan Gilbert
2019-10-25  2:07           ` Zhenyu Ye
2019-10-25 11:51             ` 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=5DB1ACF2.9080500@huawei.com \
    --to=yezhenyu2@huawei.com \
    --cc=dgilbert@redhat.com \
    --cc=jiangyiwen@huawei.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=xiexiangyou@huawei.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).