Method for reducing translation look aside buffer purges in a multitasking system
BACKGROUND OF THE INVENTION 
     1. Field of the Invention 
     The present invention relates to electronic digital processing systems and, more particularly, to data processing systems which employ virtual memory addressing. More particularly, the present invention is directed to a method for reducing operating system overhead caused by translation look aside buffer purging. 
     2. Description of the Prior Art 
     Computer systems implement virtual memory systems to more effectively manage real computer memory for computer tasks. Virtual memory is typically organized as a series of memory pages of fixed size, for example, 4096 bytes. Memory pages in turn, are grouped into segments. A virtual memory address comprises three fields as shown in FIG. 1. The segment index 100 is used to access a segment table to determine the real location of a segment containing several pages. Page index 102 is an index to access a particular page within that segment, and offset 104 provides the location of data within that particular page. 
     During task processing virtual addresses must be translated to real addresses for memory access to occur. Virtual to real address translation is carried out by a dynamic address translation mechanism 202 as shown in FIG. 2. Dynamic address translation typically requires two memory accesses: to the segment table and to the page table, before the real address can be calculated and the memory accessed for data. The result of dynamic address translation is a real address that can be used by the processor to access real memory. 
     Performing dynamic address translation for every virtual memory access greatly increases processing overhead. It is highly desirable to reduce the number of memory accesses and instruction path length required for address translation. Computer system designers have made the address resolution process more efficient by introducing a translation look aside buffer (TLB). A translation look aside buffer (208 in FIG. 2) typically contains a fixed number of entries, e.g. 256. Each TLB entry provides a direct translation from a virtual address to a real address. A typical TLB entry is shown in FIG. 3. The first field 230 is the segment table origin (STO) indicating the origin of the allocated segment table. Virtual address 232 contains the segment index (sx), page index (px), and offset (bx) as shown in FIG. 1. Real address 234 contains the real memory address used for accessing the data. 
     In operation, the processor initially performs dynamic address translation to determine the real address for a particular virtual address. The resolved entry is then added to the translation look aside buffer (TLB) 208. When future address resolution requests are made, the TLB is first checked to determine whether or not it contains an entry resolving that particular virtual address. If the virtual address is not already in the TLB, then dynamic address translation must be performed and a new TLB entry created and added to the TLB possibly casting out an older entry. 
     The TLB entries are only valid for translations within a particular segment table. Different segment tables may result in different virtual to real conversions. Without a mechanism to differentiate between TLB entries of different segment tables, the TLB must be purged at every task dispatch to prevent invalid address translations. Typically, the segment table origin is maintained in the TLB to associate a virtual to real conversion with the appropriate segment table. 
     A segment table origin (STO) defines an address space. An address space will typically persist through one or more dispatches. Each time the address space is dispatched, the TLB may have some entries left over from the previous execution of the address space which will improve performance since the initial address translation is not required. Eventually the use of address space will terminate, though it may later be reused. The virtual to real translations in the TLB will not be valid for subsequent uses of the address space. 
     At each address space dispatch, the contents of the TLB may or may not be valid, depending on whether the address space has been reused since the last time it was dispatched. 
     The processing overhead cost to purge the TLB is determined by comparing the time to purge to the length of tasks running on the computer system. The overhead to purge the TLB before task initiation is insignificant for very long running tasks. However, for a very short running task, the purge TLB overhead may constitute a significant portion of the task operating elapsed time. Thus, the requirement to frequently purge TLB adds undesired overhead to the system and reduces processor throughput. This penalty is particularly severe in short task, transaction processing systems. 
     Various methods have been suggested to reduce the need to purge the translation look aside buffer. U.S. Pat. No. 4,525,778 to Cane suggests the use of tag bits and a process identifier with each TLB entry. An address resolution access to the TLB must compare the tag bits and process identifier to determine whether this TLB entry is valid for the accessing process. If not, the entry is invalidated. Other such systems have been proposed to add marking bits to the TLB which are then compared upon TLB access. 
     The use of additional bits to mark each TLB entry adds logic overhead to the processing system. It would be desirable to avoid adding hardware or software to set and test the additional flags. It is therefore desirable to develop a TLB management system that reduces the instance of translation look aside buffer purges without adding hardware to the TLB accessing circuit. 
     The technical problem that must be resolved is to provide a system that minimizes TLB while assuring that address resolution accesses to always result in valid addresses. 
     SUMMARY OF THE INVENTION 
     The present invention is directed to providing an improved TLB purging system which reduces the number of instances of TLB purges. The present invention uses the address space allocation mechanism in conjunction with the TLB management mechanism to reduce the number of purge TLB instructions. Address spaces are allocated from a FIFO managed list of address spaces. A de-allocated address space block is placed on the bottom of the list of free address spaces. A marker is placed at the bottom of the free address space list at system initialization. When that marker reaches the top of the queue, the TLB is purged and the marker is moved to the bottom of the list. No TLB purges occur during intervening address space allocations. 
    
    
     BRIEF DESCRIPTION OF THE DRAWING 
     FIG. 1 shows the structure of a virtual address of the prior art. 
     FIG. 2 is a block diagram illustrating the virtual address resolution logic in a computer system of the prior art. 
     FIG. 3 is an example of a translation look aside buffer entry of the prior art. 
     FIG. 4 is a block diagram showing address and space allocation logic according to the present invention. 
     FIG. 5 is a diagram of the allocation process according to the present invention. 
     FIG. 6 is a diagram of the deallocation process according to the present invention. 
    
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT 
     Virtual address resolution requires the determination of a real address based on segment table, page table and offset locations for a virtual address as shown in FIG. 2 and discussed in greater detail above. The segment table origin (STO) is established during the address space allocation process. Address spaces are allocated to operating tasks from a list of free address space blocks, as shown in FIG. 4. An address space refers to the range of addresses a program or task may use. In a virtual memory system the address space of a particular program may refer to a different physical system or other programs. The operating system typically builds a fixed number of potential address spaces at system initialization. These prebuilt address spaces are dynamically allocated, as needed, from a list of available address spaces. 
     Whenever an address space is in use, that address space block is in use. Free address space blocks containing pointers to address space origins are maintained in the address space block queue 300. The address allocation process 302 removes the first block from the address space block list, and uses that address space origin as the segment table origin for the operating task. When an address space is de-allocated, the address space block is returned to the end of the queue. 
     TLB entries table 208 are valid only within a particular address space. TLB entries can cause problems only if the address space that is about to be dispatched was previously used and left entries in the TLB. In that case the STO and virtual addresses could match TLB entries but would point to invalid real addresses. If the address space was used by a different task, invalid translations of virtual to absolute addresses would occur. Thus, the system must assure that the TLB is purged before an address space is reused. If the TLB is purged as required, the system can be assured that the TLB is valid. 
     The address space allocation mechanism is used by the present invention to minimize the number of TLB purges. The present invention adds a process to check to ensure that the TLB has been purged before an address space is re-used. This process is implemented by placing a marker in the address space queue at initialization and whenever the TLB is purged. The marker is placed at the end of the queue and, as address spaces are allocated and de-allocated, eventually rises to the top of the queue. When the address space allocation mechanism detects the marker at the top of the queue &#34;purge TLB&#34; (PTLB) instruction is executed. 
     The preferred embodiment places a fullword 0 as a marker on the list of available address spaces. Each block removed from the list of available address spaces is tested to determine if it is 0. If so, the process managing the list of address spaces executes PTLB logic, returns the marker to the bottom of the list and removes the next item from the list. Address list processing logic must be modified to recognize that a list containing only a marker is an empty list. 
     In alternate embodiments the marker may be formed by placing any unambiguous value in the address space list or by changing the address space queue structure to include an extra field representing the marker. Any of the many known techniques for adding a marker to a list may be employed and are all within the scope of this invention. 
     A multi-processing system with multiple tightly coupled CPU&#39;s will maintain a TLB in each CPU even though they may be accessing shared storage. Thus, in a multi-processing system the purge TLB instruction will have to be propagated to the other processors in the multi-processor complex. 
     Although the above-described process will work in most situations, there are certain instances where it cannot be used. Where a common segment is created conflicting virtual to real mappings can occur and the TLB must be purged at each task dispatched. Common segments are provided in some operating systems to provide one virtual to real address translation for virtual addresses from different address spaces. The system must either manage these translations to ensure consistency or purge the TLB between dispatches of address spaces that have conflicting common areas. 
     The novel TLB management procedure of the present invention operates according to the process illustrated in FIG. 5. An allocate address space request is received from the operating system 240. This request may be due to the receipt of a message to be processed, a request for specific system services requiring their own address space, a request by an application for explicit address space assignment, or other timed or non-timed address space freelist. The allocation of address spaces depends on the individual operating system design. 
     Address block queue 300 is accessed 242. If PTLB marker is detected 244, a purge TLB instruction is issued 246. If this is an MP complex 248, a PTLB message is sent to the other CPU&#39;s 250. In either case, a PTLB marker is placed at the bottom of the address queue 252 and control returns to step 242 where the next address space block is accessed. If no PTLB marker is detected the address space is allocated 254. Address space deallocation (FIG. 6) performs the work necessary to free the address space step 602. This may include collecting account data, returning resources used by the process to the system. Once the deallocation work is complete, a contact block marker as described above, is placed on the list of free spaces step 604 (the FIFO address queue). 
     It will be understood from the foregoing description that various modifications and changes may be made in the preferred embodiment of the present invention without departing from its true spirit. It is intended that this description is for the purposes of illustration only and should not be construed in a limiting sense. The scope of this invention should be limited only by the language of the following claims: