Re: [Adeos-main] Re: [PATCH] Adeos nanokernel for 2.5.38 1/2: no-arch code

[Karim Yaghmour <karim@opersys.com>]

Jacob Gorm Hansen wrote:
> On Tue, Sep 24, 2002 at 05:05:12PM -0400, Karim Yaghmour wrote:
> >
> > To be honest, nothing in Adeos is "new". Adeos is implemented on
> > classic early '90s nanokernel research. I've listed a number of
> > nanokernel papers in the paper I wrote on Adeos. A complete list
> > of nanokernel papers would probably have hundreds of entries.
> > Some of these nanokernels even had OS schedulers (exokernel for
> > instance). All Adeos implements is a scheme for sharing the
> > interrupts among the various OSes using an interrupt pipeline.
> 
> Hi,
> 
> are you planning to add spaces & portals, like in Space or Pebble?

I'm not sure whether what we plan to offer actually fits Space's definition
of spaces, but domains already exist and portals should be trivial to
implement over what we already have. For details on what plan to offer
in terms of spaces, take a look at the paper I wrote describing how
to implement Linux SMP clusters:
http://opersys.com/ftp/pub/Adeos/practical-smp-clusters.ps
Basically, Adeos would hand over RAM regions according to each OS
instance's requests. In such a case, each kernel would have its own
virtual memory and communication would be possible using "bridges",
shared physical RAM regions. Many OSes can coexist in the same virtual
address space, but the mechanisms for managing the virtual address
space are not up to Adeos.

Karim

===================================================
                 Karim Yaghmour
               karim@opersys.com
      Embedded and Real-Time Linux Expert
===================================================