Lines Matching full:but

34 from transcendent memory into kernel memory, but will NOT remove the page
90 but-much-faster-than-disk "pseudo-RAM device" and the frontswap (and
108 as in zcache, but then "remotified" to another system's RAM.  This
123 virtual machines, but the pages can be compressed and deduplicated to
135 * Sure there may be performance advantages in some situations, but
140 swap device.  If CONFIG_FRONTSWAP is enabled but no frontswap "backend"
156 the existing eight bits, but let's worry about that minor optimization
163 backend, such as zcache, must implement policies to carefully (but
187 page.  But if the backend does accept a page, the data from the page
212 but this would require fairly drastic changes.  Even if it were
228 block I/O layer is not only unnecessary, but may perform "optimizations"
255 can still use frontswap but a backend for such devices must configure
262 Nearly always it can, but no, sometimes it cannot.  Consider an example
265 is non-compressible and so would take the entire 4K.  But the backend
276 space.  But if frontswap has placed a page in transcendent memory, that
290 them as global but declare them in a new include file that isn't