Well, bzero could map all memory (outside the boundaries) to a single zeroed page marked copy on write. The statistics you could gather might then point out some grossly broken programs. Peter -- Peter Dufault ([EMAIL PROTECTED]) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- 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 calloc(... 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
- 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