Ryan Heise wrote:
>
> Cliff Baeseman wrote:
>
> > JOS is also based on a single instance JVM design. This is a very poor
> > design in my opinion.
>
> It allows you to share 15 megs of system classes between applications.
> It allows you to have one thread scheduler across all applications. It
> allows you to have one garbage collecter and memory manager across all
> applications. There are a few other optimizations that are possible.
>
It might be possible to cache byte codes, native modules, JIT'd and
HotSpotted code across multiple
JVM instances in shared memory. This could help with the first issue,
if there are no technical show stoppers.
The second isn't an issue if native threads are used, right?
A monolithic gc may be simpler, but makes the system somewhat hard to
enforce policies on resources. How do you keep a process/application
from hogging
all of the available memory, for example?
The linux *kernel* is a nice little beastie, it would make a nice
foundation,
I think, as long as you avoid most of the linux *OS* stuff - text config
files
(well, might be hard to get rid of them all), X windows,
termio, installation, etc, and mainly just keep the device drivers and a
few other
oddments.
Then it could get fun...
-- Eric
_______________________________________________
Kernel maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/kernel
