From owner-freebsd-hackers Fri Jul 16 9: 6:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id AC171156A8 for ; Fri, 16 Jul 1999 09:06:14 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA19963; Fri, 16 Jul 1999 09:03:10 -0700 (PDT) (envelope-from dillon) Date: Fri, 16 Jul 1999 09:03:10 -0700 (PDT) From: Matthew Dillon Message-Id: <199907161603.JAA19963@apollo.backplane.com> To: Sean Witham Cc: "Daniel C. Sobral" , Garance A Drosihn , freebsd-hackers@FreeBSD.ORG, tech-userlevel@netbsd.org Subject: Re: Swap overcommit (was Re: Replacement for grep(1) (part 2)) References: <199907132346.TAA13780@bikini.ihack.net> <378CCB7D.AD8BC57B@newsguy.com> <378F458F.4BEEB674@asa.co.uk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message