From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: BFS v0.311 CPU scheduler for 2.6.32
Date: Fri, 11 Dec 2009 17:06:12 -0500 [thread overview]
Message-ID: <hfufos$1uj$1@ger.gmane.org> (raw)
In-Reply-To: <200912120204.51547.kernel@kolivas.org>
Con Kolivas wrote:
> 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.
>
The advantage would be that the same kernel source could then be built into a
custom version with only the config changed.Since building with various configs
is hardly unusual it would save some carrying of multiple sources, for those who
build for several uses already.
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
prev parent reply other threads:[~2009-12-11 22:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 0:24 BFS v0.311 CPU scheduler for 2.6.32 Con Kolivas
2009-12-11 10:29 ` Mike Galbraith
2009-12-11 14:10 ` Christoph Lameter
2009-12-11 15:04 ` Con Kolivas
2009-12-11 15:12 ` Christoph Lameter
2009-12-11 22:37 ` Con Kolivas
2009-12-12 0:55 ` Bartlomiej Zolnierkiewicz
2009-12-12 2:00 ` Con Kolivas
2009-12-12 3:22 ` Bartlomiej Zolnierkiewicz
2009-12-12 5:54 ` Willy Tarreau
2009-12-12 6:10 ` Con Kolivas
2009-12-12 6:14 ` Willy Tarreau
2009-12-14 14:16 ` Bartlomiej Zolnierkiewicz
2009-12-18 15:44 ` BFS v0.312 configurable " Con Kolivas
2009-12-14 14:50 ` BFS v0.311 " Christoph Lameter
2009-12-15 0:56 ` Con Kolivas
2009-12-12 7:59 ` Mike Galbraith
2009-12-20 4:46 ` Bill Davidsen
2009-12-11 22:06 ` Bill Davidsen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='hfufos$1uj$1@ger.gmane.org' \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.