JPH01116851A - Program load control system - Google Patents

Abstract

PURPOSE:To shorten the load time of an LM (Load Module) furthermore by deciding the LM to be quickly loaded based on a resident segment information table. CONSTITUTION:When load of an LM is requested to a quick load deciding means 300, this means 300 searches the requested LM name in a quick load LM state table 202. If an entry having this LM name is found and a quick load flag 2023 of this entry is set, an LM resident part copy means 301 is called; but if the quick load flag 2023 is reset, an LM load means 302 is called. The LM resident part copy means 301 uses a resident segment preliminarily loaded to a resident segment area based on the resident segment information table in an LM resident part information area 203 and copies the resident segment to a quickly loaded virtual storage area 204. Thus, the program which is frequently used is quickly loaded.

Description

DETAILED DESCRIPTION OF THE INVENTION [Field of Industrial Application] The present invention relates to a program load control method in a combiator system that employs a multiple virtual memory method.

[Conventional technology]

Conventionally, in this type of program load control system, a program is loaded from a program library into a virtual storage area every time there is a request to load a program. However, if the program is reentrant, there is a technique in which the program is loaded into the system shared virtual storage area in advance when the computer system is started up, and the program is not loaded every time a program is requested to be loaded.

[Problem that the invention seeks to solve]

In the conventional program load control method described above, in the case of a program other than a reentrant program or a reentrant program that is not loaded into the system shared virtual storage area at system startup, the load request for that program is Each time there is a program, each record of the program is read from the program library and loaded into the virtual storage area, which poses a problem in that high-speed loading is not possible and the performance of the computer system is degraded. In particular, in the case of a program that is used by many users at the same time on a computer system, the loading process of the program is often executed at the same time, so that the increase in loading time and the decrease in system performance become more noticeable.

The present invention solves these conventional problems, and its purpose is to enable frequently used programs to be loaded at high speed.

[Means for solving problems]

In order to achieve the above object, the present invention provides a program load control method in a computer system that employs a multiple virtual memory method, in which L M (
Input the LM from the LM library to the Load Module, create a preload LM in the backing store, and input the created preload LM.
LM preload means for registering management information of the LM in a preload LM table, and based on the preload LM table and the fast load LM status table, loads the resident segment of the LM into the system shared virtual storage area, and registers the management information of the loaded resident segment. LM resident section row 1 means for registering the LM resident segment information table in the resident segment information table; high-speed load determination means for determining whether or not high-speed loading is possible based on the resident segment information table in response to the LM load request; When the determining means determines that high-speed loading is possible, the system shared virtual memory t! Create a fast-loaded virtual storage area by copying resident segment 1 on the area L
M resident unit copying means, and absent segment processing means for loading absent segments generated by execution of the program in the high-speed loaded virtual storage area into main memory.

[Effect]

For M that contains a resident segment that should be loaded at high speed, input the LM from the LM library using the LM preload means, create a preload LM corresponding to that LM in the backing store in advance, and determine what kind of preload LM is. Management information such as whether it exists is registered in the preload LM table.

When the LM resident section low-1 means is activated, which preload L
Based on the fast load LM status table that holds information such as whether the resident segment of M is loaded into the system shared virtual storage area and the preload LM table, the resident segment of the corresponding LM is loaded from the backing store to the system shared virtual storage area. Load it into the storage area, and register the management information of this loaded resident segment in the resident segment information table.

After that, when an LM load request occurs, the high-speed load determination means determines whether or not high-speed loading is possible based on the resident segment information table, and if high-speed loading is possible, the LM
Resident section copying means creates a high-speed loaded virtual storage area by copying the corresponding resident segment on the system shared virtual storage area based on the resident segment information table. Also, absent segments generated by execution of programs in the high-speed loaded virtual storage area are loaded from the backing store to the main memory by the absent segment processing means. Note that when the high-speed load determining means determines that high-speed loading is not possible, loading is performed in the same manner as in the prior art.

〔Example〕

Next, embodiments of the present invention will be described with reference to the drawings.

FIG. 1 is a block diagram of an embodiment of the present invention. In this embodiment, a magnetic disk device 100. LM preload means 1
02. LM resident section loading means 103. Magnetic disk device 104. Absent segment processing means 10 days, virtual storage area 200. High-speed load determination means 300. LM resident section copying means 301 and conventional LM loading means 302
Contains. Additionally, the magnetic disk device 100 includes an LM
LM library 10 that stores multiple LMs such as IOlo
1 is stored, and the magnetic disk device 104 has a banking store area 105 and a preload LM table 106 that store a plurality of preload LMs such as the preload LM 1051.
A backing store file 107 having the following information is stored. Further, the virtual storage area 200 includes a system-coexisting virtual storage area 201 and a high-speed loaded virtual storage area 204, and the system-shared virtual storage area 201 includes a high-speed loaded L
M status table 202. There is an LM resident part information area 203, and a high-speed loaded virtual storage area 204 contains the LM resident part 20.
5. There is an LM non-resident part 206. The LM resident section information area 203 includes a resident segment information table 5000. A resident segment area 5010 is included.

FIG. 2 shows an example of the configuration of one entry in the preload LM table 106. The preload LM table 106 has a plurality of entries, and one entry 1060 includes the LM name area 1061 and the preload LM address as shown in FIG. 1062
Consists of.

FIG. 3 shows an example of the configuration of one entry in the fast load LM status table 202. The high-speed load LM status table 202 has a plurality of entries, and one entry 2020 is in the LM name area 2021. as shown in FIG. Resident segment information table 5
It consists of an address 2022 to 000 and a fast loaded flag 2023. For LMs that are desired to be loaded at high speed, the LM name is set in advance in the high speed load LM status table 202.

FIG. 4 shows an example of the format of the resident segment information table 5000. The resident segment information table 5000 has a plurality of entries, and one entry 2032 has a resident segment number 2033. as shown in FIG. Address 2034 to resident segment area and resident segment size 2
035, and the number of entries 2031 in the resident segment information table 5000 is added.

FIG. 5 shows an example of the configuration of one preload LM 1051 created in the backing store area 105.
In the case where the preload LM has a multi-process configuration, a collection of processes is called a process group, and a process group control segment 3000 is provided to control this. Further, process control segments 3010 and 3030 are provided to control each process. Here, process control segment 3010 is for process 1, and process control segment 3030 is for process 2. Further, in FIG. 5, 3021 and 3022 are segments for process l, 3041 and 3042 are segments for process 2, and 3011 and 3012 are segment descriptors of segments 3021 and 3022 for process l, respectively.
．． 3032 are segments 3041.3032 for process 2, respectively.
3042 segment descriptor, 3001 is a pointer to the process control segment 3010 for process 1, 30
02 is the process control segment 3030 for process 2
is a pointer to . In this example, for convenience of explanation, the fifth
Among the segments shown in the figure, segment 3042 is a non-resident segment, and other segments 3000, 3010
, 3021.3022.3030.3041 are the resident segments. Further, whether or not the segment is a resident segment is specified by, for example, a segment header.

FIG. 6 shows an example of the structure of the segment descriptor 3011, etc.
As shown in the figure, one segment descriptor 4000 is
Segment existence flag 4001. segment address 4
002 and segment size 4003.

FIG. 7 shows a resident segment information table 500 when the LM resident section loading means 103 loads the resident segment of the preload LM 1051 into the system shared virtual storage area 201.
FIG. 5 is a diagram showing the contents of 0 and a resident segment area 5010 and the relationship between the two. As shown in the figure, the resident segment area 501O includes a plurality of areas 5011 to 5016, and the process group control segment 3000. Process control segment 3010 for process 1 in area 5012. Process control segment 3030 for process 2 in area 5013. Area 501
4. Segment 3021゜3 for process 1 in 5015
022, and a segment 3041 for process 2 in area 5016, respectively, in the banking store area 105.
is copied from the preload LM 1051 and stored. Also, the resident segment information table 5000 corresponding to this resident segment area 5010 is the resident segment information table entry 5002 for the process group control segment 3000 of the minirea 5011. Areas 5012 and 5013
Resident segment information table entries 5003 and 5004 for process control segments 3010 and 3030 for process 1 and process 2. Areas 5014 and 50
Resident segment information table entries 5005 and 500 for segments 3021 and 3022 for process 15
6. Segment 3 for process 2 in area 5016
Resident segment information table entry 5007 for 041
．． and the number of resident segment information table entries 5001.

FIG. 8 shows how the high-speed loaded virtual storage area 204 is created using the LM resident part copying means 301 and the LM resident part information area 203, using the preload LM 1051 as an example. The LM resident section copying means 301 copies the resident segment area 50 according to the resident segment information table 5000 as explained in FIG.
By copying the contents of process group control segment 3000 .
Process control segment 3010 for process 1. Process control segment 3030 for process 2. Segment 1-3021.3022 for process l. Create segment 3041 for process 2. As shown in FIG. 8, the fifth non-resident segment in the process LM1051
Segment 3042 in the figure is the high-speed loaded virtual storage area 2
It is not copied to 04.

Next, the overall operation of this embodiment will be explained.

In FIG. 1, the LM preload means 102 inputs the LMIOIO in the LM library 101, creates (loads) an executable preload LM 1051 as shown in FIG. 5 in the banking store area 105, and Each segment descriptor 3011.3012. in that preload LM1051. ..., 3031.30
The segment existence flag 4001 in 32 is set to an absent state, the segment address 4002 is set to the address of the corresponding segment in the backing store file 107, and the segment size is set to the size of the segment in question. Further, when the LM preload means 102 creates the preload LM 1051, the LM preload means 102
By repeating the process of registering necessary items in one entry in the preload LM table 106 shown in FIG. A preload LM is created.

Next, the LM resident section row 1 means 103 is activated, and it performs the following operations as exemplified by the preload LM 1051 for each LM designated by each entry in the fast load LM status table 202.

(Entries consisting of the 11 high-speed load LM status table 202, in this case, the LM name area 2021 shown in FIG. 3 in the entry corresponding to the preload LM1051)
Obtain the LM name of M1051 and preload L with this LM name.
Search M table 106.

(2) If the same LM name is found, Prelow 11M1
The resident segment information table 5000 for 051 and the resident segment area 5oto are stored in the system shared virtual storage area 201.
The segment allocated as a resident segment among the segments in the corresponding preload LM1051.
(In the current example, process group control segment 3000, process control segment 3010.3030. segments 3021, 3022.3041) are stored in the resident segment area 501 of the system shared virtual storage area 201.
0, and set the necessary information in the resident segment information table 5000 as shown in FIG. 7 or 8.

At this time, the high-speed loading flag 2023 is turned on to indicate that the file has been loaded.

As a result of the above, the LM resident segment to be loaded at high speed has been prepared in the system shared virtual storage area 201.

After that, when a request to load the LM is made to the high-speed load determining means 300, the high-speed load determining means 300 performs the following:
First, the high-speed load LM status table 202 is
If an entry with the same LM name is found and the fast loaded flag 2023 of that entry is on, the LM resident section copying means 301 is called, and even if the entry is not found or found, the fast loaded flag 2023 is turned on.
23 is off, the conventional LM loading means 302 is called.

When the LM resident section copying means 301 is called, it copies the resident segments that have been loaded in advance into the resident segment area based on the resident segment information table in the LM resident section information area 203 for the specified LM. , copies the resident segment to fast-loaded virtual storage area 204.

On the other hand, when the conventional LM loading means 302 is called, the L
Transfer the corresponding LM from the M library 101 to the virtual storage area 200
Load into.

The absent segment processing means 108 also processes absent segments that occur due to accessing segments that do not exist in the main memory among the segments in the LM non-emergency section 206 while the program in the high-speed loaded virtual storage area 204 is being executed. Load the segment from the backing store SJ[1os into main memory and re-execute the instruction that caused the absent segment exception.0 For example, preload LM1051
In this case, since segment 3042 is a non-resident segment, if segment 3042 is not in the main memory, an absent interrupt occurs, and the absent segment processing means 108 transfers segment 3 from the banking store area 105 to the main memory.
042 is loaded.

Next, LM preload means 102. LM resident section loading means 103. High-speed load determination means 300. LM resident section copying means 301 and absent segment processing means 108
Regarding the more detailed operation of
The explanation will be made according to FIGS. 10, 11, 12, and 13.

(Operation of LM preload means 102; see FIG. 9) (1
) Flow 7000 When the LM name of the LM to be preloaded is given from the outside, the LM preload means 102 obtains it as the LM name to be preloaded.

(2) Flow 7001 Preload LM table 106 with the LM name obtained in flow 7000
Search for.

(3) Flow 7002 It is determined whether the corresponding LM name is found in the Brillo rLM table 106. If found, the process advances to flow 7005; if not, the process advances to flow 7003.

(4) Flow 7003 8 The relevant LM, for example, LMIOIO, is stored in the LM library 101
The data is manually preloaded into the backing store area 105 as a preload LM 1051. The preload procedure is as follows with reference to FIG.

(a) Create a process group control segment 3000 in the main storage area.

(According to the BL LM information, a process control segment 3010 for process 1 and a process control segment 1-3030 for process 2 are created in the above Ml fiI area. At this time, the process control segment contains a segment descriptor for each segment. 3011.3012...
・Create 3031.3032.

tel Pointer 3 to process control segment 3010.3030 in process group control segment 3000
Set 001.3002.

(Create a segment 3021 in the main storage area according to the segment information in dl LM, input the contents of the corresponding segment from LMIOIO, and add this to segment 3021.
Stored in 021. Then, this segment 3021 is stored in the backing store area 105. At this time, the segment existence flag 400 of the segment descriptor 3011
1 is set off and segment address 4002 is placed at an address within backing store area 105.

Below, the above procedure is applied to all segments in LM') 30
This is done for 22nd grade.

(81 Finally, process group control segment 3000° process!If13I segments 3010 and 3030 are stored in backing store area 105, and these segment descriptors are also set in the same way as +d+.

(5) Flow 7004 Information regarding the LMIOIO preloaded in flow 7003 is registered in the preload LM table 106. This is done by obtaining a free preload LM table entry 1060, storing the LM name in the LM name area Mi 1061, and setting the address in the backing store area 105 of the process group control segment 3000 in the preload LM address 1062.

(6) Flow 7005 A message indicating that the specified LM has already been registered is output to, for example, the console.

(Operation of LM resident section loading means 103; see FIG. 10)
(1) Flow 8000 Positioned as the first entry in the high-speed load LM status table 202.

(2) Flow 8001 Checks whether processing of all entries in the high-speed load LM status table 202 has been completed. If all entries have been completed, the process ends; otherwise, the flow advances to flow 8002.

(3) Flow B002 Obtain the LM name from the entry currently in focus.

(4) Flow 8003 Brillo FLM table 106 with the LM name obtained in flow 8002
Search for.

(5) Flow 8004 Checks whether the corresponding LM is found in the preload LM table 106. If it is not found, the high-speed load completed flag 2023 in the entry currently under consideration in the high-speed load LM status table 202 is turned off and the flow advances to flow 8008; if it is found, the flow advances to flow 8005.

(6) Flow 8005 The preload LM address 1062 is obtained from the entry in the preload LM table 106 found in flow 8003.

(7) Flow 800θ Preload LM address 10 obtained in flow 8005
62 loads the process group control segment 3000 of the preload LM 1051 on the backing store area 105 into the main storage area.0 Next, the process control segments 3010 and 3030 are loaded into the main storage area.

Then, the LM resident section information area 203 is secured within the system-coexisting virtual storage area 201. Set the necessary information in this area according to the following steps.

la) Move the process group control segment 3000 to a predetermined position in the LM resident information area 203 (5011 in FIG.
) and resident segment information table entry 5.
The resident segment number, address to the resident segment area, and resident segment size are set in each area 2033, 2034, and 2035 of 002.

(bl process control segment 3010, 3030
Similarly to (al), copy it to a predetermined position M in the LM resident section information area 203 (position 5012.5013 in FIG. 8), and create the resident segment information table entry 5003.5.
Set the resident segment number, its address, and its size in 004.

(other resident segments of the C1 process (in the current example,
For process l, segments 3021.3022. For process 2, segment 3041) is set to LM resident information II f
A predetermined position in the il area 203 (5014 for process 1.
5015, 5016 for process 2), and the resident segment number, its address, and its size in the resident segment information table entry (5005. for process 1).
5006, 5007 for process 2).

When the above processing is completed, the high-speed load completed flag 20 in the currently focused entry of the high-speed load LM status table 202 is
Turn on 23.

(8) Flow 8007 Positions the next entry in the high-speed load LM status table 202 and returns to flow 8001.

(9) Flow 8008 Display the error message on the console etc., and
Proceed to 07.

(Operation of high-speed load determining means 300; see FIG. 11) (
1) Flow 9000 Obtain the LMOLM name for which the load request was made.

(2) Flow 9001 Search the high-speed load LM status table 202 using the LM name obtained in flow 9000.

(3) Flow 9002 g Checks whether or not the relevant entry has been found. If found, the process advances to flow 9003; otherwise, the process advances to flow 9005.

5(4) Flow 9003 Check the high-speed load completed flag 2023 in the entry of the high-speed load LM status table found in flow 9001, and if this flag is on, proceed to flow 9004, and if it is off, proceed to flow 9005.

(5) Flow 9004 LM resident section copy means 301 is called.

(6) Flow 9005 Call the conventional LM loading means 302.

(Operation of LM resident section copying means 301; see FIG. 12) (
1) Flow 10001 The address 2022 to the resident segment information table 5000 is obtained from the entry in the fast load LM status table 202 corresponding to the LM name notified from the fast load determining means 300, for example, the LM name corresponding to the preload LM 1051.

Then, from this address, the resident segment information table 5oo
get o.

(2) Flow 10002 As shown in FIG. 8, the high-speed loaded virtual storage area 204
In order to create the process group control segment 3000, the resident segment information table entry 5002 for the process group control segment 3000 is passed to the 5OCR procedure (flows 10020 to 10023).

(3) Flow 10003 In order to create process control segments for all processes in the fast-loaded virtual storage area 204 using the steps from flow 10004 to flow 10006, the resident segment information table entry of the first process for the first process control segment is position.

(4) Flow 10004 Checks whether all processing for the process control segment has been completed. When all processing is completed, the process advances to flow 10007; otherwise, the process advances to flow 10005.

(5) Flow 10005 In order to create process control segments 3010 and 3030 in the fast-loaded virtual storage area 204, resident segment information table entries 5003 and 5004 for the process control segments are passed to the 5OCR procedure.

(6) Flow 10006 Position the next resident segment information table entry and return to flow 10004.

(7) In order to create all resident segments 3021, etc. in flow 11000 7L in the high-speed loaded virtual storage area 204, locate the resident segment information table entry of the first resident segment.

(8) Flow 10008 Checks whether processing for all resident segment information table entries has been completed. If completed, this procedure ends; otherwise, the process advances to flow 10009.

(9) Flow 10009 In order to create all the resident segments 3021 etc. in the high-speed loaded virtual storage area 204, resident segment information table entries 5005 and 5006 for the resident segments,
5007 in turn to the 5OCR procedure.

(10) Flow 10010 Positions the next resident segment information table entry and returns to flow 10008.

(11) Flow 10020 The corresponding resident segment information table entry 2032 is obtained.

(12) Flow 10021 Resident segment number 2033 from its entry 2032
゜Resident segment) Address 2034 to 8M area. Obtain resident segment size 2035.

(13) Flow 10022 Create a resident segment area in the high-speed loaded virtual storage area 204.

(14) Flow 10023 Copies the contents of the resident segment indicated by address 2034 to the area of the resident segment created in flow 10022.

(Operation of absent segment processing means 108; see FIG. 13) (1) Flow 11000 Obtain the segment number in which the absent segment exception has occurred.

(2) Flow 11001 Segment descriptor 400 corresponding to that segment number
Get 0.

(3) Flow 11002 A segment address 4002 in the banking store area 105 is obtained from the segment descriptor 4000.

(4) Flow 11003 Load the corresponding segment from the backing store area 105 into the main memory using the segment address 4002.

(5) Flow 11004 Turn on the segment existence flag 4001 of the corresponding segment descriptor 4000.

(6) Flag 11005 Re-executes the instruction that caused the missing segment exception.

〔Effect of the invention〕

As explained above, the present invention creates a preload LM for an LM containing frequently used resident segments and stores it in the backing store, and loads the resident segment into the system shared virtual storage area. Then, when there is a load request for that LM, a high-speed loaded virtual storage area is created by copying the resident segment that has been loaded in advance into the system-coexisting virtual storage area, and the following effects are achieved. can be obtained.

■ Since the LM record is not input from the program library and the LM is manually loaded directly from the system shared virtual storage area, the loading time of the LM becomes faster.

■ In particular, when many load requests for the same LM occur at the same time, there is a high probability that the resident segment of that LM that exists in the system shared virtual storage area exists in the main storage area due to the previous load request. , the probability of issuing input/output requests to the disk device (backing store) is lowered, and the LM load time is even faster (greater than 0), so the decrease in system performance due to LM loading is kept to a minimum. There is an effect that can be done.

[Brief explanation of the drawing]

FIG. 1 is a configuration diagram of an embodiment of the present invention, FIG. 2 is a configuration diagram of one entry in the Brillo FLM table 106, FIG. 3 is a configuration diagram of one entry in the high-speed load LM status table 202, and FIG. is a diagram showing an example of the format of a resident segment information table, FIG. 5 is a configuration diagram of the preload LM1051, FIG. 6 is a configuration diagram of a segment descriptor, and FIG. 7 is a diagram of the relationship between the resident segment information table and the resident segment area. FIG. 8 is an explanatory diagram of the operation of the LM resident section copying means 301, FIG. 9 is a flowchart of a processing example of the LM appreading means 102, FIG. 10 is a flowchart of a processing example of the LM resident section loading means 103, and FIG. 11 is a high-speed load FIG. 12 is a flowchart of a processing example of the determining means 300, FIG. 12 is a flowchart of a processing example of the LM resident section copying means 301, and FIG. 13 is a flowchart of a processing example of the absent segment processing means 108. In the figure, 100, 104...magnetic disk device lot...L
M (load module) library 102...LM preload means 103...LM resident section loading means 105...Banking store area 106...Preload LM table 107...Banking store file 10B...Absent segment Processing means 200...Virtual storage area 201...System shared virtual storage area 202...Fast load LM status table 203...LM resident information area 204...High speed loaded virtual storage area 205... L
MM resident section 206...LMM resident section 300...High speed load determination means 301...LM resident section copy means 302...Conventional LM load means 1010...LM 1051...Preload LM

Claims (1)

[Claims] In a program load control method in a computer system that adopts a multiple virtual memory method, for an LM that should be loaded at high speed, the program is loaded from an LM library.
LM preload means for inputting M to create a preload LM in a backing store and registering management information of the created preload LM in a preload LM table; LM resident part loading means for loading a segment into a system shared virtual storage area and registering management information of the loaded resident segment in a resident segment information table; a high-speed load determination unit that determines based on a resident segment information table; and when the high-speed load determination unit determines that high-speed loading is possible, copies the resident segment on the system shared virtual storage area based on the resident segment information table. LM creates a fast-loaded virtual storage area by
A program loading control method comprising: a resident section copying means; and an absent segment processing means for loading an absent segment generated by execution of a program in the high-speed loaded virtual storage area into main memory.