brk's zero-fill behavior on VAXen

[Larry Campbell]

In article <7208 at elsie.UUCP> ado at elsie.UUCP (Arthur David Olson) writes:
>In section 2 of the UNIX Programmer's Manual, the description of the "brk" and
>"sbrk" calls note only that they change the system's notion of the lowest
>location not used by the program.  If the result of the call is to expand the
>address space of the process, there's no promise about the contents of the
>newly-available address space.  Yet on our VAX (and on yours, too, if you
>have one) the newly-available space is always zero filled.
>
>Can system performance be improved by avoiding zero filling of the new
>memory?

Yes, a little bit, but this would be an obvious security hole.
-- 
Larry Campbell       MCI: LCAMPBELL          The Boston Software Works, Inc.
UUCP: {alliant,wjh12}!maynard!campbell      120 Fulton Street, Boston MA 02109
ARPA: campbell%maynard.uucp at harvisr.harvard.edu     (617) 367-6846