From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756070AbZHYTXJ (ORCPT ); Tue, 25 Aug 2009 15:23:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756057AbZHYTXI (ORCPT ); Tue, 25 Aug 2009 15:23:08 -0400 Received: from zrtps0kp.nortel.com ([47.140.192.56]:57140 "EHLO zrtps0kp.nortel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756018AbZHYTXH (ORCPT ); Tue, 25 Aug 2009 15:23:07 -0400 Message-ID: <4A943A00.9080609@nortel.com> Date: Tue, 25 Aug 2009 13:22:40 -0600 From: "Chris Friesen" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.1) Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Thunderbird/3.0b3 MIME-Version: 1.0 To: Peter Zijlstra CC: Christoph Lameter , Mike Galbraith , raz ben yehuda , riel@redhat.com, mingo@elte.hu, andrew motron , wiseman@macs.biu.ac.il, lkml , linux-rt-users@vger.kernel.org Subject: Re: RFC: THE OFFLINE SCHEDULER References: <1250983671.5688.21.camel@raz> <1251004897.7043.70.camel@marge.simson.net> <1251018551.3810.35.camel@raz> <1251012621.14003.71.camel@marge.simson.net> <1251025557.3810.65.camel@raz> <1251021133.14003.172.camel@marge.simson.net> <1251222993.7023.53.camel@marge.simson.net> <1251227322.7538.1172.camel@twins> In-Reply-To: <1251227322.7538.1172.camel@twins> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 25 Aug 2009 19:22:54.0417 (UTC) FILETIME=[71EF5C10:01CA25B9] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 08/25/2009 01:08 PM, Peter Zijlstra wrote: > Christoph, stop being silly, this offline scheduler thing won't happen, > full stop. > > Its not a maintainable solution, it doesn't integrate with existing > kernel infrastructure, and its plain ugly. > > If you want something work within Linux, don't build kernels in kernels > or other such ugly hacks. Is it the whole concept of isolating one or more cpus from all normal kernel tasks that you don't like, or just this particular implementation? I ask because I know of at least one project that would have used this capability had it been available. As it stands they have to live with the usual kernel threads running on the cpu that they're trying to dedicate to their app. Chris