Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757378AbcK2NsU (ORCPT ); Tue, 29 Nov 2016 08:48:20 -0500 Received: from mout.gmx.net ([212.227.17.21]:64646 "EHLO mout.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755269AbcK2Nqe (ORCPT ); Tue, 29 Nov 2016 08:46:34 -0500 Message-ID: <1480427175.10353.77.camel@gmx.de> Subject: Re: RFC: documentation of the autogroup feature From: Mike Galbraith To: mtk.manpages@gmail.com Cc: Peter Zijlstra , Ingo Molnar , linux-man , lkml , Thomas Gleixner Date: Tue, 29 Nov 2016 14:46:15 +0100 In-Reply-To: References: <41d802dc-873a-ff02-17ff-93ce50f3e925@gmail.com> <1479901185.4306.38.camel@gmx.de> <327586fa-4672-d070-0ded-850654586273@gmail.com> <1479915229.4306.106.camel@gmx.de> <8614679c-b1d3-3b35-193d-2ab6eac45aff@gmail.com> <1480297574.9163.76.camel@gmx.de> <1127218a-dd9b-71a8-845d-3a83969632fc@gmail.com> Content-Type: text/plain; charset="iso-2022-jp" X-Mailer: Evolution 3.16.5 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:6raBzsS3jHBYREhoGc7aCtNzYI3SliS0Gduuaq7H5VqjHVW8FOn WR0jmv0pQs5FK3c4P0/rbizeO5JE9uL4XEpclty5fc0Xrw4eF1XCZJHCkALgCwkgzAy04f3 7JXZMDJTef0zO5O89rUd4gjwTwXVtPbN45spHAHAQ2Adp62V5ZrHG4y3Qx13KhOYjOQDr4k tQCz2eKyxJa4JyEekzSNA== X-UI-Out-Filterresults: notjunk:1;V01:K0:5D/Lej6KKHg=:LFuUinckeDawZ+4u4EmoNH NKzOLd0EYwettfsNs2i2PtDgOXXpMsxQWCkubWYU77BaXsLhx88OPxDMNxepR+NgtDThoFfEi hEDsnCARhODUOEuP2AdKa4SUqE+atk9lOc1K7UStDMA7wcRwzeKuusROu0zls50h3K6QzPKzn V1WfqUlOgfHICrS4/dbgXWvaEqU+oWXZ61GQgn0fLAiZBrTf9HrPLqSw4RTtn2PN5F52fOmW0 KyF/uyBs2/go0Wn4fWM0xp2b1mtI3rDK6CvrYaioaLCjquHS5f2ZdGlaqrpjGIZKcopFY0rmE FAoKvac/hvwsloSnCK+5OgtH5qUu3xHSBAzhlFLhBHpTws4eEiaIbg4f/szUho/eaq3XUBd8x 8kHV8JE/Tx98AQ0u/uLjeJhiioTHOn2MeY3Qs8JmqYVH63JdBe5LSI/g+7y5j3ZcsraTyD2jI 3k39FaaJCygssSX8gbX/Fmlwr+G5TDjx996ltQmJuiT00+wDSfXFJ5r/F20fvRQ6AIAW1LoDI AFYVl793kRmBDVgt0rRJQFquQg37pLHWGiHmM861m47OndziE46Tey49uuwQOLTmOX6eNJ+kB YAAUHUgy4f1cJYtADmhQBdR7BprWlhqh8G8Qz0HF4ixQct5T1Sy7lQGdnXQgKi3rY3AlPERtB pKiwRUxqpvnU0S/lbmedWnE7vWq6AYaYddvcOkKOvJWUiFFW4M1VMI/21qyeh9NUS+9ozurBe fmxi2IA+KDPNDkgauGBo3E7A9RVbZl4g/nTDEY2tHRyMRsFNu4NbR/e3NVRKr8t/YzZqANq6a eU66rXh Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1910 Lines: 39 On Tue, 2016-11-29 at 10:10 +0100, Michael Kerrisk (man-pages) wrote: > Let's try and go further. How's this: > > When scheduling non-real-time processes (i.e., those scheduled > under the SCHED_OTHER, SCHED_BATCH, and SCHED_IDLE policies), the > CFS scheduler employs a technique known as "group scheduling", if > the kernel was configured with the CONFIG_FAIR_GROUP_SCHED option > (which is typical). > > Under group scheduling, threads are scheduled in "task groups". > Task groups have a hierarchical relationship, rooted under the > initial task group on the system, known as the "root task group". > Task groups are formed in the following circumstances: > > * All of the threads in a CPU cgroup form a task group. The par‐ > ent of this task group is the task group of the corresponding > parent cgroup. > > * If autogrouping is enabled, then all of the threads that are > (implicitly) placed in an autogroup (i.e., the same session, as > created by setsid(2)) form a task group. Each new autogroup is > thus a separate task group. The root task group is the parent > of all such autogroups. > > * If autogrouping is enabled, then the root task group consists > of all processes in the root CPU cgroup that were not otherwise > implicitly placed into a new autogroup. > > * If autogrouping is disabled, then the root task group consists > of all processes in the root CPU cgroup. > > * If group scheduling was disabled (i.e., the kernel was config‐ > ured without CONFIG_FAIR_GROUP_SCHED), then all of the pro‐ > cesses on the system are notionally placed in a single task > group. Notionally works for me. -Mike