From owner-freebsd-hackers Tue Feb 16 21:19: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from biggusdiskus.flyingfox.com (parker-T1-2-gw.sf3d.best.net [209.157.165.30]) by hub.freebsd.org (Postfix) with ESMTP id 8323C111B1 for ; Tue, 16 Feb 1999 21:18:59 -0800 (PST) (envelope-from jas@flyingfox.com) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.8/8.8.5) id WAA25521 for hackers@freebsd.org; Tue, 16 Feb 1999 22:25:50 -0800 (PST) Date: Tue, 16 Feb 1999 22:25:50 -0800 (PST) From: Jim Shankland Message-Id: <199902170625.WAA25521@biggusdiskus.flyingfox.com> To: hackers@freebsd.org Subject: Re: vm_page_zero_fill In-Reply-To: <199902170152.UAA00758@y.dyson.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Terry:] > Expecting sbrk'ed pages to be zero filled is just *wrong*. [John Dyson:] > Actually, you have to support that on most practical architectures. Architectures aside, the *semantics* have always been that newly sbrk-ed pages are zero-filled. It's been that way since at least v7. I went and looked for chapter and verse on this in the sbrk(2) man page, and was astonished not to find it. The Solaris man page mentions it, though, and I'll bet man page archaeologists can verify my assertion that this goes way, way back. Expecting to be able to get away with *not* zero=filling newly sbrk'ed pages is just *wrong*. Jim Shankland NLynx Systems, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message