From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266868AbUGVRyC (ORCPT ); Thu, 22 Jul 2004 13:54:02 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266864AbUGVRxp (ORCPT ); Thu, 22 Jul 2004 13:53:45 -0400 Received: from mx1.elte.hu ([157.181.1.137]:49864 "EHLO mx1.elte.hu") by vger.kernel.org with ESMTP id S266868AbUGVRxh (ORCPT ); Thu, 22 Jul 2004 13:53:37 -0400 Date: Thu, 22 Jul 2004 19:54:59 +0200 From: Ingo Molnar To: Dimitri Sivanich Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC] Patch for isolated scheduler domains Message-ID: <20040722175459.GA30059@elte.hu> References: <20040722164126.GB13189@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040722164126.GB13189@sgi.com> User-Agent: Mutt/1.4.1i X-ELTE-SpamVersion: MailScanner 4.31.6-itk1 (ELTE 1.2) SpamAssassin 2.63 ClamAV 0.73 X-ELTE-VirusStatus: clean X-ELTE-SpamCheck: no X-ELTE-SpamCheck-Details: score=-0.908, required 5.9, autolearn=not spam, BAYES_10 -0.91 X-ELTE-SpamLevel: X-ELTE-SpamScore: 0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org * Dimitri Sivanich wrote: > I'm interested in implementing something I'll call isolated sched > domains for single cpus (to minimize the latencies involved when doing > things like load balancing on certain select cpus) on IA64. > > Below I've included an initial patch to illustrate what I'd like to > do. I know there's been mention of 'platform specific work' in the > area of sched domains. This patch only addresses IA64, but could be > made generic as well. The code is derived directly from the current > default arch_init_sched_domains code. it looks good to me - and i'd suggest to put it into sched.c. Every architecture benefits from the ability to define isolated CPUs. One minor nit wrt. this line: + cpu_sd->flags &= ~(SD_BALANCE_NEWIDLE | SD_BALANCE_EXEC | + SD_BALANCE_CLONE); /* Probably redundant */ i'd suggest to set it to 0. You dont want WAKE_AFFINE nor WAKE_BALANCE to move your tasks out of the isolated domain. > - Assuming boot time configuration is appropriate ('isolcpus=' in my example), > is allowing boot time configuration of only completely isolated cpus > focusing too narrowly on this one concept, or should a boot time > configuration allow for a broader array of configurations, or would other > types of sched domain configurations be addressed separately? i'd prefer to go with this simple solution and wait for actual usage patterns to materialize. If it becomes popular we can define a syscall to configure the domain hierarchy (maybe even the parameters) runtime. Ingo