From 890e1df1bec891d9203724541e81f8fbe5183388 Mon Sep 17 00:00:00 2001 From: hc <hc@nodka.com> Date: Mon, 19 Feb 2024 01:57:06 +0000 Subject: [PATCH] default settings GPIO PA4 PA6 PA3 PB5 --- kernel/Documentation/vm/unevictable-lru.rst | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/Documentation/vm/unevictable-lru.rst b/kernel/Documentation/vm/unevictable-lru.rst index b8e29f9..17d0861 100644 --- a/kernel/Documentation/vm/unevictable-lru.rst +++ b/kernel/Documentation/vm/unevictable-lru.rst @@ -98,7 +98,7 @@ -------------------------------- The unevictable LRU facility interacts with the memory control group [aka -memory controller; see Documentation/cgroup-v1/memory.txt] by extending the +memory controller; see Documentation/admin-guide/cgroup-v1/memory.rst] by extending the lru_list enum. The memory controller data structure automatically gets a per-zone unevictable @@ -439,7 +439,7 @@ The unevictable LRU can be scanned for compactable regions and the default behavior is to do so. /proc/sys/vm/compact_unevictable_allowed controls -this behavior (see Documentation/sysctl/vm.txt). Once scanning of the +this behavior (see Documentation/admin-guide/sysctl/vm.rst). Once scanning of the unevictable LRU is enabled, the work of compaction is mostly handled by the page migration code and the same work flow as described in MIGRATING MLOCKED PAGES will apply. -- Gitblit v1.6.2