Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262434AbTEVBQH (ORCPT ); Wed, 21 May 2003 21:16:07 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262439AbTEVBQH (ORCPT ); Wed, 21 May 2003 21:16:07 -0400 Received: from franka.aracnet.com ([216.99.193.44]:62102 "EHLO franka.aracnet.com") by vger.kernel.org with ESMTP id S262434AbTEVBQG (ORCPT ); Wed, 21 May 2003 21:16:06 -0400 Date: Wed, 21 May 2003 18:28:56 -0700 From: "Martin J. Bligh" To: Gerrit Huizenga , "Nakajima, Jun" cc: jamesclv@us.ibm.com, haveblue@us.ibm.com, pbadari@us.ibm.com, linux-kernel@vger.kernel.org, johnstul@us.ibm.com, mannthey@us.ibm.com Subject: Re: userspace irq balancer Message-ID: <58830000.1053566935@[10.10.2.4]> In-Reply-To: References: X-Mailer: Mulberry/2.2.1 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 907 Lines: 21 > Yeah, I suppose this userland policy change means we should pull > the scheduler policy decisions out of the kernel and write user level > HT, NUMA, SMP and UP schedulers. Also, the IO schedulers should > probably be pulled out - I'm sure AS and CFQ and linus_scheduler > could be user land policies, as well as the elevator. Memory > placement and swapping policies, too. > > Oh, wait, some people actually do this - they call it, what, > Workload Management or some such thing. But I don't know any > style of workload management that leaves *no* default, semi-sane > policy in the kernel. I think the word you're groping for here is "microkernel". M. - 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/