* [PATCH] docs/vm: fix 'mm_count' vs 'mm_users' counter confusion
@ 2020-08-10 6:24 Alexander Gordeev
0 siblings, 0 replies; only message in thread
From: Alexander Gordeev @ 2020-08-10 6:24 UTC (permalink / raw)
To: linux-kernel; +Cc: Alexander Gordeev, Jonathan Corbet, Andrew Morton
In the context of the anonymous address space lifespan
description the 'mm_users' reference counter is confused
with 'mm_count'. I.e a "zombie" mm gets released when
"mm_count" becomes zero, not "mm_users".
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Alexander Gordeev <agordeev@linux.ibm.com>
---
Documentation/vm/active_mm.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/vm/active_mm.rst b/Documentation/vm/active_mm.rst
index c84471b..6f8269c 100644
--- a/Documentation/vm/active_mm.rst
+++ b/Documentation/vm/active_mm.rst
@@ -64,7 +64,7 @@ Active MM
actually get cases where you have a address space that is _only_ used by
lazy users. That is often a short-lived state, because once that thread
gets scheduled away in favour of a real thread, the "zombie" mm gets
- released because "mm_users" becomes zero.
+ released because "mm_count" becomes zero.
Also, a new rule is that _nobody_ ever has "init_mm" as a real MM any
more. "init_mm" should be considered just a "lazy context when no other
--
1.8.3.1
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2020-08-10 6:25 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-08-10 6:24 [PATCH] docs/vm: fix 'mm_count' vs 'mm_users' counter confusion Alexander Gordeev
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).