aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--Documentation/vm/frontswap.txt4
-rw-r--r--mm/frontswap.c2
2 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/vm/frontswap.txt b/Documentation/vm/frontswap.txt
index 37067cf455f4..5ef2d1366425 100644
--- a/Documentation/vm/frontswap.txt
+++ b/Documentation/vm/frontswap.txt
@@ -25,7 +25,7 @@ with the specified swap device number (aka "type"). A "store" will
25copy the page to transcendent memory and associate it with the type and 25copy the page to transcendent memory and associate it with the type and
26offset associated with the page. A "load" will copy the page, if found, 26offset associated with the page. A "load" will copy the page, if found,
27from transcendent memory into kernel memory, but will NOT remove the page 27from transcendent memory into kernel memory, but will NOT remove the page
28from from transcendent memory. An "invalidate_page" will remove the page 28from transcendent memory. An "invalidate_page" will remove the page
29from transcendent memory and an "invalidate_area" will remove ALL pages 29from transcendent memory and an "invalidate_area" will remove ALL pages
30associated with the swap type (e.g., like swapoff) and notify the "device" 30associated with the swap type (e.g., like swapoff) and notify the "device"
31to refuse further stores with that swap type. 31to refuse further stores with that swap type.
@@ -99,7 +99,7 @@ server configured with a large amount of RAM... without pre-configuring
99how much of the RAM is available for each of the clients! 99how much of the RAM is available for each of the clients!
100 100
101In the virtual case, the whole point of virtualization is to statistically 101In the virtual case, the whole point of virtualization is to statistically
102multiplex physical resources acrosst the varying demands of multiple 102multiplex physical resources across the varying demands of multiple
103virtual machines. This is really hard to do with RAM and efforts to do 103virtual machines. This is really hard to do with RAM and efforts to do
104it well with no kernel changes have essentially failed (except in some 104it well with no kernel changes have essentially failed (except in some
105well-publicized special-case workloads). 105well-publicized special-case workloads).
diff --git a/mm/frontswap.c b/mm/frontswap.c
index 5318b3a57080..6b3e71a2cd48 100644
--- a/mm/frontswap.c
+++ b/mm/frontswap.c
@@ -120,7 +120,7 @@ static inline void __frontswap_clear(struct swap_info_struct *sis, pgoff_t offse
120 * "Store" data from a page to frontswap and associate it with the page's 120 * "Store" data from a page to frontswap and associate it with the page's
121 * swaptype and offset. Page must be locked and in the swap cache. 121 * swaptype and offset. Page must be locked and in the swap cache.
122 * If frontswap already contains a page with matching swaptype and 122 * If frontswap already contains a page with matching swaptype and
123 * offset, the frontswap implmentation may either overwrite the data and 123 * offset, the frontswap implementation may either overwrite the data and
124 * return success or invalidate the page from frontswap and return failure. 124 * return success or invalidate the page from frontswap and return failure.
125 */ 125 */
126int __frontswap_store(struct page *page) 126int __frontswap_store(struct page *page)