Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 04 Dec 2000 22:33:54 +0100
From:      Poul-Henning Kamp <phk@critter.freebsd.dk>
To:        opentrax@email.com
Cc:        dwmalone@maths.tcd.ie, hackers@FreeBSD.ORG
Subject:   Re: M_ZERO patches. 
Message-ID:  <27912.975965634@critter>
In-Reply-To: Your message of "Mon, 04 Dec 2000 13:28:12 PST." <200012042128.NAA07566@spammie.svbug.com> 

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?27912.975965634>