summaryrefslogtreecommitdiffstats
path: root/configs/fedora/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING
diff options
context:
space:
mode:
Diffstat (limited to 'configs/fedora/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING')
-rw-r--r--configs/fedora/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING23
1 files changed, 23 insertions, 0 deletions
diff --git a/configs/fedora/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING b/configs/fedora/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING
new file mode 100644
index 000000000..2f3d89cf6
--- /dev/null
+++ b/configs/fedora/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING
@@ -0,0 +1,23 @@
+# CONFIG_ZSMALLOC_PGTABLE_MAPPING:
+#
+# By default, zsmalloc uses a copy-based object mapping method to
+# access allocations that span two pages. However, if a particular
+# architecture (ex, ARM) performs VM mapping faster than copying,
+# then you should select this. This causes zsmalloc to use page table
+# mapping rather than copying for object mapping.
+#
+# You can check speed with zsmalloc benchmark:
+# https://github.com/spartacus06/zsmapbench
+#
+# Symbol: ZSMALLOC_PGTABLE_MAPPING [=n]
+# Type : bool
+# Defined at mm/Kconfig:708
+# Prompt: Use page table mapping to access object in zsmalloc
+# Depends on: ZSMALLOC [=y]=y
+# Location:
+# -> Memory Management options
+# -> Memory allocator for compressed pages (ZSMALLOC [=y])
+#
+#
+#
+# CONFIG_ZSMALLOC_PGTABLE_MAPPING is not set