Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932678Ab1EMJFt (ORCPT ); Fri, 13 May 2011 05:05:49 -0400 Received: from mx2.mail.elte.hu ([157.181.151.9]:48567 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932380Ab1EMJFr (ORCPT ); Fri, 13 May 2011 05:05:47 -0400 Date: Fri, 13 May 2011 11:05:37 +0200 From: Ingo Molnar To: Peter Zijlstra Cc: Mike Galbraith , Yong Zhang , Carl-Johan Kjellander , linux-kernel@vger.kernel.org Subject: Re: Sched_autogroup and niced processes Message-ID: <20110513090537.GH13647@elte.hu> References: <1305273950.15080.7.camel@marge.simson.net> <20110513082250.GB13647@elte.hu> <1305276066.2561.1.camel@twins> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1305276066.2561.1.camel@twins> User-Agent: Mutt/1.5.20 (2009-08-17) X-ELTE-SpamScore: -2.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.0 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.3.1 -2.0 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1511 Lines: 49 * Peter Zijlstra wrote: > On Fri, 2011-05-13 at 10:22 +0200, Ingo Molnar wrote: > > * Mike Galbraith wrote: > > > > > > > time make -j12 # with seti@home running > > > > > real 4m16.753s > > > > > user 10m33.770s > > > > > sys 1m39.710s > > > > > > > > > > time make -j12 # without seti@home running > > > > > real 2m12.480s > > > > > user 10m11.580s > > > > > sys 1m39.980s > > > > I think the practical question here is to make seti@home run more idle. > > > > Are there some magic cgroup commands you could recommend for that? > > Yong already did. Oh, indeed, stupid me. This teaches me to not stop at the first paragraph of interesting looking emails ;-) Could we somehow automate this: > echo 19 > /proc/'pid of seti@home'/autogroup and split off nice 19 tasks into separate groups and lower the group's priority? That would fit into the general principle of auto-sched as well. Another thing we could do is to lower the priority of a cgroup if it *only* runs reniced tasks. I.e. track the 'maximum priority' of cgroups and propagate that to their weight. This way renicing within cgroups will be more powerful and people do not have to muck with cgroup details. Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/