Thanks for the comment!a synchronous concurrency-safe page-oriented pseudo-RAM device (suchHow baked in is the synchronous requirement? Memory, for example, can
:
conform to certain policies as follows:
be asynchronous if it is copied by a dma engine, and since there are
hardware encryption engines, there may be hardware compression engines
in the future.
Synchronous is required, but likely could be simulated by ensuring all
coherency (and concurrency) requirements are met by some intermediate
"buffering driver" -- at the cost of an extra page copy into a buffer
and overhead of tracking the handles (poolid/inode/index) of pages in
the buffer that are "in flight". This is an approach we are considering
to implement an SSD backend, but hasn't been tested yet so, ahem, the
proof will be in the put'ing. ;-)