Date: Fri, 16 Jul 1999 09:03:10 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: Sean Witham <sean.witham@asa.co.uk> Cc: "Daniel C. Sobral" <dcs@newsguy.com>, Garance A Drosihn <drosih@rpi.edu>, freebsd-hackers@FreeBSD.ORG, tech-userlevel@netbsd.org Subject: Re: Swap overcommit (was Re: Replacement for grep(1) (part 2)) Message-ID: <199907161603.JAA19963@apollo.backplane.com> References: <199907132346.TAA13780@bikini.ihack.net> <v04011702b3b275648c0f@[128.113.24.47]> <378CCB7D.AD8BC57B@newsguy.com> <378F458F.4BEEB674@asa.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
:
:For those who wish to develop code for safety related systems that is
:not good enough. They have to prove that all code can handle the
:degradation
:of resources gracefully. Such code relies on guaranteed memory
:allocations
:or in the very least warnings of memory shortage and prioritized
:allocations.
:So the least important sub-systems die first.
:
:--Sean
I'm sorry, but when you write code for a safety related system you
do not dynamically allocate memory at all. It's all essentially static.
There is no issue with the memory resource. Besides, none of the BSD's are
certified for any of that stuff that I know of.
What's next: A space shot? These what-if scenarios are getting
ridiculous.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199907161603.JAA19963>