Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756646AbZLNOvL (ORCPT ); Mon, 14 Dec 2009 09:51:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756764AbZLNOvJ (ORCPT ); Mon, 14 Dec 2009 09:51:09 -0500 Received: from nlpi129.sbcis.sbc.com ([207.115.36.143]:36030 "EHLO nlpi129.prodigy.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756704AbZLNOvI (ORCPT ); Mon, 14 Dec 2009 09:51:08 -0500 Date: Mon, 14 Dec 2009 08:50:19 -0600 (CST) From: Christoph Lameter X-X-Sender: cl@router.home To: Con Kolivas cc: Willy Tarreau , Bartlomiej Zolnierkiewicz , linux-kernel@vger.kernel.org Subject: Re: BFS v0.311 CPU scheduler for 2.6.32 In-Reply-To: <200912121710.44216.kernel@kolivas.org> Message-ID: References: <200912111124.18118.kernel@kolivas.org> <200912121300.54803.kernel@kolivas.org> <20091212055459.GC32739@1wt.eu> <200912121710.44216.kernel@kolivas.org> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 815 Lines: 17 On Sat, 12 Dec 2009, Con Kolivas wrote: > That's the first meaningful reason I've heard for it. I may have to consider > it now. It still would be compile time limited so probably not quite what > you're hoping for. I don't have the time and energy to do and maintain the > whole plugsched crap for boottime selection all over again, and that adds > overhead which goes against one of my prime objectives. There was no such suggestion. It would help you a lot if you would be less uptight about things. If you are near Chicago: Want to get together for a beer or so? -- 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/