Date: Sat, 11 Aug 2018 01:51:19 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 230402] With buildworld, the system can not use swap Message-ID: <bug-230402-227-Iq1TXRgr6S@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-230402-227@https.bugs.freebsd.org/bugzilla/> References: <bug-230402-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230402 --- Comment #7 from Mark Millard <marklmi26-fbsd@yahoo.com> --- Mark Johnston has indicated that after investigations in small armv7 and aarch64 examples, such as rpi3's and rpi2's (V1.1): I do think the default [vm.pageout_oom_seq] value is too low and will get that addressed in 12.0. Mark J. had someone with rpi3 and rpi2 (V1.1) usage experiment with: sysctl vm.pageout_oom_seq=3D120 and things got much farther but it was not a cure. While not a cure but it was discovered that when some other changes were made ("lowering the pagedaemon sleep period") a fair time ago, vm.pageout_oom_seq was not rescaled to roughly match, making OOM kills happen easier. There are some patches for reporting information that Mark J. has indicated will likely have some variant become standard FreeBSD code that could be enabled without needing patches, targeting 12.0 having such. The lists have a long history tied to the investigations on arm. I'll reference the first Mark Johnston message here: https://lists.freebsd.org/pipermail/freebsd-arm/2018-August/018506.html His messages have most of the technical content tied to internal evidence his patches produced and what might be done. (Other folks produced data from there environments, mostly one person.) The prior activity does not get much into internal activity tied to the issue. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-230402-227-Iq1TXRgr6S>