From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751534AbdBMF3t (ORCPT ); Mon, 13 Feb 2017 00:29:49 -0500 Received: from mout.gmx.net ([212.227.17.22]:61932 "EHLO mout.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750711AbdBMF3s (ORCPT ); Mon, 13 Feb 2017 00:29:48 -0500 Message-ID: <1486963730.5912.89.camel@gmx.de> Subject: Re: [PATCHSET for-4.11] cgroup: implement cgroup v2 thread mode From: Mike Galbraith To: Paul Turner , Peter Zijlstra Cc: Tejun Heo , "lizefan@huawei.com" , Johannes Weiner , Ingo Molnar , Andy Lutomirski , cgroups , LKML , kernel-team , "lvenanci@redhat.com" , Linus Torvalds , Andrew Morton Date: Mon, 13 Feb 2017 06:28:50 +0100 In-Reply-To: References: <20170202200632.13992-1-tj@kernel.org> <20170209144704.GD6515@twins.programming.kicks-ass.net> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.16.5 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:BE/yYo981rJvNjoi6+y7TMnbFb85mB8kAF034MaGd4cJoOw2mux NNjjhZwqtSUAB07qcqXf+QJaXB9D3Y76r9Dq/tDa1xnadlLSjfZJIlCMVdWk1zYyO8tN+Eg e+Iphdlbn14vu7NhOXM97//E+8mbE6CnIfLA5GYxhWnI9b8JiD6JFo7x9w81p3bNp/+new7 FJQY3hKhVmPcpnfnIzDOA== X-UI-Out-Filterresults: notjunk:1;V01:K0:+b6U66+3KUE=:MY6lkQCYbHfs57caUzpeWM DmlteYxA39hF3DKRU6xWoNPc62qMpUcIvqupZFDoeaZjllurAKpsosfikCX/+Yaw12uIHHw6I 7W3ke6d5bXmfNftuqOflVGVfXcvWjSHGKkHSX+o9CdEffPgLOUkIkfarIhP3oBi545fijmguA XGL5BbQvHfKocPh8ZVezFWFgAHA8JytqjvGnjuRSYEsprT6hSAHb1uU8BxkeyrsV/UQsUhxwb oKOO5EyNtRf1DpHTUZhLDiUtNbGj+efTiBgvfD97UvH4nT63isceVOqwitFa9MahcsiGuUiWL BDLFoN94xu5eL5n3WatKAjSu3sTIiKeVRDHSAwKmBMibR44YPDuhJ4e+dDrRdF9H0iSzS0pfK LM+gvrVzGpKwFyQ9dLBmN+JoLeZwdWlIsSJ0cFUX98quEo/O/U/DJcYsD6kxuqI0ea55XXsB0 ZIIPetalt9D63SZrHldar5h4tjgatp7/hJ50UNG27SX3NWHvVsGj3jm/ckb2G4DqobjZvqgCI JHRSdd4lexrkM1AsgDUQUyLh/MY/w/1q02KWMvSCHVNGbz5SlWXRcRe1QkqgVLaOTLprg318c yvylzXSxPyzooyx8kh8YD3aDm/V1Tn5G+JoPmIMRZB9s/z6bdD6elLCW/Kljsv5dv23eISKr5 KVBMGI80adUGtGaNwSBePMTnWxWsZthENVPR7ASndGy/NcYeZ/KJHF+h6Dr1tHIfA0JyM2Ff1 YWiqeU2bnCbjaJ/U/6DzZbCI0+U7gD4WrQYspog/5cGWUcPyOOHnWEvDwM8U1AfiCKXrh1TXR SOf13FMgNn84wKJjp1SjIAesP692CYVx8NT5ZXw4z9iQ8OtokAyB8eywNP9/ywLf0qIH+mvuu UT7NvTWJvwYaApeQvHo0Pzdk9xEVPoS0i680wfooX0B0+pyIM68TRVcFaVOnb0TQov/eH9UGN /qWMgQ/GeZIBLeHMvbgTfoS/sieNf7Hq+J2rN9uD7xnM4zmd8FQ2rQ1vtwYX5BSPZssHSLoWv E7lPmqNlWNwCdq/Wm4b8PFw= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 2017-02-12 at 13:16 -0800, Paul Turner wrote: > > > On Thursday, February 9, 2017, Peter Zijlstra wrote: > > On Thu, Feb 09, 2017 at 05:07:16AM -0800, Paul Turner wrote: > > > The only case that this does not support vs ".threads" would be some > > > hybrid where we co-mingle threads from different processes (with the > > > processes belonging to the same node in the hierarchy). I'm not aware > > > of any usage that looks like this. > > > > If I understand you right; this is a fairly common thing with RT where > > we would stuff all the !rt threads of the various processes in a 'misc' > > bucket. > > > > Similarly, it happens that we stuff the various rt threads of processes > > in a specific (shared) 'rt' bucket. > > > > So I would certainly not like to exclude that setup. > > > > Unless you're using rt groups I'm not sure this one really changes. > Whether the "misc" threads exist at the parent level or one below > should not matter. (with exclusive cpusets, a mask can exist at one and only one location)