Date: 24 Feb 2001 23:14:27 +0100 From: Dag-Erling Smorgrav <des@ofug.org> To: seebs@plethora.net (Peter Seebach) Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Setting memory allocators for library functions. Message-ID: <xzp3dd37mpo.fsf@flood.ping.uio.no> In-Reply-To: seebs@plethora.net's message of "Sat, 24 Feb 2001 15:58:39 -0600" References: <200102242158.f1OLwd619758@guild.plethora.net>
next in thread | previous in thread | raw e-mail | index | archive | help
seebs@plethora.net (Peter Seebach) writes: > In message <9877.983050267@critter>, Poul-Henning Kamp writes: > > And just how will the OS know that a particular memory chip will not > > generate an uncorrectable ECC error ? > It can't, but that's no reason for the OS to *add* reasons for failures. It doesn't (and I'm very close to using expletives here). On the contrary, it tries to always satisfy the application's requests and hopes for the best. It's quite possible that memory isn't available when you call malloc(), but becomes available before you actually get to dirty the pages that were allocated. DES -- Dag-Erling Smorgrav - des@ofug.org 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?xzp3dd37mpo.fsf>