From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Oliver Xymoron <oxymoron@waste.org>
Cc: Daniel Phillips <phillips@bonn-fries.net>,
Karim Yaghmour <karim@opersys.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Adeos nanokernel for Linux kernel
Date: Wed, 5 Jun 2002 11:41:49 +0200 [thread overview]
Message-ID: <20020605114149.R681@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <E17FQPj-0001Rr-00@starship> <Pine.LNX.4.44.0206042132450.2614-100000@waste.org>
On Tue, Jun 04, 2002 at 09:40:25PM -0500, Oliver Xymoron wrote:
> Just bear in mind that it's next to impossible to avoid throwing the baby
> out with the bathwater here. Ok, so you've got an RT kernel playing your
> MP3 alongside your UNIX system - how do you control it? How do you switch
> tracks? All the latency that you were struggling with in the player is
> still there in the user interface.
What stops you from providing non-sleeping messaging scheme
primitives in Adeos?
Adeos -> Client: Use virtual interrupt vectors and use your ipipe
for it.
Client -> Adeos: Provide Emission of this virtual interrupts in
Adeos.
Also some kind of shared memory and a "commit" for this memory is
needed in Adeos. Allocation of this memory should be up to the
requester of this memory, so Adeos doesn't need to wait for it
and neither does the RTOS on the other end.
With that primitives (plus some atomic magic ;-)) you can build
non-sleeping messaging.
Karim, is sth. like this planned or is it senseless?
Regards
Ingo Oeser
--
Science is what we can tell a computer. Art is everything else. --- D.E.Knuth
next prev parent reply other threads:[~2002-06-05 10:33 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-03 8:35 [ANNOUNCE] Adeos nanokernel for Linux kernel Karim Yaghmour
2002-06-03 8:46 ` Erik Andersen
2002-06-03 8:56 ` Alessandro Rubini
2002-06-03 9:14 ` Karim Yaghmour
2002-06-03 9:52 ` Erik Andersen
2002-06-03 10:05 ` Alessandro Rubini
2002-06-03 10:12 ` Karim Yaghmour
2002-06-03 10:33 ` Erik Andersen
2002-06-03 10:38 ` Karim Yaghmour
2002-06-03 11:05 ` Daniel Phillips
2002-06-03 9:26 ` Daniel Phillips
2002-06-04 19:29 ` Oliver Xymoron
2002-06-05 2:20 ` Daniel Phillips
2002-06-05 2:40 ` Oliver Xymoron
2002-06-05 2:57 ` Daniel Phillips
2002-06-05 13:51 ` Oliver Xymoron
2002-06-05 14:25 ` Daniel Phillips
2002-06-05 15:37 ` Oliver Xymoron
2002-06-05 17:32 ` Daniel Phillips
2002-06-05 18:06 ` Mark Mielke
2002-06-05 18:26 ` Daniel Phillips
2002-06-05 19:13 ` Oliver Xymoron
2002-06-05 19:40 ` Daniel Phillips
2002-06-05 20:51 ` Mark Mielke
2002-06-05 21:45 ` Daniel Phillips
2002-06-05 21:22 ` Oliver Xymoron
2002-06-05 21:55 ` Daniel Phillips
2002-06-06 8:52 ` Peter Wächtler
2002-06-06 10:58 ` Daniel Phillips
2002-06-06 14:03 ` Peter Wächtler
2002-06-06 16:53 ` Daniel Phillips
2002-06-05 20:48 ` Mark Mielke
2002-06-06 8:34 ` Peter Wächtler
2002-06-08 13:50 ` john slee
2002-06-08 13:59 ` Thunder from the hill
2002-06-06 21:21 ` Pavel Machek
2002-06-07 1:35 ` Mark Mielke
2002-06-07 2:42 ` Daniel Phillips
2002-06-07 2:48 ` Mark Mielke
2002-06-07 10:32 ` Daniel Phillips
2002-06-07 21:35 ` Pavel Machek
2002-06-05 9:41 ` Ingo Oeser [this message]
2002-06-05 18:20 ` Karim Yaghmour
2002-06-05 3:56 ` J Sloan
2002-06-05 4:08 ` Daniel Phillips
2002-06-05 7:28 ` Eric W. Biederman
2002-06-05 11:15 ` Peter Wächtler
2002-06-05 12:56 ` Daniel Phillips
2002-06-05 11:11 ` Peter Wächtler
2002-06-05 16:55 ` Rob Landley
2002-06-04 16:10 ` Pavel Machek
2002-06-04 19:59 ` Karim Yaghmour
2002-06-04 21:53 ` Karim Yaghmour
2002-06-04 23:06 ` Alan Cox
2002-06-05 4:00 ` Daniel Phillips
-- strict thread matches above, loose matches on Subject: below --
2002-06-05 9:24 Martin.Knoblauch
2002-06-05 19:01 Paul Zimmerman
2002-06-05 19:11 ` Karim Yaghmour
2002-06-05 20:17 ` Daniel Phillips
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=20020605114149.R681@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oxymoron@waste.org \
--cc=phillips@bonn-fries.net \
/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