Lines Matching refs:memory

1 Frontswap provides a "transcendent memory" interface for swap pages.
6 and the only necessary changes to the core kernel for transcendent memory;
8 See the LWN.net article "Transcendent memory in a nutshell" for a detailed
15 to the requirements of transcendent memory (such as Xen's "tmem", or
16 in-kernel compressed memory, aka "zcache", or future RAM-like devices);
25 copy the page to transcendent memory and associate it with the type and
27 from transcendent memory into kernel memory, but will NOT remove the page
28 from transcendent memory.  An "invalidate_page" will remove the page
29 from transcendent memory and an "invalidate_area" will remove ALL pages
36 success, the data has been successfully saved to transcendent memory and
38 If a store returns failure, transcendent memory has rejected the data, and the
45 store frontswap pages to more completely manage its memory usage.
47 Note that if a page is stored and the page already exists in transcendent memory
70 "transcendent memory" that is otherwise not directly addressable to the kernel.
76 cleancache) interface to transcendent memory provides a nice way to read
84 stored in local memory, thus increasing the total anonymous pages
86 cycles used in compression/decompression for better memory utilization.
87 Benchmarks have shown little or no impact when memory pressure is
89 on some workloads under high memory pressure.
91 "RAMster" builds on zcache by adding "peer-to-peer" transcendent memory
96 vice versa.  RAMster can also be configured as a memory server so
111 memory pressure may result in swapping; frontswap allows those pages
112 to be swapped to and from hypervisor RAM (if overall host system memory
118 a memory extension technology.
129 request (i.e. provides no memory despite claiming it might),
145 When swap pages are stored in transcendent memory instead of written
146 out to disk, there is a side effect that this may create more memory
149 dynamically) manage memory limits to ensure this doesn't happen.
156 frontswap backend has access to some "memory" that is not directly
157 accessible by the kernel.  Exactly how much memory it provides is
209 defined dynamically depending on current memory constraints.
231 There is a downside to the transcendent memory specifications for
261 space.  But if frontswap has placed a page in transcendent memory, that
264 of the memory managed by frontswap and back into kernel-addressable memory.
267 this is driven using the frontswap_shrink mechanism when memory pressure