> If we had a virtual memory manager and swap file/partition, wouldn't JOS
> require less real RAM? We need to get that virtual memory manager working.
Yes, but it would probably be unusably slow without a great deal
of work on our part to make sure that things like java.lang.String aren't
swapped out :)
> This is one of the very good reasons for pursuing (1) Kore and (2) package
> files.
Package files I don't have any objection too, and it should be
fairly straightforward to write support for them, in either the C++
primordial classloader or (as you suggest below) in a Java
classloader. (As a matter of fact, doing it in a Java classloader would
come in handy for testing decaf's integration/support with/of a given
classlibrary, because the file/io/net/VM-interaction stuff covers a whole
lot of the core functionality.)
When I get a chance, I'll try to look into the size of classpath
vs. Kore -- if Kore is compellingly smaller, I'll look into a switch.
-_Quinn
_______________________________________________
Kernel maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/kernel
