Skip to contentSkip to conversation

docs/vm: fix 'mm_count' vs 'mm_users' counter confusion

PATCH Applied Alexander Gordeev 1 participant 1 message Aug 10, 2020 Documentation

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 docs/vm: fix 'mm_count' vs 'mm_users' counter confusion

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 <[email protected]>
Cc Andrew Morton <[email protected]>
---
 Documentation/vm/active_mm.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/vm/active_mm.rst +1 -1
index c84471b..6f8269c 100644
@@ -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
Signature · 1 line
1.8.3.1