Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756734AbYKKP0i (ORCPT ); Tue, 11 Nov 2008 10:26:38 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756160AbYKKP0a (ORCPT ); Tue, 11 Nov 2008 10:26:30 -0500 Received: from viefep20-int.chello.at ([62.179.121.40]:38684 "EHLO viefep20-int.chello.at" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756016AbYKKP03 (ORCPT ); Tue, 11 Nov 2008 10:26:29 -0500 X-SourceIP: 213.46.9.244 Subject: Re: [RFC PATCH v3 3/5] sched: nominate preferred wakeup cpu From: Peter Zijlstra To: vatsa@in.ibm.com Cc: Gregory Haskins , Vaidyanathan Srinivasan , Linux Kernel , Suresh B Siddha , Venkatesh Pallipadi , Ingo Molnar , Dipankar Sarma , Balbir Singh , Gautham R Shenoy , Andi Kleen , David Collier-Brown , Tim Connors , Max Krasnyansky In-Reply-To: <20081111152126.GF3593@linux.vnet.ibm.com> References: <20081110181526.562.69941.stgit@drishya.in.ibm.com> <20081110183326.562.37718.stgit@drishya.in.ibm.com> <1226411019.7685.1767.camel@twins> <491991BE.9080405@gmail.com> <20081111152126.GF3593@linux.vnet.ibm.com> Content-Type: text/plain Date: Tue, 11 Nov 2008 16:26:14 +0100 Message-Id: <1226417174.7685.1898.camel@twins> Mime-Version: 1.0 X-Mailer: Evolution 2.24.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1363 Lines: 28 On Tue, 2008-11-11 at 20:51 +0530, Srivatsa Vaddagiri wrote: > On Tue, Nov 11, 2008 at 09:07:58AM -0500, Gregory Haskins wrote: > > > Would it make sense to place the preferred_wakeup_cpu stuff in the > > > root_domain structure we already have? > > > > > > > From the description, this is exactly what the root-domains were created > > to solve. > > > > Vaidyanathan, just declare your object in "struct root_domain" and > > initialize it in init_rootdomain() in kernel/sched.c, and then access it > > via rq->rd to take advantage of this infrastructure. It will > > automatically follow any partitioning that happens to be configured. > > If I understand correctly, we may want to have more than one preferred > cpu in a given sched domain, taking into account node topology i.e if a > given sched domain encompasses two nodes, then we may like to designate > 2 preferred wakeup_cpu's, one per node. If that is the case, then > root_domain may not be of use here? Agreed, in which case this sched_domain_attr stuff might work out better - but I'm not sure I fully get that.. will stare at that a bit more. -- 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/