Lines Matching refs:RAM
9 swapped pages are saved in RAM (or a RAM-like device) instead of a swap disk.
21 a synchronous concurrency-safe page-oriented "pseudo-RAM device" conforming
23 in-kernel compressed memory, aka "zcache", or future RAM-like devices);
24 this pseudo-RAM device is not directly accessible or addressable by the
88 useful for write-balancing for some RAM-like devices). Swap pages (and
89 evicted page-cache pages) are a great use for this kind of slower-than-RAM-
90 but-much-faster-than-disk "pseudo-RAM device" and the frontswap (and
95 provides a huge amount of flexibility for more dynamic, flexible RAM
100 that can be safely kept in RAM. Zcache essentially trades off CPU
108 as in zcache, but then "remotified" to another system's RAM. This
109 allows RAM to be dynamically load-balanced back-and-forth as needed,
113 server configured with a large amount of RAM... without pre-configuring
114 how much of the RAM is available for each of the clients!
118 virtual machines. This is really hard to do with RAM and efforts to do
122 "fallow" hypervisor-owned RAM to not only be "time-shared" between multiple
124 optimize RAM utilization. And when guest OS's are induced to surrender
125 underutilized RAM (e.g. with "selfballooning"), sudden unexpected
127 to be swapped to and from hypervisor RAM (if overall host system memory
229 that are inappropriate for a RAM-oriented device including delaying