@@ -8,7 +8,7 @@ significant performance improvement if reads from the compressed cache are
8
8
faster than reads from a swap device.
9
9
10
10
NOTE: Zswap is a new feature as of v3.11 and interacts heavily with memory
11
- reclaim. This interaction has not be fully explored on the large set of
11
+ reclaim. This interaction has not been fully explored on the large set of
12
12
potential configurations and workloads that exist. For this reason, zswap
13
13
is a work in progress and should be considered experimental.
14
14
@@ -23,7 +23,7 @@ Some potential benefits:
23
23
drastically reducing life-shortening writes.
24
24
25
25
Zswap evicts pages from compressed cache on an LRU basis to the backing swap
26
- device when the compressed pool reaches it size limit. This requirement had
26
+ device when the compressed pool reaches its size limit. This requirement had
27
27
been identified in prior community discussions.
28
28
29
29
To enabled zswap, the "enabled" attribute must be set to 1 at boot time. e.g.
@@ -37,7 +37,7 @@ the backing swap device in the case that the compressed pool is full.
37
37
38
38
Zswap makes use of zbud for the managing the compressed memory pool. Each
39
39
allocation in zbud is not directly accessible by address. Rather, a handle is
40
- return by the allocation routine and that handle must be mapped before being
40
+ returned by the allocation routine and that handle must be mapped before being
41
41
accessed. The compressed memory pool grows on demand and shrinks as compressed
42
42
pages are freed. The pool is not preallocated.
43
43
@@ -56,7 +56,7 @@ in the swap_map goes to 0) the swap code calls the zswap invalidate function,
56
56
via frontswap, to free the compressed entry.
57
57
58
58
Zswap seeks to be simple in its policies. Sysfs attributes allow for one user
59
- controlled policies :
59
+ controlled policy :
60
60
* max_pool_percent - The maximum percentage of memory that the compressed
61
61
pool can occupy.
62
62
0 commit comments