From: Xiongwei Song <[email protected]>
The radix-tree for Page Cache has been replaced with xarray, see
commit eb797a8ee0ab ("page cache: Rearrange address_space"), so move
"radix-tree" to "xarray".
Signed-off-by: Xiongwei Song <[email protected]>
---
Documentation/admin-guide/cgroup-v1/memory.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/admin-guide/cgroup-v1/memory.rst b/Documentation/admin-guide/cgroup-v1/memory.rst
index 47d1d7d932a8..dcb65b49bb22 100644
--- a/Documentation/admin-guide/cgroup-v1/memory.rst
+++ b/Documentation/admin-guide/cgroup-v1/memory.rst
@@ -197,11 +197,11 @@ are not accounted. We just account pages under usual VM management.
RSS pages are accounted at page_fault unless they've already been accounted
for earlier. A file page will be accounted for as Page Cache when it's
-inserted into inode (radix-tree). While it's mapped into the page tables of
+inserted into inode (xarray). While it's mapped into the page tables of
processes, duplicate accounting is carefully avoided.
An RSS page is unaccounted when it's fully unmapped. A PageCache page is
-unaccounted when it's removed from radix-tree. Even if RSS pages are fully
+unaccounted when it's removed from xarray. Even if RSS pages are fully
unmapped (by kswapd), they may exist as SwapCache in the system until they
are really freed. Such SwapCaches are also accounted.
A swapped-in page is accounted after adding into swapcache.
--
2.25.1
From: Xiongwei Song <[email protected]>
"listers" -> "listeners"
Signed-off-by: Xiongwei Song <[email protected]>
---
Documentation/admin-guide/cgroup-v1/memory.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/admin-guide/cgroup-v1/memory.rst b/Documentation/admin-guide/cgroup-v1/memory.rst
index dcb65b49bb22..1f239fa938c2 100644
--- a/Documentation/admin-guide/cgroup-v1/memory.rst
+++ b/Documentation/admin-guide/cgroup-v1/memory.rst
@@ -909,7 +909,7 @@ experiences some pressure. In this situation, only group C will receive the
notification, i.e. groups A and B will not receive it. This is done to avoid
excessive "broadcasting" of messages, which disturbs the system and which is
especially bad if we are low on memory or thrashing. Group B, will receive
-notification only if there are no event listers for group C.
+notification only if there are no event listeners for group C.
There are three optional modes that specify different propagation behavior:
--
2.25.1
On Fri, Jul 21, 2023 at 01:49:38PM +0800, [email protected] wrote:
> From: Xiongwei Song <[email protected]>
>
> "listers" -> "listeners"
>
> Signed-off-by: Xiongwei Song <[email protected]>
Applied 1-2 to cgroup/for-6.6.
Thanks.
--
tejun