Date: Tue, 31 Jul 2018 11:54:41 -0700 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-arm@freebsd.org Subject: Re: RPI3 swap experiments Message-ID: <93D7A41F-3AFA-48FE-A82E-FC4AA76A355C@yahoo.com> In-Reply-To: <20180731181923.GC94742@www.zefox.net> References: <AB5EE2E4-B2FD-4CA9-A993-04C2A4BE10AE@yahoo.com> <20180723155311.GB45726@www.zefox.net> <4ED9B658-A5A8-4BA6-9412-EBB7150B4B66@yahoo.com> <20180723190257.GA47869@www.zefox.net> <76BCFCB9-1071-4557-9FDE-017444ADBF42@yahoo.com> <20180725232453.GA57716@www.zefox.net> <20180731054712.GA92917@www.zefox.net> <d17be735-4d7e-73b6-4af1-a64470bc9e32@sentry.org> <20180731153531.GA94742@www.zefox.net> <908FB299-07CF-4E88-9C18-298CA357AD01@yahoo.com> <20180731181923.GC94742@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2018-Jul-31, at 11:19 AM, bob prohaska <fbsd at www.zefox.net> wrote: > On Tue, Jul 31, 2018 at 10:51:51AM -0700, Mark Millard wrote: >>=20 >>=20 >> On 2018-Jul-31, at 8:35 AM, bob prohaska <fbsd at www.zefox.net> = wrote: >>=20 >>> On Tue, Jul 31, 2018 at 10:31:33PM +1000, Trev wrote: >>>> bob prohaska wrote on 31/07/2018 15:47: >>>>=20 >>>>> It would be most interesting to see what happens if OOMA >>>>> could be turned off. Is that possible? >>>>=20 >>>> Possibly, but you might find you're treating the symptom(s) rather = than=20 >>>> the cause(s) ... something must be triggering the condition whether=20= >>>> correctly or not. >>>=20 >>> That's my point. To determine if OOMA is triggered correctly or not. = I'm starting >>> to think not. >>>=20 >>> The reason is the dependency on swap layout (mixed USB/microSD vs = all one or the >>> other) and the fact that OOMA kills don't seem to coincide with = periods of=20 >>> maximum storage read/write delay, which is the conventional = explanation for >>> why OOMA kills happen in the first place. If turning off OOMA allows = buildworld >>> to complete successfully it suggests OOMA isn't correctly = implemented.=20 >>=20 >> Your rpi2 report said: >>=20 >>> In this particular case all swap is on USB, in a single >>> 2 GB partition. >>=20 >> which for that example indicates that swap layout being split >> was not involved. (But there is the potential too-large issue.) >>=20 > That's true, I can't test mixed swap on that setup. My point was=20 > that formerly (months ago) 2GB of USB swap worked for -j4 buildworld. >=20 >> Have you had other examples of non-split swap layout getting >> OOMA kills? If yes, what types of contexts? [Especially any that >> do not have observed huge latencies or to evidence of device >> failures (retries required).] Any on rpi3? Any others on rpi2? >>=20 > Yes. Another storage configuration for the Pi3 (not installed=20 > at the moment) has three 1 GB swap partitions on USB and three > 1 GB swap partitions on microSD. In that case buildworld fails > from OOMA using 2 GB mixed or microSD swap but succeeds using=20 > USB swap. You seem to be indicating "one swap device" worked even with multiple swap partitions on the device, at least for the USB example. But you also have the example of a microsSD which got the OOMA activity with only one swap device in use (but multiple swap partitions on that device). Do you have examples that are multi-device swap but that do not involve that microSD? What was the mix of OOMA vs. it finishing for such example(s) (if any)? Can you attempt such tests with devices that seems to always work for "one swap device" tests? > That surprised me in that the microSD cards are the same. The USB=20 > device in that case is 3.0 vs 3.1, so different in some small way. >=20 >> As for swap use, do you have any tmpfs or other files systems >> that are memory based that also use swap if they grow too >> big (and are configured to allow such growth)? >>=20 > No memory-based filesystems in use.=20 >=20 =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?93D7A41F-3AFA-48FE-A82E-FC4AA76A355C>