Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 13 Aug 2018 18:42:26 -0700
From:      bob prohaska <fbsd@www.zefox.net>
To:        Mark Millard <marklmi@yahoo.com>
Cc:        Mark Johnston <markj@FreeBSD.org>, John Kennedy <warlock@phouka.net>, freebsd-arm <freebsd-arm@freebsd.org>, bob prohaska <fbsd@www.zefox.net>
Subject:   Re: RPI3 swap experiments (grace under pressure)
Message-ID:  <20180814014226.GA50013@www.zefox.net>
In-Reply-To: <FA3B8541-73E0-4796-B2AB-D55CE40B9654@yahoo.com>
References:  <20180809033735.GJ30738@phouka1.phouka.net> <20180809175802.GA32974@www.zefox.net> <20180812173248.GA81324@phouka1.phouka.net> <20180812224021.GA46372@www.zefox.net> <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>

next in thread | previous in thread | raw e-mail | index | archive | help
[Altered subject, philosophical question]
On Mon, Aug 13, 2018 at 01:05:38PM -0700, Mark Millard wrote:
> 
> Here there is architecture choice and goals/primary
> contexts. FreeBSD is never likely to primarily target
> anything with a workload like buildworld buildkernel
> on hardware like rpi3's and rpi2 V1.1's and
> Pine64+ 2GB's and so on.
> 

I understand that the RPi isn't a primary platform for FreeBSD.
But, decent performance under overload seems like a universal
problem that's always worth solving, whether for a computer or
an office. The exact goals might vary, but coping with too much
to do and not enough to do it with is humanity's oldest puzzle. 
 
Maybe I should ask what the goals of the OOMA process serve.
I always thought an OS's goals were along the lines of:
1. maintain control
2. get the work done
3. remain responsive

There's at least some degree of conflict between all of them, 
made worse when the workload grows beyond the design assumptions.
The RPI makes the issue more visible, but it's always lurking.

OOMA seems to sacrifice getting work done, potentially entirely,
in support of keeping the system responsive and under control.

To have some fun with the office analogy, when business is
slow the clerk serves customers as they come in. When things
get busy, the clerk says "take a number". When they get really
busy new customers are told "come back tomorrow" and when they
get absolutely frantic present customers are told "I can't finish 
this now, I'll call you when it's done". That's grace under pressure.

What do FreeBSD's designers want the system to do as it's 
progressively overworked? Is the office analogy too ambitious? 

Thanks for reading, and apologies for the ruminating.

bob prohaska




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180814014226.GA50013>