mm/frontswap: cleanup doc and comment error
Signed-off-by: Wanpeng Li <liwp.linux@gmail.com> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>hifive-unleashed-5.1
parent
3389b530a6
commit
1d00015e26
|
@ -25,7 +25,7 @@ with the specified swap device number (aka "type"). A "store" will
|
||||||
copy the page to transcendent memory and associate it with the type and
|
copy the page to transcendent memory and associate it with the type and
|
||||||
offset associated with the page. A "load" will copy the page, if found,
|
offset associated with the page. A "load" will copy the page, if found,
|
||||||
from transcendent memory into kernel memory, but will NOT remove the page
|
from transcendent memory into kernel memory, but will NOT remove the page
|
||||||
from from transcendent memory. An "invalidate_page" will remove the page
|
from transcendent memory. An "invalidate_page" will remove the page
|
||||||
from transcendent memory and an "invalidate_area" will remove ALL pages
|
from transcendent memory and an "invalidate_area" will remove ALL pages
|
||||||
associated with the swap type (e.g., like swapoff) and notify the "device"
|
associated with the swap type (e.g., like swapoff) and notify the "device"
|
||||||
to refuse further stores with that swap type.
|
to refuse further stores with that swap type.
|
||||||
|
@ -99,7 +99,7 @@ server configured with a large amount of RAM... without pre-configuring
|
||||||
how much of the RAM is available for each of the clients!
|
how much of the RAM is available for each of the clients!
|
||||||
|
|
||||||
In the virtual case, the whole point of virtualization is to statistically
|
In the virtual case, the whole point of virtualization is to statistically
|
||||||
multiplex physical resources acrosst the varying demands of multiple
|
multiplex physical resources across the varying demands of multiple
|
||||||
virtual machines. This is really hard to do with RAM and efforts to do
|
virtual machines. This is really hard to do with RAM and efforts to do
|
||||||
it well with no kernel changes have essentially failed (except in some
|
it well with no kernel changes have essentially failed (except in some
|
||||||
well-publicized special-case workloads).
|
well-publicized special-case workloads).
|
||||||
|
|
|
@ -120,7 +120,7 @@ static inline void __frontswap_clear(struct swap_info_struct *sis, pgoff_t offse
|
||||||
* "Store" data from a page to frontswap and associate it with the page's
|
* "Store" data from a page to frontswap and associate it with the page's
|
||||||
* swaptype and offset. Page must be locked and in the swap cache.
|
* swaptype and offset. Page must be locked and in the swap cache.
|
||||||
* If frontswap already contains a page with matching swaptype and
|
* If frontswap already contains a page with matching swaptype and
|
||||||
* offset, the frontswap implmentation may either overwrite the data and
|
* offset, the frontswap implementation may either overwrite the data and
|
||||||
* return success or invalidate the page from frontswap and return failure.
|
* return success or invalidate the page from frontswap and return failure.
|
||||||
*/
|
*/
|
||||||
int __frontswap_store(struct page *page)
|
int __frontswap_store(struct page *page)
|
||||||
|
|
Loading…
Reference in New Issue