Re: ARM is sort of channeling the IBM 360

Stephen Fuld wrote:


snip


Sorry for the self folllow up, but the next paragraph in my prewvious
post is copnfusing at best.

The no relocation issue only applied within a task, not between tasks.
So, for example, if you had a job with three tasks, r.g. compile, link
and execute", if the execute had larger memory requirements than say
the link, the fjob might be delayed if an "execute sized" region wasn't
available, but that region didn't have to be the same one as the link
used.

 
While a job could change its memory requirements with each task,IIRC
it was better to specify the largest requirement in the beginning, and
releasing memory as the largest remaining requirement got smaller.
This was because if the memory requirement increased inn the middle of
the job, you were not quaranteed that the additional memory was
available, and if it wasn't, the job would have to be terminated or
"rolled out" until the required memory was available.  Note, as John
explained, since programs were not relocatable, if a program was
rolled out, it could only be rolled in to the same address it was
rolled out from.

--
 - Stephen Fuld
(e-mail address disguised to prevent spam)