Lines Matching +full:ram +full:- +full:code

9 swapped pages are saved in RAM (or a RAM-like device) instead of a swap disk.
15 a synchronous concurrency-safe page-oriented "pseudo-RAM device" conforming
17 in-kernel compressed memory, aka "zcache", or future RAM-like devices);
18 this pseudo-RAM device is not directly accessible or addressable by the
19 kernel and is of unknown and possibly time-varying size.  The driver
76 useful for write-balancing for some RAM-like devices).  Swap pages (and
77 evicted page-cache pages) are a great use for this kind of slower-than-RAM-
78 but-much-faster-than-disk "pseudo-RAM device".
81 provides a huge amount of flexibility for more dynamic, flexible RAM
86 that can be safely kept in RAM.  Zcache essentially trades off CPU
92 "RAMster" builds on zcache by adding "peer-to-peer" transcendent memory
94 as in zcache, but then "remotified" to another system's RAM.  This
95 allows RAM to be dynamically load-balanced back-and-forth as needed,
99 server configured with a large amount of RAM... without pre-configuring
100 how much of the RAM is available for each of the clients!
104 virtual machines.  This is really hard to do with RAM and efforts to do
106 well-publicized special-case workloads).
108 "fallow" hypervisor-owned RAM to not only be "time-shared" between multiple
110 optimize RAM utilization.  And when guest OS's are induced to surrender
111 underutilized RAM (e.g. with "selfballooning"), sudden unexpected
113 to be swapped to and from hypervisor RAM (if overall host system memory
131 CPU overhead is still negligible -- and since every frontswap fail
132 precedes a swap page write-to-disk, the system is highly likely
161 Whenever a swap-device is swapon'd frontswap_init() is called,
169 have room, frontswap_store returns -1 and the kernel swaps the page
180 When the swap subsystem needs to swap-in a page (swap_readpage()),
184 the swap-in is complete.  If not, the normal swap-in code is
194   or maybe swap-over-nbd/NFS)?
215 that are inappropriate for a RAM-oriented device including delaying
224 Similarly, a KVM guest-side implementation could do in-guest compression
229 choose to accept pages only until host-swapping might be imminent,
251 is non-compressible and so would take the entire 4K.  But the backend
260 The frontswap code depends on some swap-subsystem-internal data