"Kelly Yancey" <[EMAIL PROTECTED]> writes: > Ahh...but wouldn't the bzero() touch all of the memory just allocated > functionally making it non-overcommit? No. If it were an "non-overcomitting malloc", it would return NULL and set errno to ENOMEM, instead of dumping core. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- Overcommit and calloc() Kelly Yancey
- Re: Overcommit and calloc() Dag-Erling Smorgrav
- 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 cal... Dag-Erling Smorgrav
- Re: Overcommit and calloc() Ville-Pertti Keinonen
- Re: Overcommit and calloc() Peter Dufault
- RE: Overcommit and calloc() Charles Randall
- Re: RE: Overcommit and calloc() Matthew Dillon