Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752845Ab0K3ONi (ORCPT ); Tue, 30 Nov 2010 09:13:38 -0500 Received: from mx3.mail.elte.hu ([157.181.1.138]:35238 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752471Ab0K3ONh (ORCPT ); Tue, 30 Nov 2010 09:13:37 -0500 Date: Tue, 30 Nov 2010 15:13:20 +0100 From: Ingo Molnar To: Mike Galbraith Cc: Paul Turner , Peter Zijlstra , Linus Torvalds , Oleg Nesterov , LKML Subject: Re: [PATCH v4] sched: automated per session task groups Message-ID: <20101130141320.GA22588@elte.hu> References: <20101128201851.GA20555@elte.hu> <1291031593.32004.19.camel@laptop> <1291052268.32004.171.camel@laptop> <1291057565.20709.2.camel@marge.simson.net> <20101129192033.GA18372@elte.hu> <1291090455.7550.7.camel@marge.simson.net> <1291123083.28239.18.camel@marge.simson.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1291123083.28239.18.camel@marge.simson.net> User-Agent: Mutt/1.5.20 (2009-08-17) X-ELTE-SpamScore: -1.3 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.3 required=5.9 tests=BAYES_00,FUZZY_VPILL autolearn=no SpamAssassin version=3.2.5 0.7 FUZZY_VPILL BODY: Attempt to obfuscate words in spam -2.0 BAYES_00 BODY: Bayesian 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: 2854 Lines: 86 * Mike Galbraith wrote: > On Mon, 2010-11-29 at 20:23 -0800, Paul Turner wrote: > > > I've left some machines running tip + fix above + autogroup to see if > > anything else emerges. Hasn't crashed yet, I'll leave it going > > overnight. > > Thanks. Below is the hopefully final version against tip. The last I > sent contained a couple remnants. Note, I removed this chunk: > kernel/sched_debug.c | 29 ++-- > Index: linux-2.6/kernel/sched_debug.c > =================================================================== > --- linux-2.6.orig/kernel/sched_debug.c > +++ linux-2.6/kernel/sched_debug.c > @@ -87,6 +87,20 @@ static void print_cfs_group_stats(struct > } > #endif > > +#if defined(CONFIG_CGROUP_SCHED) && \ > + (defined(CONFIG_FAIR_GROUP_SCHED) || defined(CONFIG_RT_GROUP_SCHED)) > +static void task_group_path(struct task_group *tg, char *buf, int buflen) > +{ > + /* may be NULL if the underlying cgroup isn't fully-created yet */ > + if (!tg->css.cgroup) { > + if (!autogroup_path(tg, buf, buflen)) > + buf[0] = '\0'; > + return; > + } > + cgroup_path(tg->css.cgroup, buf, buflen); > +} > +#endif > + > static void > print_task(struct seq_file *m, struct rq *rq, struct task_struct *p) > { > @@ -115,7 +129,7 @@ print_task(struct seq_file *m, struct rq > char path[64]; > > rcu_read_lock(); > - cgroup_path(task_group(p)->css.cgroup, path, sizeof(path)); > + task_group_path(task_group(p), path, sizeof(path)); > rcu_read_unlock(); > SEQ_printf(m, " %s", path); > } > @@ -147,19 +161,6 @@ static void print_rq(struct seq_file *m, > read_unlock_irqrestore(&tasklist_lock, flags); > } > > -#if defined(CONFIG_CGROUP_SCHED) && \ > - (defined(CONFIG_FAIR_GROUP_SCHED) || defined(CONFIG_RT_GROUP_SCHED)) > -static void task_group_path(struct task_group *tg, char *buf, int buflen) > -{ > - /* may be NULL if the underlying cgroup isn't fully-created yet */ > - if (!tg->css.cgroup) { > - buf[0] = '\0'; > - return; > - } > - cgroup_path(tg->css.cgroup, buf, buflen); > -} > -#endif > - > void print_cfs_rq(struct seq_file *m, int cpu, struct cfs_rq *cfs_rq) > { > s64 MIN_vruntime = -1, min_vruntime, max_vruntime = -1, Because it didn't build (for obvious reasons - the CONFIG conditions dont match up), but more importantly it's quite ugly. Some existing 'path' variables are 64 byte, some are 128 byte - so there's pre-existing damage - i removed it all. Could we do this debugging code in a bit saner way please? (as a delta patch on top of the -tip that i'll push out in the next hour or so.) 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/