€•—]Œsphinx.addnodes”Œdocument”“”)”}”(Œ rawsource”Œ”Œchildren”]”(Œ translations”Œ LanguagesNode”“”)”}”(hhh]”(hŒ pending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ refdomain”Œstd”Œreftype”Œdoc”Œ reftarget”Œ(/translations/zh_CN/admin-guide/mm/zswap”Œmodname”NŒ classname”NŒ refexplicit”ˆuŒtagname”hhh ubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ(/translations/zh_TW/admin-guide/mm/zswap”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ(/translations/it_IT/admin-guide/mm/zswap”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ(/translations/ja_JP/admin-guide/mm/zswap”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ(/translations/ko_KR/admin-guide/mm/zswap”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ(/translations/sp_SP/admin-guide/mm/zswap”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h hhŒ _document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒzswap”h]”hŒzswap”…””}”(hh¨hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh£hžhhŸŒB/var/lib/git/docbuild/linux/Documentation/admin-guide/mm/zswap.rst”h Kubh¢)”}”(hhh]”(h§)”}”(hŒOverview”h]”hŒOverview”…””}”(hhºhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh·hžhhŸh¶h KubhŒ paragraph”“”)”}”(hX Zswap is a lightweight compressed cache for swap pages. It takes pages that are in the process of being swapped out and attempts to compress them into a dynamically allocated RAM-based memory pool. zswap basically trades CPU cycles for potentially reduced swap I/O. This trade-off can also result in a significant performance improvement if reads from the compressed cache are faster than reads from a swap device.”h]”hX Zswap is a lightweight compressed cache for swap pages. It takes pages that are in the process of being swapped out and attempts to compress them into a dynamically allocated RAM-based memory pool. zswap basically trades CPU cycles for potentially reduced swap I/O. This trade-off can also result in a significant performance improvement if reads from the compressed cache are faster than reads from a swap device.”…””}”(hhÊhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Khh·hžhubhÉ)”}”(hŒSome potential benefits:”h]”hŒSome potential benefits:”…””}”(hhØhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Khh·hžhubhŒ bullet_list”“”)”}”(hhh]”(hŒ list_item”“”)”}”(hŒaDesktop/laptop users with limited RAM capacities can mitigate the performance impact of swapping.”h]”hÉ)”}”(hŒaDesktop/laptop users with limited RAM capacities can mitigate the performance impact of swapping.”h]”hŒaDesktop/laptop users with limited RAM capacities can mitigate the performance impact of swapping.”…””}”(hhñhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Khhíubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhhèhžhhŸh¶h Nubhì)”}”(hX Overcommitted guests that share a common I/O resource can dramatically reduce their swap I/O pressure, avoiding heavy handed I/O throttling by the hypervisor. This allows more work to get done with less impact to the guest workload and guests sharing the I/O subsystem”h]”hÉ)”}”(hX Overcommitted guests that share a common I/O resource can dramatically reduce their swap I/O pressure, avoiding heavy handed I/O throttling by the hypervisor. This allows more work to get done with less impact to the guest workload and guests sharing the I/O subsystem”h]”hX Overcommitted guests that share a common I/O resource can dramatically reduce their swap I/O pressure, avoiding heavy handed I/O throttling by the hypervisor. This allows more work to get done with less impact to the guest workload and guests sharing the I/O subsystem”…””}”(hj hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Khjubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhhèhžhhŸh¶h Nubhì)”}”(hŒrUsers with SSDs as swap devices can extend the life of the device by drastically reducing life-shortening writes. ”h]”hÉ)”}”(hŒqUsers with SSDs as swap devices can extend the life of the device by drastically reducing life-shortening writes.”h]”hŒqUsers with SSDs as swap devices can extend the life of the device by drastically reducing life-shortening writes.”…””}”(hj!hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Khjubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhhèhžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ*”uh1hæhŸh¶h Khh·hžhubhÉ)”}”(hŒÊZswap evicts pages from compressed cache on an LRU basis to the backing swap device when the compressed pool reaches its size limit. This requirement had been identified in prior community discussions.”h]”hŒÊZswap evicts pages from compressed cache on an LRU basis to the backing swap device when the compressed pool reaches its size limit. This requirement had been identified in prior community discussions.”…””}”(hj=hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Khh·hžhubhÉ)”}”(hX«Whether Zswap is enabled at the boot time depends on whether the ``CONFIG_ZSWAP_DEFAULT_ON`` Kconfig option is enabled or not. This setting can then be overridden by providing the kernel command line ``zswap.enabled=`` option, for example ``zswap.enabled=0``. Zswap can also be enabled and disabled at runtime using the sysfs interface. An example command to enable zswap at runtime, assuming sysfs is mounted at ``/sys``, is::”h]”(hŒAWhether Zswap is enabled at the boot time depends on whether the ”…””}”(hjKhžhhŸNh NubhŒliteral”“”)”}”(hŒ``CONFIG_ZSWAP_DEFAULT_ON``”h]”hŒCONFIG_ZSWAP_DEFAULT_ON”…””}”(hjUhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jShjKubhŒl Kconfig option is enabled or not. This setting can then be overridden by providing the kernel command line ”…””}”(hjKhžhhŸNh NubjT)”}”(hŒ``zswap.enabled=``”h]”hŒzswap.enabled=”…””}”(hjghžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jShjKubhŒ option, for example ”…””}”(hjKhžhhŸNh NubjT)”}”(hŒ``zswap.enabled=0``”h]”hŒzswap.enabled=0”…””}”(hjyhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jShjKubhŒ›. Zswap can also be enabled and disabled at runtime using the sysfs interface. An example command to enable zswap at runtime, assuming sysfs is mounted at ”…””}”(hjKhžhhŸNh NubjT)”}”(hŒ``/sys``”h]”hŒ/sys”…””}”(hj‹hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jShjKubhŒ, is:”…””}”(hjKhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Khh·hžhubhŒ literal_block”“”)”}”(hŒ-echo 1 > /sys/module/zswap/parameters/enabled”h]”hŒ-echo 1 > /sys/module/zswap/parameters/enabled”…””}”hj¥sbah}”(h]”h ]”h"]”h$]”h&]”Œ xml:space”Œpreserve”uh1j£hŸh¶h K&hh·hžhubhÉ)”}”(hXWhen zswap is disabled at runtime it will stop storing pages that are being swapped out. However, it will _not_ immediately write out or fault back into memory all of the pages stored in the compressed pool. The pages stored in zswap will remain in the compressed pool until they are either invalidated or faulted back into memory. In order to force all pages out of the compressed pool, a swapoff on the swap device(s) will fault back into memory all swapped out pages, including those in the compressed pool.”h]”hXWhen zswap is disabled at runtime it will stop storing pages that are being swapped out. However, it will _not_ immediately write out or fault back into memory all of the pages stored in the compressed pool. The pages stored in zswap will remain in the compressed pool until they are either invalidated or faulted back into memory. In order to force all pages out of the compressed pool, a swapoff on the swap device(s) will fault back into memory all swapped out pages, including those in the compressed pool.”…””}”(hjµhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K(hh·hžhubeh}”(h]”Œoverview”ah ]”h"]”Œoverview”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒDesign”h]”hŒDesign”…””}”(hjÎhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjËhžhhŸh¶h K2ubhÉ)”}”(hŒáZswap receives pages for compression from the swap subsystem and is able to evict pages from its own compressed pool on an LRU basis and write them back to the backing swap device in the case that the compressed pool is full.”h]”hŒáZswap receives pages for compression from the swap subsystem and is able to evict pages from its own compressed pool on an LRU basis and write them back to the backing swap device in the case that the compressed pool is full.”…””}”(hjÜhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K4hjËhžhubhÉ)”}”(hX„Zswap makes use of zpool for the managing the compressed memory pool. Each allocation in zpool is not directly accessible by address. Rather, a handle is returned by the allocation routine and that handle must be mapped before being accessed. The compressed memory pool grows on demand and shrinks as compressed pages are freed. The pool is not preallocated. By default, a zpool of type selected in ``CONFIG_ZSWAP_ZPOOL_DEFAULT`` Kconfig option is created, but it can be overridden at boot time by setting the ``zpool`` attribute, e.g. ``zswap.zpool=zsmalloc``. It can also be changed at runtime using the sysfs ``zpool`` attribute, e.g.::”h]”(hX”Zswap makes use of zpool for the managing the compressed memory pool. Each allocation in zpool is not directly accessible by address. Rather, a handle is returned by the allocation routine and that handle must be mapped before being accessed. The compressed memory pool grows on demand and shrinks as compressed pages are freed. The pool is not preallocated. By default, a zpool of type selected in ”…””}”(hjêhžhhŸNh NubjT)”}”(hŒ``CONFIG_ZSWAP_ZPOOL_DEFAULT``”h]”hŒCONFIG_ZSWAP_ZPOOL_DEFAULT”…””}”(hjòhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jShjêubhŒQ Kconfig option is created, but it can be overridden at boot time by setting the ”…””}”(hjêhžhhŸNh NubjT)”}”(hŒ ``zpool``”h]”hŒzpool”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jShjêubhŒ attribute, e.g. ”…””}”(hjêhžhhŸNh NubjT)”}”(hŒ``zswap.zpool=zsmalloc``”h]”hŒzswap.zpool=zsmalloc”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jShjêubhŒ4. It can also be changed at runtime using the sysfs ”…””}”(hjêhžhhŸNh NubjT)”}”(hŒ ``zpool``”h]”hŒzpool”…””}”(hj(hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jShjêubhŒ attribute, e.g.:”…””}”(hjêhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K8hjËhžhubj¤)”}”(hŒ2echo zsmalloc > /sys/module/zswap/parameters/zpool”h]”hŒ2echo zsmalloc > /sys/module/zswap/parameters/zpool”…””}”hj@sbah}”(h]”h ]”h"]”h$]”h&]”j³j´uh1j£hŸh¶h KBhjËhžhubhÉ)”}”(hŒqThe zsmalloc type zpool has a complex compressed page storage method, and it can achieve great storage densities.”h]”hŒqThe zsmalloc type zpool has a complex compressed page storage method, and it can achieve great storage densities.”…””}”(hjNhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KDhjËhžhubhÉ)”}”(hXCWhen a swap page is passed from swapout to zswap, zswap maintains a mapping of the swap entry, a combination of the swap type and swap offset, to the zpool handle that references that compressed swap page. This mapping is achieved with a red-black tree per swap type. The swap offset is the search key for the tree nodes.”h]”hXCWhen a swap page is passed from swapout to zswap, zswap maintains a mapping of the swap entry, a combination of the swap type and swap offset, to the zpool handle that references that compressed swap page. This mapping is achieved with a red-black tree per swap type. The swap offset is the search key for the tree nodes.”…””}”(hj\hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KGhjËhžhubhÉ)”}”(hŒªDuring a page fault on a PTE that is a swap entry, the swapin code calls the zswap load function to decompress the page into the page allocated by the page fault handler.”h]”hŒªDuring a page fault on a PTE that is a swap entry, the swapin code calls the zswap load function to decompress the page into the page allocated by the page fault handler.”…””}”(hjjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KMhjËhžhubhÉ)”}”(hŒ¹Once there are no PTEs referencing a swap page stored in zswap (i.e. the count in the swap_map goes to 0) the swap code calls the zswap invalidate function to free the compressed entry.”h]”hŒ¹Once there are no PTEs referencing a swap page stored in zswap (i.e. the count in the swap_map goes to 0) the swap code calls the zswap invalidate function to free the compressed entry.”…””}”(hjxhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KQhjËhžhubhÉ)”}”(hŒaZswap seeks to be simple in its policies. Sysfs attributes allow for one user controlled policy:”h]”hŒaZswap seeks to be simple in its policies. Sysfs attributes allow for one user controlled policy:”…””}”(hj†hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KUhjËhžhubhç)”}”(hhh]”hì)”}”(hŒYmax_pool_percent - The maximum percentage of memory that the compressed pool can occupy. ”h]”hÉ)”}”(hŒXmax_pool_percent - The maximum percentage of memory that the compressed pool can occupy.”h]”hŒXmax_pool_percent - The maximum percentage of memory that the compressed pool can occupy.”…””}”(hj›hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KXhj—ubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhj”hžhhŸh¶h Nubah}”(h]”h ]”h"]”h$]”h&]”j;j<uh1hæhŸh¶h KXhjËhžhubhÉ)”}”(hXThe default compressor is selected in ``CONFIG_ZSWAP_COMPRESSOR_DEFAULT`` Kconfig option, but it can be overridden at boot time by setting the ``compressor`` attribute, e.g. ``zswap.compressor=lzo``. It can also be changed at runtime using the sysfs "compressor" attribute, e.g.::”h]”(hŒ&The default compressor is selected in ”…””}”(hjµhžhhŸNh NubjT)”}”(hŒ#``CONFIG_ZSWAP_COMPRESSOR_DEFAULT``”h]”hŒCONFIG_ZSWAP_COMPRESSOR_DEFAULT”…””}”(hj½hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jShjµubhŒF Kconfig option, but it can be overridden at boot time by setting the ”…””}”(hjµhžhhŸNh NubjT)”}”(hŒ``compressor``”h]”hŒ compressor”…””}”(hjÏhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jShjµubhŒ attribute, e.g. ”…””}”(hjµhžhhŸNh NubjT)”}”(hŒ``zswap.compressor=lzo``”h]”hŒzswap.compressor=lzo”…””}”(hjáhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jShjµubhŒU. It can also be changed at runtime using the sysfs “compressor†attribute, e.g.:”…””}”(hjµhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K[hjËhžhubj¤)”}”(hŒ2echo lzo > /sys/module/zswap/parameters/compressor”h]”hŒ2echo lzo > /sys/module/zswap/parameters/compressor”…””}”hjùsbah}”(h]”h ]”h"]”h$]”h&]”j³j´uh1j£hŸh¶h KahjËhžhubhÉ)”}”(hXPWhen the zpool and/or compressor parameter is changed at runtime, any existing compressed pages are not modified; they are left in their own zpool. When a request is made for a page in an old zpool, it is uncompressed using its original compressor. Once all pages are removed from an old zpool, the zpool and its compressor are freed.”h]”hXPWhen the zpool and/or compressor parameter is changed at runtime, any existing compressed pages are not modified; they are left in their own zpool. When a request is made for a page in an old zpool, it is uncompressed using its original compressor. Once all pages are removed from an old zpool, the zpool and its compressor are freed.”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KchjËhžhubhÉ)”}”(hXŽSome of the pages in zswap are same-value filled pages (i.e. contents of the page have same value or repetitive pattern). These pages include zero-filled pages and they are handled differently. During store operation, a page is checked if it is a same-value filled page before compressing it. If true, the compressed length of the page is set to zero and the pattern or same-filled value is stored.”h]”hXŽSome of the pages in zswap are same-value filled pages (i.e. contents of the page have same value or repetitive pattern). These pages include zero-filled pages and they are handled differently. During store operation, a page is checked if it is a same-value filled page before compressing it. If true, the compressed length of the page is set to zero and the pattern or same-filled value is stored.”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KihjËhžhubhÉ)”}”(hXTo prevent zswap from shrinking pool when zswap is full and there's a high pressure on swap (this will result in flipping pages in and out zswap pool without any real benefit but with a performance drop for the system), a special parameter has been introduced to implement a sort of hysteresis to refuse taking pages into zswap pool until it has sufficient space if the limit has been hit. To set the threshold at which zswap would start accepting pages again after it became full, use the sysfs ``accept_threshold_percent`` attribute, e. g.::”h]”(hXòTo prevent zswap from shrinking pool when zswap is full and there’s a high pressure on swap (this will result in flipping pages in and out zswap pool without any real benefit but with a performance drop for the system), a special parameter has been introduced to implement a sort of hysteresis to refuse taking pages into zswap pool until it has sufficient space if the limit has been hit. To set the threshold at which zswap would start accepting pages again after it became full, use the sysfs ”…””}”(hj#hžhhŸNh NubjT)”}”(hŒ``accept_threshold_percent``”h]”hŒaccept_threshold_percent”…””}”(hj+hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jShj#ubhŒ attribute, e. g.:”…””}”(hj#hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KphjËhžhubj¤)”}”(hŒ?echo 80 > /sys/module/zswap/parameters/accept_threshold_percent”h]”hŒ?echo 80 > /sys/module/zswap/parameters/accept_threshold_percent”…””}”hjCsbah}”(h]”h ]”h"]”h$]”h&]”j³j´uh1j£hŸh¶h KyhjËhžhubhÉ)”}”(hŒ:Setting this parameter to 100 will disable the hysteresis.”h]”hŒ:Setting this parameter to 100 will disable the hysteresis.”…””}”(hjQhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K{hjËhžhubhÉ)”}”(hŒÄSome users cannot tolerate the swapping that comes with zswap store failures and zswap writebacks. Swapping can be disabled entirely (without disabling zswap itself) on a cgroup-basis as follows::”h]”hŒÃSome users cannot tolerate the swapping that comes with zswap store failures and zswap writebacks. Swapping can be disabled entirely (without disabling zswap itself) on a cgroup-basis as follows:”…””}”(hj_hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K}hjËhžhubj¤)”}”(hŒ /sys/fs/cgroup//memory.zswap.writeback”h]”hŒ /sys/fs/cgroup//memory.zswap.writeback”…””}”hjmsbah}”(h]”h ]”h"]”h$]”h&]”j³j´uh1j£hŸh¶h KhjËhžhubhÉ)”}”(hŒÕNote that if the store failures are recurring (for e.g if the pages are incompressible), users can observe reclaim inefficiency after disabling writeback (because the same pages might be rejected again and again).”h]”hŒÕNote that if the store failures are recurring (for e.g if the pages are incompressible), users can observe reclaim inefficiency after disabling writeback (because the same pages might be rejected again and again).”…””}”(hj{hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KƒhjËhžhubhÉ)”}”(hXWhen there is a sizable amount of cold memory residing in the zswap pool, it can be advantageous to proactively write these cold pages to swap and reclaim the memory for other use cases. By default, the zswap shrinker is disabled. User can enable it as follows::”h]”hXWhen there is a sizable amount of cold memory residing in the zswap pool, it can be advantageous to proactively write these cold pages to swap and reclaim the memory for other use cases. By default, the zswap shrinker is disabled. User can enable it as follows:”…””}”(hj‰hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K‡hjËhžhubj¤)”}”(hŒ6echo Y > /sys/module/zswap/parameters/shrinker_enabled”h]”hŒ6echo Y > /sys/module/zswap/parameters/shrinker_enabled”…””}”hj—sbah}”(h]”h ]”h"]”h$]”h&]”j³j´uh1j£hŸh¶h KŒhjËhžhubhÉ)”}”(hŒYThis can be enabled at the boot time if ``CONFIG_ZSWAP_SHRINKER_DEFAULT_ON`` is selected.”h]”(hŒ(This can be enabled at the boot time if ”…””}”(hj¥hžhhŸNh NubjT)”}”(hŒ$``CONFIG_ZSWAP_SHRINKER_DEFAULT_ON``”h]”hŒ CONFIG_ZSWAP_SHRINKER_DEFAULT_ON”…””}”(hj­hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jShj¥ubhŒ is selected.”…””}”(hj¥hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KŽhjËhžhubhÉ)”}”(hŒ¯A debugfs interface is provided for various statistic about pool size, number of pages stored, same-value filled pages and various counters for the reasons pages are rejected.”h]”hŒ¯A debugfs interface is provided for various statistic about pool size, number of pages stored, same-value filled pages and various counters for the reasons pages are rejected.”…””}”(hjÅhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K‘hjËhžhubeh}”(h]”Œdesign”ah ]”h"]”Œdesign”ah$]”h&]”uh1h¡hh£hžhhŸh¶h K2ubeh}”(h]”Œzswap”ah ]”h"]”Œzswap”ah$]”h&]”uh1h¡hhhžhhŸh¶h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h¶uh1hŒcurrent_source”NŒ current_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¦NŒ generator”NŒ datestamp”NŒ source_link”NŒ source_url”NŒ toc_backlinks”Œentry”Œfootnote_backlinks”KŒ sectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒ strip_classes”NŒ report_level”KŒ halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ traceback”ˆŒinput_encoding”Œ utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”jŒerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œ language_code”Œen”Œrecord_dependencies”NŒconfig”NŒ id_prefix”hŒauto_id_prefix”Œid”Œ dump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h¶Œ _destination”NŒ _config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒ raw_enabled”KŒline_length_limit”M'Œpep_references”NŒ pep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒ rfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œ smart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œ docinfo_xform”KŒsectsubtitle_xform”‰Œ image_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(jàjÝjÈjÅjØjÕuŒ nametypes”}”(jà‰jȉj؉uh}”(jÝh£jÅh·jÕjËuŒ footnote_refs”}”Œ citation_refs”}”Œ autofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ footnotes”]”Œ citations”]”Œautofootnote_start”KŒsymbol_footnote_start”KŒ id_counter”Œ collections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œ transformer”NŒ include_log”]”Œ decoration”Nhžhub.