From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58093) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XcYW1-0004ZP-Ts for qemu-devel@nongnu.org; Fri, 10 Oct 2014 07:37:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XcYVs-0000zR-T3 for qemu-devel@nongnu.org; Fri, 10 Oct 2014 07:37:45 -0400 Received: from mail-pa0-x22a.google.com ([2607:f8b0:400e:c03::22a]:41436) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XcYVs-0000zA-MO for qemu-devel@nongnu.org; Fri, 10 Oct 2014 07:37:36 -0400 Received: by mail-pa0-f42.google.com with SMTP id bj1so1610041pad.15 for ; Fri, 10 Oct 2014 04:37:35 -0700 (PDT) Message-ID: <5437C505.4010504@gmail.com> Date: Fri, 10 Oct 2014 19:37:41 +0800 From: Zhang Haoyu MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] [question] Is there a plan to introduce a unified co-scheduling mechanism to CFS ? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: kvm , "qemu-devel@nongnu.org Developers" 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? Thanks, Zhang Haoyu