From owner-freebsd-arm@freebsd.org Thu Nov 12 20:03:06 2015 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 121B7A2D4F5 for ; Thu, 12 Nov 2015 20:03:06 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7D1921F42; Thu, 12 Nov 2015 20:03:05 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id tACK30hQ075444 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 12 Nov 2015 22:03:00 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua tACK30hQ075444 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id tACK30uJ075443; Thu, 12 Nov 2015 22:03:00 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 12 Nov 2015 22:03:00 +0200 From: Konstantin Belousov To: Michael Tuexen Cc: freebsd-arm Subject: Re: Memory management issue on RPi? Message-ID: <20151112200300.GR2257@kib.kiev.ua> References: <20151112121825.GJ2257@kib.kiev.ua> <20151112171221.GO2257@kib.kiev.ua> <984BA2E2-DD1A-4D05-858B-362192660E54@freebsd.org> <20151112180954.GP2257@kib.kiev.ua> <29DB8CF5-7569-4139-885A-8496993805A7@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <29DB8CF5-7569-4139-885A-8496993805A7@freebsd.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Nov 2015 20:03:06 -0000 On Thu, Nov 12, 2015 at 08:47:29PM +0100, Michael Tuexen wrote: > > On 12 Nov 2015, at 19:09, Konstantin Belousov wrote: > > > > On Thu, Nov 12, 2015 at 06:57:03PM +0100, Michael Tuexen wrote: > >>> On 12 Nov 2015, at 18:12, Konstantin Belousov wrote: > >>> > >>> On Thu, Nov 12, 2015 at 05:25:37PM +0100, Michael Tuexen wrote: > >>>>> On 12 Nov 2015, at 13:18, Konstantin Belousov 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. > OK, now I understand. You want to see if some processes are getting killed. > (I was thinking that you might want to see some sysctl counters or so). > > Results: > * I'm able to compile/link/install a kernel from source. This was not > possible before. > * When running three instances of sort /dev/zero, two of them get killed > after a while (less than a minute). One continued to run, but got also > kill eventually. All via ssh login. Exactly, this is the experiment I want to occur, and even more, the results are good. > > Let me know if you want me to do some more testing. No, this is enough. Thank you.