SAS and mapping descriptors

[Jonathan Shapiro]

   It's known that those mappings can't possibly conflict with any
   of the other mappings that I _do_ want to access, so the sender
   can't violate my integrity.

Wait!  I'm not assuming a SAS!

   ...these MMU table resources are generally
   implemented as caches anyway, so they can be dynamically thrown away and
   reallocated to map other parts or memory.

I was moving towards a model in which page frames are accounted
resources, and that would include page frames used for memory mapping
tables.  Making MMU tables be cached certainly simplifies things, but
it raises issues of RT guarantees w.r.t. mapping table reconstruction
that make me resist it.

   ...There are now tools,
   some of which were developed here, that allow arbitrary structured
   data to be automatically massaged as necessary when pieces of DSM are
   transferred across heterogeneous nodes.  So, for example, you could
   share a single address space between a big-endian PA-RISC machine and
   a little-endian i386.  Sharing between machines with different word sizes
   would be more difficult...

Can you point me to any papers on this?

Thanks again!


Jonathan