FLPA (X'OS') Page available -This flag is set if
available on the chain. Note that this
there is no such page available.
there is a full
flag may be set
4K page
even ifSKEY This one-byte field contains the storage key assigned to storage
on this chain.TCODE This ene-byte field contains the FREETAB table code for storage on
this chain.
Each element on the free chain has the following format:
<------------- 4bytes -------------) r-- I POINTER --pointer to the next 0(0) I element in the free chain I 1------------------------------------ I SIZE -- size of this free
4 (4) element, in bytes
Remainder of this free elementWhen the user issues a variable length GETMAIN, the control program
reserves 6 1/2 pages for usage; this is a designed and set value.
If the user wants more space, fer example, fer more directories, be
should free (from the high end of storage) some of the variable area. As indicated in the illustration above, the POINTER field points to
the next element in the chain, or contains the value zero if there is no
next element. TheSIZE field contains the size of this element, in
bytes.
All elements within a given chain are chained together in order of
descending stcrage address. This is done for two reasons:
1. Because the allocation search is satisfiedby the first free
element that is large enough, the allocated elements are grouped
together at the top of the storage area, and prevent storage
fragmentation. This is particularly important for high-storage
free storage allocations, because it is desirable to keepFREELOWE as high as possible.
2. If free storage does becomesomewhat the search causes
as few page faults as possible.
As a matter of convention, completely nonallccated 4K pages arekept on the user chain rather than the nucleus chain. This is because
requests for large blocks of storage are made, most of the time, from
user storage rather than from nucleus storage. Nucleus requests need to
break up a full page less frequently thanuser requests. Method of operation and Program Organization 2-103
available on the chain. Note that this
there is no such page available.
there is a full
flag may be set
4K page
even if
on this chain.
this chain.
Each element on the free chain has the following format:
<------------- 4
4 (4) element, in bytes
Remainder of this free element
reserves 6 1/2 pages for
If the user wants more space, fer example, fer more directories, be
should free (from the high end of storage) some of the variable
the next element in the chain, or contains the value zero if there is no
next element. The
bytes.
All elements within a given chain are chained together in order of
descending stcrage address. This is done for two reasons:
1. Because the allocation search is satisfied
element that is large enough, the allocated elements are grouped
together at the top of the storage area, and prevent storage
fragmentation. This is particularly important for high-storage
free storage allocations, because it is desirable to keep
2. If free storage does become
as few page faults as possible.
As a matter of convention, completely nonallccated 4K pages are
requests for large blocks of storage are made, most of the time, from
user storage rather than from nucleus storage. Nucleus requests need to
break up a full page less frequently than