From: Kelly Yancey [mailto:[EMAIL PROTECTED]] >I have another post on this list which begs the question: if memory given >to us fro sbrk() is already zeroed, why zero it again if we don't have >too.... if we make calloc() smarter, we could save come clock cycles. Because the memory returned from malloc() might be from a previous malloc()/free() and may be dirty. Charles To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- RE: Overcommit and calloc() Kelly Yancey
- Re: Overcommit and calloc() Dag-Erling Smorgrav
- Re: Overcommit and calloc() Dan Nelson
- RE: Overcommit and calloc() Kelly Yancey
- RE: Overcommit and calloc() Kelly Yancey
- Re: Overcommit and calloc() Dag-Erling Smorgrav
- Re: Overcommit and calloc() John-Mark Gurney
- Re: Overcommit and calloc(... Dag-Erling Smorgrav
- Re: Overcommit and calloc() Ville-Pertti Keinonen
- Re: Overcommit and calloc() Peter Dufault
- Re: RE: Overcommit and calloc() Charles Randall
- Re: RE: Overcommit and calloc() Matthew Dillon
- RE: Overcommit and calloc() Kelly Yancey
- RE: Overcommit and calloc() David Wolfskill
- RE: Overcommit and calloc() Bob Bishop
- Re: RE: Overcommit and calloc() Matthew Dillon
- Re: RE: Overcommit and calloc() Bob Bishop
- Re: RE: Overcommit and calloc() Matthew Dillon
- Re: RE: Overcommit and calloc() Matthew Dillon
- RE: RE: Overcommit and calloc() Kelly Yancey