From: Karim Yaghmour <karim@opersys.com>
To: Dan Aloni <da-x@gmx.net>
Cc: Nuno Silva <nuno.silva@vgertech.com>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Cooperative Linux
Date: Mon, 26 Jan 2004 00:01:25 -0500 [thread overview]
Message-ID: <40149F25.1040209@opersys.com> (raw)
In-Reply-To: <20040126042631.GA401@callisto.yi.org>
Dan Aloni wrote:
> I can't say exactly when, but several people volunteered to work on this.
BTW, I've been looking at the code. Many of the tricks done for forcing
NT to share resources with Linux should be unnecessary for a Linux setup.
Also, the code apparently assumes only two OSes. You probably want to
check the detailed discussion I had written some time ago about how to
easily obtain an SMP cluster with Linux (N instances on separate CPUs
with very few code modifications required):
http://www.opersys.com/adeos/dox/practical-smp-clusters/practical-smp-clusters.html
Some of the code you've already written can be used as-is to this end.
The nanokernel side still needs some extending, but you've brought things
one step closer to completion.
On a UP system, instead of running just 2 instances, you can load a
nanokernel in a fixed RAM region and remap it in every instance's
virtual memory. You can then use a slightly modified kexec to start
independent images in different RAM regions. I had discussed this
with Eric at the last OLS and he was interested. The added
advantage with Adeos is that you could then share a single interrupt
pipeline among all OSes, and have different OSes manage different hardware
components. Of course, if you add the PCI allocation code I cover in the
above paper, you can then have things like two kernels independently
managing, for example, two seperate sets of ethernet card and SCSI disk.
There's some pretty cool stuff to be done here, away from the simple
virtual devices. You could also have a virtual ethernet layer which is
shared by all OS images, and then have a private network between all
OS instances. With Adeos, you can also have one kernel take care of
all hard-rt operations and another kernel take care of the soft-rt
operations. All of it is fairly hardware independent.
Karim
--
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 1-866-677-4546
next prev parent reply other threads:[~2004-01-26 4:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-25 19:35 [ANNOUNCE] Cooperative Linux Dan Aloni
2004-01-25 20:01 ` Karim Yaghmour
2004-01-26 3:40 ` Nuno Silva
2004-01-26 3:57 ` JustFillBug
2004-01-26 4:59 ` Ben Pfaff
2004-01-26 9:19 ` Christoph Hellwig
2004-01-26 17:00 ` Ben Pfaff
2004-01-26 19:44 ` Christoph Hellwig
2004-01-26 20:04 ` Omkhar Arasaratnam
2004-01-26 5:04 ` Karim Yaghmour
2004-01-26 5:06 ` Nuno Silva
2004-01-26 6:36 ` Karim Yaghmour
2004-01-26 11:35 ` Rik van Riel
2004-01-26 15:20 ` Karim Yaghmour
2004-01-26 11:32 ` Rik van Riel
2004-01-27 0:20 ` David Schwartz
2004-01-26 4:26 ` Dan Aloni
2004-01-26 5:01 ` Karim Yaghmour [this message]
2004-01-26 7:23 ` Dan Aloni
-- strict thread matches above, loose matches on Subject: below --
2004-01-29 5:57 Paul Zimmerman
2004-01-29 9:10 ` Dan Aloni
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=40149F25.1040209@opersys.com \
--to=karim@opersys.com \
--cc=da-x@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.silva@vgertech.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