qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Wang, Wei W" <wei.w.wang@intel.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	"yang.zhang.wz@gmail.com" <yang.zhang.wz@gmail.com>,
	"virtio-dev@lists.oasis-open.org"
	<virtio-dev@lists.oasis-open.org>,
	"quan.xu0@gmail.com" <quan.xu0@gmail.com>,
	"quintela@redhat.com" <quintela@redhat.com>,
	"liliang.opensource@gmail.com" <liliang.opensource@gmail.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"dgilbert@redhat.com" <dgilbert@redhat.com>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>,
	"nilal@redhat.com" <nilal@redhat.com>
Subject: Re: [Qemu-devel] [virtio-dev] Re: [PATCH v5 4/5] virtio-balloon: VIRTIO_BALLOON_F_FREE_PAGE_HINT
Date: Mon, 26 Mar 2018 16:04:03 +0100	[thread overview]
Message-ID: <20180326150403.GN19266@redhat.com> (raw)
In-Reply-To: <286AC319A985734F985F78AFA26841F739485EE3@shsmsx102.ccr.corp.intel.com>

On Mon, Mar 26, 2018 at 02:54:45PM +0000, Wang, Wei W wrote:
> On Monday, March 26, 2018 7:09 PM, Daniel P. Berrangé wrote:
> > 
> > As far as libvirt is concerned there are three sets of threads it provides
> > control over
> > 
> >  - vCPUs - each VCPU in KVM has a thread. Libvirt provides per-thread
> >    tunable control
> > 
> >  - IOThreads - each named I/O thread can be associated with one or more
> >    devices. Libvirt provides per-thread tunable control.
> > 
> >  - Emulator - any other QEMU thread which isn't an vCPU thread or IO thread
> >    gets called an emulator thread by libvirt. There is no-per thread
> >    tunable control - we can set tunables for entire set of emulator threads
> >    at once.
> > 
> 
> 
> Hi Daniel,
> Thanks for sharing the details, they are very helpful. I still have a question:
> 
> There is no fundamental difference between iothread and our optimization
> thread (it is similar to the migration thread, which is created when
> migration begins and terminated when migration is done) - both of them are
> pthreads and each has a name. Could we also add the similar per-thread
> tunable control in libvirt for such threads?
> 
> For example, in QEMU we can add a new migration qmp command,
> migrate_enable_free_page_optimization (just like other commands
> migrate_set_speed 10G), this command will create the optimization thread.
> In this way, creation of the thread is in libvirt's control, and libvirt
> can then support tuning the thread (e.g. pin it to any pCPU), right?

Anything is possible from a technical level, but from a design POV we
would rather not start exposing tunables for arbitrary device type specific
threads as they are inherantly non-portable and may not even exist in QEMU
long term as it is just an artifact of the current QEMU implementation.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

  reply	other threads:[~2018-03-26 15:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-16 10:48 [Qemu-devel] [PATCH v5 0/5] virtio-balloon: free page hint reporting support Wei Wang
2018-03-16 10:48 ` [Qemu-devel] [PATCH v5 1/5] bitmap: bitmap_count_one_with_offset Wei Wang
2018-03-16 10:48 ` [Qemu-devel] [PATCH v5 2/5] migration: use bitmap_mutex in migration_bitmap_clear_dirty Wei Wang
2018-03-16 10:48 ` [Qemu-devel] [PATCH v5 3/5] migration: API to clear bits of guest free pages from the dirty bitmap Wei Wang
2018-03-16 10:48 ` [Qemu-devel] [PATCH v5 4/5] virtio-balloon: VIRTIO_BALLOON_F_FREE_PAGE_HINT Wei Wang
2018-03-16 15:16   ` Michael S. Tsirkin
2018-03-18 10:36     ` Wei Wang
2018-03-19  4:24       ` Michael S. Tsirkin
2018-03-19  9:01         ` [Qemu-devel] [virtio-dev] " Wei Wang
2018-03-19 22:55           ` Michael S. Tsirkin
2018-03-20  2:16             ` Wei Wang
2018-03-20  2:59               ` Michael S. Tsirkin
2018-03-20  3:18                 ` Wei Wang
2018-03-20  3:24                   ` Michael S. Tsirkin
2018-03-22  3:13                     ` Wei Wang
2018-03-26 10:58                       ` Wei Wang
2018-03-26 11:09                     ` Daniel P. Berrangé
2018-03-26 14:54                       ` Wang, Wei W
2018-03-26 15:04                         ` Daniel P. Berrangé [this message]
2018-03-26 15:35                           ` Wang, Wei W
2018-03-30  9:52                     ` Wei Wang
2018-03-16 10:48 ` [Qemu-devel] [PATCH v5 5/5] migration: use the free page hint feature from balloon Wei Wang

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=20180326150403.GN19266@redhat.com \
    --to=berrange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=liliang.opensource@gmail.com \
    --cc=mst@redhat.com \
    --cc=nilal@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quan.xu0@gmail.com \
    --cc=quintela@redhat.com \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=wei.w.wang@intel.com \
    --cc=yang.zhang.wz@gmail.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).