From owner-freebsd-hackers Mon Dec 4 13:34: 4 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 4 13:34:00 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 793AB37B400 for ; Mon, 4 Dec 2000 13:33:59 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eB4LXsL27914; Mon, 4 Dec 2000 22:33:54 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: opentrax@email.com Cc: dwmalone@maths.tcd.ie, hackers@FreeBSD.ORG Subject: Re: M_ZERO patches. In-Reply-To: Your message of "Mon, 04 Dec 2000 13:28:12 PST." <200012042128.NAA07566@spammie.svbug.com> Date: Mon, 04 Dec 2000 22:33:54 +0100 Message-ID: <27912.975965634@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200012042128.NAA07566@spammie.svbug.com>, opentrax@email.com writes : >Can someone email me with a brief explaination of this M_ZERO path? >I see it is about something to do with memory (malloc, bcopy, etc.) > > Thanks Jessem. Since a majority of malloc(9) uses immediately bzero(9) the allocation, I added an flag to malloc(9) so one can ask for a zero'ed allocation. This saves a couple hundred calls to bzero(9), improves cache-locality and generally improves code readability as a result. It will also allow us to operate a "idle-time-malloc(9)- zeroing-daemon" later. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message