From owner-freebsd-hackers Mon Dec 4 14:41:55 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 4 14:41:53 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from spammie.svbug.com (mg134-106.ricochet.net [204.179.134.106]) by hub.freebsd.org (Postfix) with ESMTP id A392937B404 for ; Mon, 4 Dec 2000 14:41:51 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id OAA08132; Mon, 4 Dec 2000 14:38:41 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200012042238.OAA08132@spammie.svbug.com> Date: Mon, 4 Dec 2000 14:38:40 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: M_ZERO patches. To: phk@critter.freebsd.dk Cc: dwmalone@maths.tcd.ie, hackers@FreeBSD.ORG In-Reply-To: <27912.975965634@critter> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: jessem@spammie.svbug.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 4 Dec, Poul-Henning Kamp wrote: > 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. > Very cool! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message