Miles Sabin <[EMAIL PROTECTED]> writes:
> Agreed. One big headache is the fact that asynchronous IO
> (POSIX or otherwise) is typically going to require that buffers
> be at fixed addresses, ...
> I guess that in principle it ought to be possible to tweak
> JVMs to special-case a priviledged class of byte[]s to allow
> them to be pinned for an extended interval without completely
> screwing GC,
The real issue is that you need an efficient way for Java applications
to manipulate and manage memory outside of the Java heap (or else, to
have more control over how the heap itself is managed). Jaguar lets you
make use of "external objects" which can be treated as byte arrays or
even more structured objects -- i.e. you can map a Java class with
fields and the rest onto an external memory region. Byte arrays are not
all you want!
Chi-Chao Chang at Cornell proposed a similar mechanism called "jbufs"
which is based on an extension to the Microsoft Marmot Java compiler.
Basically the same idea.
Cheers -
Matt
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
