Date: Wed, 15 Aug 2018 14:30:34 -0500 From: Jedi Tek'Unum <jedi@jeditekunum.com> To: John-Mark Gurney <jmg@funkthat.com> Cc: freebsd-arm@freebsd.org Subject: Re: RPI3 swap experiments (grace under pressure) Message-ID: <DD10EA43-AD78-404D-B299-E7A32113BA0D@jeditekunum.com> In-Reply-To: <20180815125513.GT97145@funkthat.com> References: <B81E53A9-459E-4489-883B-24175B87D049@yahoo.com> <20180813021226.GA46750@www.zefox.net> <0D8B9A29-DD95-4FA3-8F7D-4B85A3BB54D7@yahoo.com> <FC0798A1-C805-4096-9EB1-15E3F854F729@yahoo.com> <20180813185350.GA47132@www.zefox.net> <FA3B8541-73E0-4796-B2AB-D55CE40B9654@yahoo.com> <20180814014226.GA50013@www.zefox.net> <02fe39af-a02c-fb6a-70b0-da3b7fd06c22@goodgas.com.au> <20180814213107.GA51051@www.zefox.net> <D04BB7AF-503F-4779-B31B-AEF2A15EA7C6@jeditekunum.com> <20180815125513.GT97145@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 15, 2018, at 7:55 AM, John-Mark Gurney <jmg@funkthat.com> wrote: >=20 > Jedi Tek'Unum wrote this message on Tue, Aug 14, 2018 at 17:17 -0500: >> I have one question??? when was the last time anyone saw Solaris kill = a process because the system was under memory stress? In my experience, = NEVER! And I wouldn???t say that the system became unreasonably = unresponsive either. >=20 > At least for Solaris 2.5, they would not allow overallocation of = swap... > If you had pages that could be modified, you had to have enough swap > storage to store a copy of those pages... If you didn't, you'd get an > out of memory error when trying to allocate the memory, such as = forking, > sbrk or mmap'ing... That=E2=80=99s an entirely different situation. The process that wants = the memory gets the error from a syscall. The only =E2=80=9Ccrime=E2=80=9D that the OOM killer victim has is that = it was selected because of its state. Gets no chance to do anything = useful - just boom, gone.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DD10EA43-AD78-404D-B299-E7A32113BA0D>