Date: Tue, 22 Oct 2024 17:00:24 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 280846] Low memory freezes / OOM: a thread waited too long to allocate a page Message-ID: <bug-280846-227-6fEw35UZUF@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-280846-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280846 --- Comment #49 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to commit-hook from comment #48) Previous(/current) descriptions : vm.domain.0.stats.laundpdpgs: Laundry pages scanned by the page daemon vm.domain.0.stats.laundry: laundry pages vm.domain.0.stats.unswappable: Unswappable pages vm.domain.0.stats.unswppdpgs: Unswappable pages scanned by the page daemon More accurate ones for comparison/contrast (if I've understood right)? : vm.domain.0.stats.laundpdpgs: Swappable Laundry pages scanned by the page daemon vm.domain.0.stats.laundry: Swappable+Unswappable laundry pages vm.domain.0.stats.unswappable: Unswappable pages vm.domain.0.stats.unswppdpgs: Unswappable pages scanned by the page daemon vm.domain.0.stats.laundpdpgs is actually unchanged but in the new context the original description is highly ambiguous via it not matching vm.domain.0.stats.laundry . To estimate the old vm.domain.0.stats.laundry value (just Swappable) requires subtraction in the new context. Also: vm.domain.0.stats.laundry+vm.domain.0.stats.unswappable should not be used in the new context (avoiding double counting of unswappable). The proposed wording suggests those points. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-280846-227-6fEw35UZUF>