Lines Matching refs:RAM

3 swapped pages are saved in RAM (or a RAM-like device) instead of a swap disk.
14 a synchronous concurrency-safe page-oriented "pseudo-RAM device" conforming
16 in-kernel compressed memory, aka "zcache", or future RAM-like devices);
17 this pseudo-RAM device is not directly accessible or addressable by the
73 useful for write-balancing for some RAM-like devices).  Swap pages (and
74 evicted page-cache pages) are a great use for this kind of slower-than-RAM-
75 but-much-faster-than-disk "pseudo-RAM device" and the frontswap (and
80 provides a huge amount of flexibility for more dynamic, flexible RAM
85 that can be safely kept in RAM.  Zcache essentially trades off CPU
93 as in zcache, but then "remotified" to another system's RAM.  This
94 allows RAM to be dynamically load-balanced back-and-forth as needed,
98 server configured with a large amount of RAM... without pre-configuring
99 how much of the RAM is available for each of the clients!
103 virtual machines.  This is really hard to do with RAM and efforts to do
107 "fallow" hypervisor-owned RAM to not only be "time-shared" between multiple
109 optimize RAM utilization.  And when guest OS's are induced to surrender
110 underutilized RAM (e.g. with "selfballooning"), sudden unexpected
112 to be swapped to and from hypervisor RAM (if overall host system memory
214 that are inappropriate for a RAM-oriented device including delaying