Date: Thu, 12 Nov 2015 20:09:54 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: Michael Tuexen <tuexen@freebsd.org> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: Memory management issue on RPi? Message-ID: <20151112180954.GP2257@kib.kiev.ua> In-Reply-To: <984BA2E2-DD1A-4D05-858B-362192660E54@freebsd.org> References: <CB20D8FA-303C-4AA2-B2A6-1FF25DDB8A94@freebsd.org> <20151112121825.GJ2257@kib.kiev.ua> <BE0B4761-54EC-4632-BA23-A3C373D419AE@freebsd.org> <20151112171221.GO2257@kib.kiev.ua> <984BA2E2-DD1A-4D05-858B-362192660E54@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 12, 2015 at 06:57:03PM +0100, Michael Tuexen wrote: > > On 12 Nov 2015, at 18:12, Konstantin Belousov <kostikbel@gmail.com> wrote: > > > > On Thu, Nov 12, 2015 at 05:25:37PM +0100, Michael Tuexen wrote: > >>> On 12 Nov 2015, at 13:18, Konstantin Belousov <kostikbel@gmail.com> wrote: > >>> This is a known problem with the swap-less OOM. The following patch > >>> should give you an immediate relief. You might want to tweak > >>> sysctl vm.pageout_oom_seq if default value is not right, it was selected > >>> by 'try and see' approach on very small (32 or 64MB) i386 VM. > >> It just works... Will do some more testing... > > > > I am more interested in report if OOM was triggered when it should. > How do I know? What output do you want to see? > > Best regards > Michael > > > > Try running several instances of 'sort /dev/zero'. ^^^^^^^^^^^^^ I already answered this. Run sort /dev/zero, and see whether OOM fires.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151112180954.GP2257>