Date: Tue, 5 Jun 2018 17:48:08 -0400 From: Mark Johnston <markj@freebsd.org> To: Lev Serebryakov <lev@freebsd.org> Cc: gljennjohn@gmail.com, FreeBSD current <freebsd-current@freebsd.org> Subject: Re: swapping is completely broken in -CURRENT r334649? Message-ID: <20180605214808.GA94301@pesky> In-Reply-To: <2925b27f-43cf-8813-eaa7-4f3d12bef8f0@FreeBSD.org> References: <d3ee2b8f-bdbe-ce25-f496-6267f9bb0212@FreeBSD.org> <20180605181716.73b8ea91@ernst.home> <2925b27f-43cf-8813-eaa7-4f3d12bef8f0@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 06, 2018 at 12:22:08AM +0300, Lev Serebryakov wrote: > On 05.06.2018 19:17, Gary Jennejohn wrote: > > > > I complained about this also and alc@ gave me this hint: > > sysctl vm.pageout_update_period=0 > > Really, situation is worse than stated in subject, because processes > are being killed AFTER memory pressure, when here are a lot of free > memory already! > > It looks like very serious bug. The issue was identified earlier this week and is being worked on. It's a regression from r329882 which appears only on certain hardware. You can probably work around it by setting vm.pageout_oom_seq to a large value (try 1000 for instance), though this will make the "true" OOM killer take longer to kick in. The problem is unrelated to the pageout_update_period.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180605214808.GA94301>