Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site u1100a.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!gamma!pyuxww!u1100a!sdo
From: sdo@u1100a.UUCP (Scott Orshan)
Newsgroups: net.unix-wizards
Subject: Re: memory access benchmark
Message-ID: <836@u1100a.UUCP>
Date: Tue, 15-Oct-85 09:05:15 EDT
Article-I.D.: u1100a.836
Posted: Tue Oct 15 09:05:15 1985
Date-Received: Thu, 17-Oct-85 00:30:53 EDT
References: <89@ucbjade.BERKELEY.EDU>
Reply-To: sdo@u1100a.UUCP (Scott Orshan)
Organization: Bell Communications Research, Piscataway, NJ
Lines: 22

In article <89@ucbjade.BERKELEY.EDU> cnrdean@ucbtopaz.BERKELEY.EDU () writes:
>
>My guess is that to test the data size, I would simply keep 'alloc'ing
>until a failure happens.  I would like, not only to declare a
>large array, but to test that values are accurately stored.

This wouldn't work on the Sperry 1100 versions of the UNIX system.
The stack and data share a memory area.  There is a user defined
address at which the stack starts growing downward and the heap
starts growing upward.  This address is an option to the loader
and it allows stack to be traded for heap.

0400000  <----- Stack Growth ----| Data |------ sbrk area ---> 0777777
				 ^
				 |
			This can be adjusted
-- 

			Scott Orshan
			Bell Communications Research
			201-981-3064
			{ihnp4,bellcore,pyuxww}!u1100a!sdo