qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Zhang Haoyu <ahzhanghaoyu@gmail.com>
To: Wanpeng Li <kernellwp@gmail.com>, kvm <kvm@vger.kernel.org>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [question] Is there a plan to introduce a unified co-scheduling mechanism to CFS ?
Date: Fri, 10 Oct 2014 20:00:46 +0800	[thread overview]
Message-ID: <5437CA6E.2000802@gmail.com> (raw)
In-Reply-To: <5437C6A2.3020908@gmail.com>

 >> Hi,
 >>
 >> Is it worthy to introduce a unified co-scheduling mechanism to CFS ?
 >> Because multiple cooperating threads or tasks frequently synchronize 
with each other,
 >> not executing them concurrently would only increase the latency of 
synchronization.
 >> For example, a thread blocking in spinlock to waiting for another 
thread to release the same spinlock
 >> might reduce its waiting time by being executed concurrently with 
the thread which hold the same spinlock.
 >> In virtualization scenario, multiple vcpus (which belong to the same 
vm) co-scheduling is more desired
 >> when several cooperating threads/task is running in guest.
 >>
 >> Is there a plane for this work?
 >
 > Please refer to gang scheduler.
 >
Is there a mechanism to dynamically detect which vcpus belong to the 
same gang?
Maybe a cooperative degree can be used to decide the threshold of which 
vcpus belong to the same gang, just a wild thought.

 > Regards,
 > Wanpeng Li
 >>
 >> Thanks,
 >> Zhang Haoyu

      reply	other threads:[~2014-10-10 12:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-10 11:37 [Qemu-devel] [question] Is there a plan to introduce a unified co-scheduling mechanism to CFS ? Zhang Haoyu
2014-10-10 11:44 ` Wanpeng Li
2014-10-10 12:00   ` Zhang Haoyu [this message]

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=5437CA6E.2000802@gmail.com \
    --to=ahzhanghaoyu@gmail.com \
    --cc=kernellwp@gmail.com \
    --cc=kvm@vger.kernel.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).