@@ -8,12 +8,6 @@ Frontswap provides a "transcendent memory" interface for swap pages.
8
8
In some environments, dramatic performance savings may be obtained because
9
9
swapped pages are saved in RAM (or a RAM-like device) instead of a swap disk.
10
10
11
- (Note, frontswap -- and :ref: `cleancache ` (merged at 3.0) -- are the "frontends"
12
- and the only necessary changes to the core kernel for transcendent memory;
13
- all other supporting code -- the "backends" -- is implemented as drivers.
14
- See the LWN.net article `Transcendent memory in a nutshell `_
15
- for a detailed overview of frontswap and related kernel parts)
16
-
17
11
.. _Transcendent memory in a nutshell : https://lwn.net/Articles/454795/
18
12
19
13
Frontswap is so named because it can be thought of as the opposite of
@@ -87,11 +81,9 @@ This interface is ideal when data is transformed to a different form
87
81
and size (such as with compression) or secretly moved (as might be
88
82
useful for write-balancing for some RAM-like devices). Swap pages (and
89
83
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
91
- cleancache) interface to transcendent memory provides a nice way to read
92
- and write -- and indirectly "name" -- the pages.
84
+ but-much-faster-than-disk "pseudo-RAM device".
93
85
94
- Frontswap -- and cleancache -- with a fairly small impact on the kernel,
86
+ Frontswap with a fairly small impact on the kernel,
95
87
provides a huge amount of flexibility for more dynamic, flexible RAM
96
88
utilization in various system configurations:
97
89
0 commit comments