Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp2345628imm; Thu, 27 Sep 2018 11:14:56 -0700 (PDT) X-Google-Smtp-Source: ACcGV60hGcqHbE6MB+r6gAatK+DuAGE+cQw2GcPhYw4dLtf6c5cAa7mhRgyxrZvrAdo0IemYvOtK X-Received: by 2002:a62:6781:: with SMTP id t1-v6mr12685155pfj.200.1538072096840; Thu, 27 Sep 2018 11:14:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1538072096; cv=none; d=google.com; s=arc-20160816; b=yHNWiJ1mIPuBOpu0tK7nClyfSsxDr0iXrrWr5cr8d/TMI9Vx2wDNbHlWpA781C5ycH GGaSAIwjbDUmAitEIvmDJA350fgflr+z8YF1qTDmW26GVuU7lclIueTsg9PA/7jcyvGe Cpexat5Gtxmf/vYaZmQaOiXd8TVmXMwV6+TFNW+ncza1UjqEEbsIYyeciAgFl4HZXGZF 2/b8YrE/4teNqwHvWknFWfnq2oih9UDfNAN2UHP8RC/dU1tvqKKywWwwVSS8/XfreOQT rmQO4rTFbmaFKR3XvBuSOqMXn2QxPXRdUaXh59A2ZMaWv6ZnWGB/ggeDobp6y+ZH1wcZ Q3aA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=mjT2C6lHzgGUiU0fI0OkORjd+PtI20uVj1BfMezw4nY=; b=ttdMxrknmO6f8VPxvXEL8e/62/2A3LqZjUzhF6C1s92FLNg75/ultklhUb9cCd8+KG WJkv+kIwQ395gT1P3WRcc874aV3X9yV0tI6Hrc1M9Hw+KTopSyqBSfZvAv61aVCz5OTH h9oJu/qUo/U+DMA3dCmq3Fn3r3GMC1kfIQPELI0czge7Vv41uuNYYtMNVOjyqv1EB0ku hDrvqEDh6bw/nMMXtupL20oQLWrW/pf//C5OfyiVkANbCZ/6O3CJpoYrcZEjgFO0lnpB Me+8/wL1OYlyS9vo7WHqiKq4w9yF0I7E4eTNqdN7YcvzB++lOUgRe6rSyFGx7KjoqNJW oHFA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@oracle.com header.s=corp-2018-07-02 header.b=VXSmsTdn; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=oracle.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h65-v6si2800471pfb.70.2018.09.27.11.14.39; Thu, 27 Sep 2018 11:14:56 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@oracle.com header.s=corp-2018-07-02 header.b=VXSmsTdn; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=oracle.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728301AbeI1Acx (ORCPT + 99 others); Thu, 27 Sep 2018 20:32:53 -0400 Received: from userp2120.oracle.com ([156.151.31.85]:37160 "EHLO userp2120.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727404AbeI1Acx (ORCPT ); Thu, 27 Sep 2018 20:32:53 -0400 Received: from pps.filterd (userp2120.oracle.com [127.0.0.1]) by userp2120.oracle.com (8.16.0.22/8.16.0.22) with SMTP id w8RHx3P2146854; Thu, 27 Sep 2018 18:12:42 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=subject : to : cc : references : from : message-id : date : mime-version : in-reply-to : content-type : content-transfer-encoding; s=corp-2018-07-02; bh=mjT2C6lHzgGUiU0fI0OkORjd+PtI20uVj1BfMezw4nY=; b=VXSmsTdnM5swEuIG8IC3n9v1L137RmFvzXAvvtAIxrYurA1ohsPQvfvtQ9E1e02dyZfW NOgbV5CE2N1h4aZtPXuqvPjSq5f2D8Jbv9uvd5AQjECTWMKCuuLJSDVTWsLJm8Nt6nYg kwTON7SJDvF57Qs7JsCblro/02beXKtS2f01AXBF+MW1SMrII4y7i2WGwpWcVfxZAinA lgYb2yL7CVkwkEj1k7U+4h5c7rlJTgtyximqR9v47ccTtDU2NpmLNmGr+amEVb7xnQ40 p0nYa9HOOPGT0SzIw8e2EkzK5ZVzal9Jgd4GliK83gqbgAEzAAsZDITTqCvsXDGdfoAr Rw== Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by userp2120.oracle.com with ESMTP id 2mnvtv2hwf-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 27 Sep 2018 18:12:42 +0000 Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by userv0022.oracle.com (8.14.4/8.14.4) with ESMTP id w8RICf3q017513 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 27 Sep 2018 18:12:41 GMT Received: from abhmp0010.oracle.com (abhmp0010.oracle.com [141.146.116.16]) by aserv0121.oracle.com (8.14.4/8.13.8) with ESMTP id w8RICeB1031756; Thu, 27 Sep 2018 18:12:41 GMT Received: from [10.132.91.175] (/10.132.91.175) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 27 Sep 2018 11:12:40 -0700 Subject: Re: [RFC 00/60] Coscheduling for Linux To: "=?UTF-8?Q?Jan_H._Sch=c3=b6nherr?=" , Ingo Molnar , Peter Zijlstra Cc: linux-kernel@vger.kernel.org References: <20180907214047.26914-1-jschoenh@amazon.de> <3336974a-38f7-41dd-25a7-df05e077444f@oracle.com> <90282ce3-dd14-73dc-fb9f-e78bb4042221@amazon.de> From: Subhra Mazumdar Message-ID: Date: Thu, 27 Sep 2018 11:12:33 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=9029 signatures=668707 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=727 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1809270167 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/24/2018 08:43 AM, Jan H. Schönherr wrote: > On 09/19/2018 11:53 PM, Subhra Mazumdar wrote: >> Can we have a more generic interface, like specifying a set of task ids >> to be co-scheduled with a particular level rather than tying this with >> cgroups? KVMs may not always run with cgroups and there might be other >> use cases where we might want co-scheduling that doesn't relate to >> cgroups. > Currently: no. > > At this point the implementation is tightly coupled to the cpu cgroup > controller. This *might* change, if the task group optimizations mentioned > in other parts of this e-mail thread are done, as I think, that it would > decouple the various mechanisms. > > That said, what if you were able to disable the "group-based fairness" > aspect of the cpu cgroup controller? Then you would be able to control > just the coscheduling aspects on their own. Would that satisfy the use > case you have in mind? > > Regards > Jan Yes that will suffice the use case. We wish to experiment at some point with co-scheduling of certain workers threads in DB parallel query and see if there is any benefit Thanks, Subhra