Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758729AbZLKPEn (ORCPT ); Fri, 11 Dec 2009 10:04:43 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754959AbZLKPEj (ORCPT ); Fri, 11 Dec 2009 10:04:39 -0500 Received: from home.kolivas.org ([59.167.196.135]:59962 "EHLO home.kolivas.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754207AbZLKPEi (ORCPT ); Fri, 11 Dec 2009 10:04:38 -0500 From: Con Kolivas To: Christoph Lameter Subject: Re: BFS v0.311 CPU scheduler for 2.6.32 Date: Sat, 12 Dec 2009 02:04:51 +1100 User-Agent: KMail/1.12.1 (Linux/2.6.32-ck1; KDE/4.3.2; x86_64; ; ) Cc: linux-kernel@vger.kernel.org References: <200912111124.18118.kernel@kolivas.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200912120204.51547.kernel@kolivas.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 671 Lines: 18 On Sat, 12 Dec 2009 01:10:39 Christoph Lameter wrote: > Could you make the scheduler build time configurable instead of replacing > the existing one? Embedded folks in particular may love a low footprint > scheduler. > It's not a bad idea, but the kernel still needs to be patched either way. To get BFS they'd need to patch the kernel. If they didn't want BFS, they wouldn't patch it in the first place. Thanks, -- -ck -- 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/