Date: Mon, 23 Oct 2000 00:32:20 +0200 From: Peter van Dijk <peter@dataloss.net> To: current@FreeBSD.ORG Subject: Re: Junior Kernel Hacker Task: M_ZERO Message-ID: <20001023003220.N51871@dataloss.net> In-Reply-To: <200010222224.SAA00866@hda.hda.com>; from dufault@hda.com on Sun, Oct 22, 2000 at 06:23:57PM -0400 References: <17100.972069144@critter> <200010222224.SAA00866@hda.hda.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001023003220.N51871>