From owner-freebsd-current Sun Oct 22 15:30:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from dataloss.net (massive.dataloss.net [212.189.232.193]) by hub.freebsd.org (Postfix) with SMTP id 5B29137B65F for ; Sun, 22 Oct 2000 15:30:03 -0700 (PDT) Received: (qmail 60196 invoked by uid 1000); 22 Oct 2000 22:32:20 -0000 Date: Mon, 23 Oct 2000 00:32:20 +0200 From: Peter van Dijk To: current@FreeBSD.ORG Subject: Re: Junior Kernel Hacker Task: M_ZERO Message-ID: <20001023003220.N51871@dataloss.net> Mail-Followup-To: current@FreeBSD.ORG References: <17100.972069144@critter> <200010222224.SAA00866@hda.hda.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200010222224.SAA00866@hda.hda.com>; from dufault@hda.com on Sun, Oct 22, 2000 at 06:23:57PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 22, 2000 at 06:23:57PM -0400, Peter Dufault wrote: [snip] > I guess I'm suggesting a clarification on when you want to set this flag. > If I want to be sure I get my zeroed out stuff real soon should I use > still use bzero? No. What he means is that this 'zeroing process' will happen during *all* idle time. If you do a malloc and request that the area is zeroed, it will select an area that it has *already* zeroed. If that is not available, it will still do the zeroing for you. Adding that flag to a malloc *guarantees* a zeroed area. The change allows *room for* optimization. Greetz, Peter -- dataloss networks '/ignore-ance is bliss' - me 'Het leven is een stuiterbal, maar de mijne plakt aan t plafond!' - me To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message