From: Con Kolivas <kernel@kolivas.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>,
Peter Williams <pwil3058@bigpond.net.au>,
William Lee Irwin III <wli@holomorphy.com>,
Alexander Nyberg <alexn@dsv.su.se>,
Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: [PATCH][plugsched 0/28] Pluggable cpu scheduler framework
Date: Mon, 01 Nov 2004 10:37:41 +1100 [thread overview]
Message-ID: <41857745.6020808@kolivas.org> (raw)
In-Reply-To: <20041031233313.GB6909@elf.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
Pavel Machek wrote:
> Hi!
>
>
>>This code was designed to touch the least number of files, be completely
>>arch-independant, and allow extra schedulers to be coded in by only
>>touching Kconfig, scheduler.c and scheduler.h. It should incur no
>>overhead when run and will allow you to compile in only the scheduler(s)
>>you desire. This allows, for example, embedded hardware to have a tiny
>>new scheduler that takes up minimal code space.
>
>
> You are changing
>
> some_functions()
>
> into
>
> something->function()
>
> no? I do not think that is 0 overhead...
Indeed, and I am performing microbenchmarks to see what measurable
overhead there is and so far any difference is lost in noise.
Cheers,
Con
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2004-10-31 23:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-30 14:32 [PATCH][plugsched 0/28] Pluggable cpu scheduler framework Con Kolivas
2004-10-31 23:33 ` Pavel Machek
2004-10-31 23:37 ` Con Kolivas [this message]
2004-11-01 1:42 ` William Lee Irwin III
2004-11-01 11:41 ` Ingo Molnar
2004-11-01 13:08 ` Kasper Sandberg
2004-11-01 13:32 ` Con Kolivas
2004-11-01 14:23 ` Nick Piggin
2004-11-01 17:54 ` Jesse Barnes
2004-11-02 21:28 ` Matthias Urlichs
2004-11-02 22:30 ` Peter Chubb
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=41857745.6020808@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@osdl.org \
--cc=alexn@dsv.su.se \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=pavel@ucw.cz \
--cc=pwil3058@bigpond.net.au \
--cc=wli@holomorphy.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox