JPH09282189A - Server program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce the capacity of a memory to be used for a server program, and to enable connection with much more clients by providing server programs A and B respectively equipped with access managing means, and a switching means for switching the server programs A and B. SOLUTION: A switching control means 15 confirms the presence/absence of access request arrival at every monitor time. When the access request does not arrive within the monitor time, a program determining means 14 is called to determine the server program to be executed and continuously, a switching means 13 is called to change the program under executing. When all the access requests do not frequently arrive or when the access requests unprocessable for a server program B30 do not frequently arrive, with such an operation, the user process can execute a server program B30 with the comparatively less capacity of the memory to be used in stead of a server program A20.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a client / server program for sharing resources existing remotely by using a network, and more particularly to a method for reducing the memory used by the server program.

[0002]

2. Description of the Related Art With the spread of personal computers (hereinafter referred to as personal computers), user program files, which are conventionally stored in a storage device for each personal computer,
Data files and the like are stored in a large-capacity storage device at one place, and users of each personal computer share data or access data exceeding the storage device capacity of each personal computer. Generally, a computer called a server and a plurality of personal computers called clients are connected via a network, and data on the server is accessed and used by each client. In a conventional server, a process for processing a service for a client is created each time a connection with each client is established. Hereinafter, this process is called a user process. A process is a virtual reality in which a program is executed inside a computer, and causing a process to start an executable program is called loading. In this way, the main reason for creating a user process for each client is to process access requests from multiple users in parallel to speed up the response, and to prevent a failure caused by processing an access request from a user. This is because the access processing to each user is performed independently so as not to affect other users.

FIG. 4 shows a processing flow of a server main routine 41 in a conventional server program. The routine 41 is a routine started when the conventional server program is started. In the routine 41, after initialization such as initialization of the work memory area is performed in step 4100, a connection establishment request from the client program is waited in step 4101. Upon receiving the establishment request,
In step 4102, a connection with the client program is established. Next, in step 4103, a user process for the client program is generated, and the established connection is handed over to the user process in order to execute the processing of the access request sent from the client program. Then, the process returns to step 4101 to wait for the reception of the subsequent connection establishment request. In this way, the conventional server program has the same number of user processes as the client programs that have established a connection, because a user process is generated for each client program.

FIG. 5 shows a processing flow of a user main routine 42 which is a program first executed by a user process generated by the server main routine 41. The user main routine 42 first performs a login process of the user of the client information processing apparatus in step 4200,
In step 4201, the arrival of an access request from the user is awaited. When the access request arrives, the type of the access request is determined in step 4202. If the access request is the logout request, the logout process is performed in step 4204, and the user main routine 42 ends. Step 4202
If the access request is other than the logout request, the access process is executed in step 4203 and the execution result is sent to the client program. Then, step 42
Return to 01 and wait for an access request.

As an example of such a server program,
JP-A-3-147151 discloses a method of generating a user process for processing an access request from a client program for each client program, and executing each of the user processes a server program having a function for processing all access requests. It is disclosed in the official gazette. By the way, the server program links a library such as a security service program provided by the operating system in order to process the access request. Here, linking means loading the library by linking the library with the program body when the program is executed in order to use the function in the library from the program. When the server program linked with the library is executed, each user process reserves an area on the memory for storing the code and data of the library. This area is generally several Mbytes to several Mbytes.

[0006]

In the conventional example, since the same number of user processes as the number of connected clients are created, the memory usage amount increases proportionally after the clients. Moreover, these user processes constantly use the memory even when waiting for an access request. However, since the information processing device in which the server program is operating has a finite amount of memory that can be installed, there is a problem that many clients cannot be connected when the memory usage of the library linked by the server program is large.

An object of the present invention is to reduce the memory usage of a server program without changing the conventional method of generating one server process for one client and suppressing the deterioration of the response to an access request. , To provide a way to allow connections with more clients.

[0008]

In order to achieve this object, the present invention comprises an access processing means A for processing all access requests sent from a client program, and a switching means for switching between the server program A and the server program B. A program determining means for determining which of the server program A and the server program B should be executed, based on the free memory capacity of the information processing device in which the server program is operating, or the memory usage of the server program, and an access request. Control means for switching the server program so that the arrival of the server program and the switching of the server program do not overlap with each other, the monitoring time which is the period for confirming the arrival of the access request, and the upper limit of the access request issuing frequency that cannot be processed by the server program B Storage means for storing values And the server program A with a,
Excluding the access processing means A from the server program A,
A server program B including an access processing unit B in which a memory usage amount is reduced by omitting a part of a function of processing an access request from the access processing unit A and reducing a library to be linked is provided. The storage unit stores the monitoring time and the upper limit of the access request issuance frequency that cannot be processed by the server program B. The program determining means determines that the server program B should operate when the free space of the memory of the server information processing device is below a predetermined lower limit value, and when the free space is equal to or higher than the lower limit value, the server Decide that program A should work. Alternatively, when the total memory usage of the server program exceeds a predetermined upper limit value, it is determined that the server program B should operate, and when the memory usage is less than or equal to the upper limit value, the server program A operates. Decide that it should. The switching means loads the other server program from the server program A or the server program B and changes the program being executed. The switching control means refers to the access request issuance history for each user, and the access request of the user whose access frequency that the server program B cannot process is less than the value indicated by the upper limit of the issuance frequency is the server program. Accept at B. Then, when an access request that cannot be processed by the server program B arrives, the switching means is called to switch the server program B to the server program A and control the access request to be processed.
On the other hand, only the server program A accepts an access request from a user whose access frequency that the server program B cannot process is less than or equal to the value indicated by the upper limit of the issuance frequency. Further, the switching control means confirms whether or not the access request arrives at each monitoring time, and when the access request does not arrive within the monitoring time, calls the program determining means to determine the server program to be executed, and then the switching means. To change the running program.

By this operation, the user process relatively uses the memory in place of the server program A when all access requests do not arrive frequently or when access requests that cannot be processed by the server program B do not arrive frequently. It is possible to execute the server program B which has a small number. In addition, it is possible to reduce the number of delays in the response of the access request, which occurs when the access request arrives when the server programs are switched. Therefore, it is possible to reduce the memory usage of the server program, suppress the deterioration of the response to the access request, and allow more client programs to connect to the server program.

[0010]

BEST MODE FOR CARRYING OUT THE INVENTION A first embodiment of the present invention will be described with reference to the drawings.

FIG. 2 shows the system configuration of this embodiment. 1s is a server information processing apparatus and 1c is a client information processing apparatus. The server information processing device 1s includes a central processing unit (CPU) 2s, a memory 3s, a magnetic disk 4s, a disk controller 5s, and a LAN controller 6s. When the server information processing device 1s is activated, an operating system (hereinafter referred to as OS) 7
s, file server program 8s is magnetic disk 4s
Is loaded on the memory 3s via the disk controller 5s. On the other hand, the client information processing apparatus 1c includes a CPU 2c, a memory 3c, a magnetic disk 4c, a disk controller 5c, and a LAN controller 6c. When the client information processing apparatus 1c is activated, the OS 7c is loaded from the magnetic disk 4c onto the memory 3c via the disk controller 5c. Further, when a user of the client information processing apparatus 1c (hereinafter, simply referred to as a user) starts the client program 8c, the client program 8c operates from the magnetic disk 4c to the memory 3c via the disk controller 5c.
Loaded on. The server information processing device 1s and the client information processing device 1c are connected by a local area network (hereinafter referred to as LAN) 9 and communicate via LAN controllers 6s and 6c. The outline of the processing of the file server program 8s will be briefly described below.
The file server program 8s realizes an access process from the client information processing apparatus 1c to a file existing on the magnetic disk 4s. The client program 8c sends to the file server program 8s an access request for a file existing on the user's magnetic disk 4s. The file server program 8s receives and processes the access request. Access requests are roughly classified into three types: login / logout requests, file operation requests, and file attribute operation requests. The file operation request is an open request, a close request, a read request, a write request, etc., and the file attribute operation request is a file owner and access attribute reference request and conversion request.
The file server program 8s executes the received access request on the server information processing device 1s, and sends the execution result to the client program 8c.

FIG. 1 shows the programs that make up the file server program 8s in this embodiment and the routines that make up those programs. Here, a routine is a constituent element of a program and is a set of instructions and data for realizing a certain function. The file server program 8s includes a server main program 10, a user service program A20, and a user service program B30. The routines that form the three programs will be described below.

The server main program 10 includes a server main routine 11 for establishing a connection with the client program 8c, a user main routine 12 having a login processing section 80 for processing a login request, and a running server main program 10. The switching routine 13 for changing to one of the two programs and the information storage area 16 for the file server program 8s to hold information are provided on the memory 3s.

The user service program 20 includes a file operation processing unit 81 for processing a file operation request sent from the client program 8c, a file attribute operation processing unit 82 for processing a file attribute operation request, and a logout processing unit for processing a logout request. An access processing routine A21 having 83, a switching routine 13 for changing the running user service program 20 to the user service program 30, and a program to be operated by the user service program 20 or the user service program 30 The information storage area 16 is provided with a program determination routine 14 for executing the switching routine, a switching control routine 15 for determining the timing for calling the switching routine 13, and calling the switching routine 13 to execute switching. That.

The user service program 30 has an access processing routine B3 having only a file operation processing section 81.
1 and a switching routine 1 for changing the running user service program 30 to the user service program 20.
3, a program determination routine 14, a switching control routine 15, and an information storage area 16.

FIG. 3 shows three programs constituting the file server program 8s and a library linked with the three programs. In this embodiment, the file operation function 101 in the library A100 is required to process the file operation request, and the login / logout request and the file attribute operation request are processed respectively.
Login / logout function 20 in library B200
1 and the file attribute operation function 202 are required. Therefore, the server main program 10 links the library B200 in order to process the login request. Further, the user service program 20 links the library A100 and the library B200 in order to process all three types of access requests. On the other hand, the user service program 30 links only the library A100 and does not link the library B200 in order to reduce the memory usage as compared with the user service program 20. Therefore, the login / logout request and the file attribute operation request cannot be processed.

FIG. 6 shows the information recorded in the information storage area 16. The memory free space lower limit value 73 is a value for storing the lower limit value of the free space of the memory 3s, which is a condition when the user service program 20 switches to the user service program 30. The monitoring time 74 is the length of an interval for checking whether or not an access request has arrived. When the access request flag 72 is 1, it indicates that the access request has arrived, and when it is 0, it indicates that the access request has not arrived. The access request flag 72 is the access processing routine A21 and the access processing routine B3.
1 updates. The program number 71 indicates a running user service program. The program number of the user service program 20 is 0, and the program number of the user service program 30 is 1. After the file server program 8s is switched, the access processing routine A21 and the access processing routine B31 set the program number 7 to the number indicating the newly started program.
Set to 1. The user name 70 is the ID of the user who has logged in, and is recorded by the user main routine 12 after the login process.

The administrator of the file server program 8s writes in the parameter file 90 the memory free space lower limit value 73 'and the monitoring time 47' according to the execution environment.
The file server program 8s starts from the parameter file 90 at the time of startup, and the lower limit value 73 'of free memory space and the monitoring time 7
4'is read and recorded in the memory free space lower limit value 73 and the monitoring time 74 of the information storage area 16, respectively.

The flow of processing of each routine will be described below with reference to flowcharts. FIG. 7 shows the flow of processing of the server main routine 11 in this embodiment. Routine 11 is a routine started when the file server program 8s is started. The server main routine 11 performs initialization such as initialization of the working memory area in step 1100, and then in step 1101 the memory free space lower limit value 7 defined in the parameter file 90.
3'and the monitoring time 74 'are read, and the memory free space lower limit value 73 of the information storage area 16 and the monitoring time 7
Set to 4, respectively. Then, in step 1102, the client program 8c waits for a connection establishment request. When the establishment request is received, in step 1103, the connection with the client program 8c is established. Next, in step 1104, the user process 2 is generated, and the established connection is handed over to the user process 2. The subsequent processing of the access request sent from the client program 8c is executed by the user process 2. After that, the process returns to step 1102 and waits for the reception of the subsequent connection establishment request.

FIG. 8 shows the processing flow of the user main routine 12 in this embodiment. User main routine 1
Reference numeral 2 is a routine that is first executed on the user process 2. First, in step 1200, the login request sent from the client program 8c is received through the connection established by the server main routine 11, and the user login processing is performed. Step 120
In step 1, the user name 70 sent from the client program 8c during the login process is written in the user name 71 in the information storage area 16. Next, the open file descriptor held by the running server main program 10 and the information recorded in the information storage area 16 (hereinafter referred to as server information) are stored in the server main program 10.
Since it is used by the user service program 20 even after the end of step 1, the server information is written and saved in the inter-process shared area existing in the memory 3s in step 1202. Next, in order to accept all access requests, step 1
At 203, the user service program 20 is loaded, and the user main routine 12 is ended.

FIG. 9 shows a processing flow of the program determination routine 14. First, in step 1400, the free space of the memory 3s is acquired, and in step 1401, it is confirmed whether or not the free memory space is smaller than the lower limit value 73 of the free memory space held in the information storage area 16. If the obtained free memory capacity is smaller than the lower limit value 73, it means that the memory 3s is insufficient, so it is determined that the user service program 30 having a relatively small memory usage should operate. Thirty
0 which is the program number of is returned. Step 1401
If the free memory capacity is equal to or more than the lower limit value 73, it is determined that the free space in the memory 3s is sufficient, it is determined that the user service program 20 should operate, and in step 1403, the program of the user service program 20 is executed. Returns 1 which is the number.

FIG. 10 shows a processing flow of the switching control routine 15. First, in step 1500, the access request flag 72 in the information storage area 16 is initialized to 0, and in step 1501, the process waits for the monitoring time 74. When an access request arrives during the monitoring time 74, the access processing routine A21 or the access processing routine B31 running in another thread sets the access request flag 72 to 1. After monitoring time 74, step 1
At 502, it is confirmed whether the access request flag 72 is 1,
Check whether there is an access request that arrived after waiting. If the flag 72 is 1, it is considered that there is a high probability that the next access request will arrive soon after this, because the access request has arrived. If an access request arrives during the switching of the file server program 8s, the access request is not received until the switching process is completed. Further, when a file attribute operation request arrives during the switching to the user service program 30, the user service program 20 is immediately sent after the switching process is completed.
Need to switch to. For this reason, in order to avoid delaying the response to the access request, if the flag 72 is 1 in step 1502, the file server program 8s is not switched and step 15 is executed.
Return to 00. If the access request flag 72 is 0 in step 1502, it is considered that the access request does not arrive immediately and the file server program 8s is switched.
In step 1503, the program decision routine 14 is called to decide which of the user service program 20 and the user service program 30 should be operated. Then, in step 1504, it is confirmed whether the return value of the program determination routine 14 is the same as the program number 71 recorded in the information storage area 16. In the present embodiment, the return value of the program determination routine 14 is the program number of the program that should be currently operated. on the other hand,
Program number 7 held in information storage area 16
1 is the program number of the program actually running at this point. If the return value and the program number 71 are the same, there is no need to switch the file server program 8s, and the process returns to step 1501. Step 1
If the return value is different from the program number 71 at 504,
In the next steps,
Switch to the program indicated by the return value. First, in step 1505, the server information is written and saved in the inter-process shared area on the memory 3s. Then, in step 1506, it is confirmed whether the return value is 0. If the return value is 0, the user service program 30 is loaded in step 1507. If the return value is not 0 in step 1506, the user service program 20 is loaded in step 1508.

FIG. 11 shows a processing flow of the access processing routine A21.

When the user service program 20 is loaded on the user process 2, the access processing routine A21 is first started. First, in step 2100, initialization such as initialization of the working memory area is performed,
The server information saved in step 2101 is stored in the memory 3
It is read from the inter-process shared area on s and stored in the data area in the user process 2. The in-process data area is an area that exists on the memory 3s and is a dedicated area for storing data used by the user service program 20. Next, in order to indicate that the program currently being executed is the user service program 20, step 2102 is executed.
Then, the program number 1 of the user service program 20 is set in the program number 71 of the information storage area 16. Then, in step 2103, a new thread is generated and the switching control routine 15 is executed in order to check whether the switching of the file server program 8s can be executed. At step 2104, the access request is waited, and when the access request arrives, the access request flag 72 of the information storage area 16 is set to 1 in order to record the arrival of the access request at step 2105. In step 2106, it is confirmed whether or not the arrived access request is a logout request, and if it is a logout request, logout processing is performed in step 2109, and the user service program 20 is terminated. At this time, the switching control routine 15 operating in another thread also ends. If the access request is not the logout request in step 2106, it is confirmed in the following step 2107 whether it is a file attribute operation request. If it is a file attribute operation request, the file attribute operation is executed in step 2110 and the subsequent access request is issued. To wait, return to step 2104. Step 2
If the access request is not a file attribute operation request at 107, it is a file operation request, so step 2108
To execute the file operation. After that, in order to accept the subsequent access request, the process returns to the access request waiting in step 2104.

FIG. 12 shows the processing flow of the access processing routine B31.

When the user service program 30 is loaded on the user process 2, the access processing routine B31 is first started. First, in step 3100, initialization such as initialization of the working memory area is performed,
In step 3101, the server information saved in the inter-process shared area on the memory 3s is read and stored in the in-process data area. Next, at step 3102, the program number of the user service program 30 is 0.
Is set to the program number 71 in the information storage area 16. Thereafter, in order to check whether the file server program 8s can be switched, a new thread is generated in step 3103 and the switching control routine 15 is executed. When the access request arrives in step 3104 and the access request arrives, the information storage area 16 is recorded in step 3105 to record that the access request is made.
The access request flag 72 is set to 1. Step 3
The type of access request is confirmed at 106, and if it is a file operation request, the file operation is executed at step 3107. After that, the process returns to step 3104 to wait for the subsequent access request. In step 3106, if the access request is an access request other than a file operation, the access processing routine B31 cannot process it.
At 08, the server information is written in the inter-process shared area on the memory 3s, and at step 3109, the user service program 20 is loaded and the access processing routine B is executed.
The user service program 30 including 31 is terminated.
At this time, the switching control routine 15 operating in another thread also ends.

As described above, when the client program 8c does not frequently issue access requests, the user process 2 corresponding to the client program 8c.
Receives an access request by the user service program 30 having a relatively small memory usage. Therefore, if there is a user who does not frequently execute access requests, it is possible to reduce the total memory usage of the file server program 8s, and to increase the number of client programs 8c.
Can simultaneously connect to the file server program 8s.

A second embodiment of the present invention will be described with reference to the drawings.

The system configuration according to the second embodiment of the present invention, the programs and routines constituting the file server program 8s, and the libraries linked with the three programs constituting the file server program 8s are shown in FIGS. 2 and 1, respectively. 3, the system configuration of the first embodiment shown in FIG. 3, the programs and routines constituting the file server program 8s, the file server program 8
It is the same as the library to which the three programs that make up s are linked. The information recorded in the information storage area 16 in the second embodiment, the switching routine 13, the program determination routine 14, and the switching control routine 15 are different from those in the first embodiment.

FIG. 13 shows information recorded in the information storage area 16. The access request history 77 is a history of types and arrival times of access requests issued while the user is logged in. The access processing routine A21 and the access processing routine B31 record the access request history 77 in the information storage area 16. The access processing routine 21 outputs the access request history 77 to the access request history 77 ′ in the access request history file 91 for each user after processing the logout request. The switching flag 76 is set to 1 when the user does not frequently execute the file attribute operation request.
And 0 otherwise. The user main routine 12 refers to the user's access request history file 91 when the user logs in, and sets the switching flag 76 to 1 if the frequency of file attribute operation is low.
The access request flag 72 and the user name 70 are the same as in the first embodiment. The memory usage amount upper limit value 78 is a value for storing the upper limit value of the usage amount of the memory 3s, which is a condition when the user service program 20 switches to the user service program 30. Attribute operation free time 75
Is a value for recording the lower limit of the arrival interval of the file attribute operation request, which is a condition for considering that the user rarely executes the file attribute operation request.

The administrator writes in the parameter file 90 the monitoring time 74 ', the attribute operation free time 75', and the memory usage upper limit 78 'determined according to the execution environment. When the file server program 8s is started, the monitoring time 74 'and the attribute operation free time 7 are read from the parameter file 90.
5 ′ and the memory usage upper limit 78 ′ are read and recorded in the monitoring time 74, the attribute operation idle time 75, and the memory usage upper limit 78 of the information storage area 16, respectively.

The processing flow of each routine will be described below.

Server main routine 1 in this embodiment
1 is the same as the server main routine 11 in the first embodiment shown in FIG.

FIG. 14 shows the flow of processing of the user main routine 12 in this embodiment. The user main routine 12 is a routine executed first on the user process 2. First, in step 5200, the login request sent from the client program 8c through the connection established by the server main routine 11 is received, and the login process for the user is performed. Step 520
1, the user name sent from the client program 8c during the login process is set to the user name 7 in the information storage area 16.
Write to 0. Next, at step 5202, the access request history 77 'in the access history file 91 is referred to, and the minimum value of the arrival interval of the file attribute operation request is checked. If the minimum value exceeds the attribute operation free time 75, it is considered that the user is not likely to execute the file attribute operation, and the user service program 30 that cannot process the file attribute operation request but has a relatively small memory usage is mainly used. In order to indicate use, 1 is set in the switching flag 76 of the information storage area 16 in step 5205. After that, in step 5206, the server information is used in the user service program 20 even after the server main program 10 ends, so the server information is written and saved in the inter-process shared area existing in the memory 3s, and in step 5207, the user service program. 30 is loaded, and the user main routine 12 is ended. In step 5202, if the minimum value is 75 or less for the attribute operation free time,
It is considered that the user is likely to execute the file attribute operation, and in step 5203, like step 5206, the server information is written to the inter-process shared area existing in the memory 3s and saved, and then all access requests are issued. The user service program 20 is loaded at step 5204 for processing and the user main routine 12 is exited.

FIG. 15 shows the program determination routine 14 in this embodiment. The routine 14 is called from the switching control routine 15. First, step 4400
Then, the current memory usage of the entire file server program 8s is acquired, and it is confirmed at step 4401 whether the memory usage is equal to or less than the upper limit value 78 recorded in the information storage area 16. If the memory usage amount is equal to or less than the upper limit value 78 in step 4401, there is a margin in the memory 3s.
1 which is the program number of is returned. In step 4401, if the memory usage amount is larger than the upper limit value 78 recorded in the information storage area 16, the usage amount of the memory 3s exceeds the upper limit value 78, so that another switching condition is confirmed. To do. In step 4402, the access request history 77 is referenced, and the difference value obtained by subtracting the arrival time of the latest attribute operation request from the current time and the attribute operation free time 75
Compare. If the value of the difference is larger than the attribute operation free time 75, it means that the user has an access tendency not to frequently execute the file attribute operation and still does not execute the file attribute operation within the attribute operation free time 75. , It is highly likely that the file attribute operation will not be executed even after this. Therefore, it is determined that the user service program 30 should operate, and in step 4403 the program number 0 of the user service program 30 is returned. In other cases, it is determined that the user service program 20 should operate, and the program number 1 is returned in step 4404.

FIG. 16 shows a processing flow of the switching control routine 15. The switching control routine 15 is called from the access processing routine A21. First, step 4
In 500, the access request flag 72 in the information storage area 16 is initialized by setting 0, and in step 4501, the process waits for a monitoring time 74 to monitor the arrival of the access request. If an access request arrives during the monitoring time 74, the access processing routine A21 running in another thread sets 1 in the access request flag 72. Monitoring time 74
Then, in step 4502, the access request flag 72 is set to 1
Then, after waiting, it is confirmed whether there is an access request that has arrived. If the flag 72 is 1, the access request has arrived, and it is considered that the probability that the access request will arrive soon after this is high. Therefore, in order to avoid the delay of the response to the access request due to the overlap of the arrival of the access request and the switching of the file server program 8s, the switching is not executed in step 45.
Return to 00. If the access request flag 72 is 0 in step 4502, there is no arriving access request and switching can be executed. Therefore, in order to determine which of the user service program 20 and the user service program 30 should operate, In step 4503, the program decision routine 14 is called. Here, the return value of the program determination routine 14 is the program number of the program to be operated at present. Step 450
In step 4, it is confirmed whether the return value is 0, and if the return value is 0, switching to the user service program 30 is performed. First, in step 4505, the server information is written and saved in the inter-process shared area on the memory 3s. Then, in step 4506, the user service program 30 is loaded. If the return value is not 0 in step 4504, both the program currently being executed and the program to be executed are user service programs 20, and there is no need to execute switching, so step 450
Return to 1.

FIG. 17 shows a processing flow of the access processing routine A21. In step 2200, the access processing routine A21 performs initialization such as initialization of the work memory area, and in step 2201, reads the server information saved in the inter-process shared area on the memory 3s and stores it in the in-process data area. Store. Next, in order to confirm whether it is necessary to operate the switching control routine,
In step 2202, the switching flag 76 is referenced. If the switching flag 76 is 1 in step 2202, a new thread is generated and the switching control routine 15 is executed in step 2203 to check whether the switching of the file server program 8s can be executed.
If the flag 76 is not 1 in step 2202, there is no need to switch the file server program 8s, so the flow advances to step 2204. Waiting for the access request at step 2204, and when the access request arrives, step 220
In step 5, the access request flag 72 in the information storage area 16 is set to 1 to record the arrival of the access request. In step 2206, it is confirmed whether the access request is a logout request. If the access request is a logout request, the logout request is processed in step 2210, and step 2211 is executed.
The access request history 7 recorded in the information storage area 16
After outputting 7 to the access request history file 91, the user service program 20 is terminated. At this time, the switching control routine 15 operating in another thread also ends. If the access request is not the logout request in step 2206, it is confirmed in the following step 2207 whether it is a file attribute operation request. If it is a file attribute operation request, the file attribute operation is executed in step 2212, and the access is performed in step 2209. The request type and arrival time are recorded in the information storage area 16 as the access request history 77. After that, in order to accept the subsequent access request, the process returns to the access request waiting in step 2204. On the other hand, if the access request is not a file attribute operation request in step 2207, it is a file operation request, and therefore a file operation is executed in step 2208. Then, in step 2209, the type and arrival time of the access request are recorded in the information storage area 16 as the access request history 77.
After that, in order to accept the subsequent access request, the process returns to the access request waiting in step 2204.

FIG. 18 shows the processing flow of the access processing routine B31. When the user service program 30 is loaded on the user process 2, the access processing routine B31 is first started. First, step 320
At 0, initialization such as initialization of the work memory area is performed, and at step 3201, the server information saved in the inter-process shared area on the memory 3s is read and stored in the in-process data area. Next, in step 3202, an access request is waited for, and when the access request arrives, the access request flag 72 in the information storage area 16 is set to 1 in order to record that the access request is made in step 3203.
Set. In step 3204, the type of access request is confirmed, and if it is a file operation, the file operation is executed in step 3205. Thereafter, in step 3206, the type of the access request and the arrival time are recorded in the information storage area 16 as the access request history 77, and the process returns to step 3202 to wait for the subsequent access request. In step 3204, if the access request is an access request other than a file operation, it cannot be processed by the access processing routine B31. Therefore, in step 3207, the server information is written in the inter-process shared area on the memory 3s, and then step 3
At 208, the user service program 20 is loaded, and the user service program 30 including the access processing routine B31 is terminated. At this time, the switching control routine 15 operating in another thread also ends.

As described above, when the client program 8c does not frequently issue a file attribute operation request or all access requests, the user process 2 of the client program 8c omits the function of processing the file attribute operation request. As a result, the access request is accepted by the user service program 30 whose memory usage is relatively small. Therefore, when there is such a user as described above, the memory usage of the file server program 8s can be reduced, so that more client programs 8c can be connected to the file server program 8s at the same time.

[0040]

According to the present invention, the server program A for processing an access request, the server program B in which a part of the function for processing an access request is omitted from the server program A to reduce the memory usage, and the two programs are mutually By providing switching means for realizing the switching of the access request, program determining means for determining the program to be executed, and switching control means for executing the switching so that the arrival of the access request and the execution of the switching do not overlap with each other, the access request Since the decrease in response is suppressed and the memory usage of the server program is reduced, more client programs can connect to the server program at the same time. In addition, the resources of the server information processing device can be effectively used.

[Brief description of drawings]

FIG. 1 is an explanatory diagram of programs constituting a file server program 8s according to a first embodiment and a second embodiment of the present invention.

FIG. 2 is an explanatory diagram showing a system configuration in a first embodiment and a second embodiment of the present invention.

FIG. 3 is an explanatory diagram of programs constituting a file server program 8s according to the first and second embodiments of the present invention.

FIG. 4 is a flowchart of processing of a server main routine 41 in a conventional example.

FIG. 5 is a flowchart of processing of a user main routine 42 in a conventional example.

FIG. 6 is an explanatory diagram showing information used when the file server program 8s executes switching in the first embodiment of the present invention.

FIG. 7 is a flowchart of the processing of the server main routine 11 in the first and second embodiments of the present invention.

FIG. 8 is a flowchart of processing of a user main routine 12 according to the first embodiment of this invention.

FIG. 9 is a flowchart of the processing of a program determination routine 14 according to the first embodiment of this invention.

FIG. 10 is a flowchart of processing of a switching control routine 15 according to the first embodiment of this invention.

FIG. 11 is a flowchart of processing of an access processing routine A21 according to the first embodiment of this invention.

FIG. 12 is a flowchart of processing of an access processing routine B31 according to the first embodiment of this invention.

FIG. 13 is an explanatory diagram showing information used when the file server program 8s according to the second embodiment of this invention performs switching.

FIG. 14 is a flowchart of processing of a user main routine 12 according to the second embodiment of this invention.

FIG. 15 is a flowchart of the processing of a program determination routine 14 according to the second embodiment of the present invention.

FIG. 16 is a flowchart of processing of a switching control routine 15 according to the second embodiment of this invention.

FIG. 17 is a flowchart of processing of an access processing routine A21 according to the second embodiment of this invention.

FIG. 18 is a flowchart of processing of an access processing routine B31 according to the second embodiment of this invention.

[Explanation of symbols]

 13 ... Switching routine, 14 ... Program determination routine, 20 ... User service program, 30 ... User service program.

Claims (8)

[Claims] 1. A server program for resource sharing, which operates on a server information processing apparatus connected to a client information processing apparatus having a client program by a network, wherein all access requests transmitted from the client program are A server program A having a processable access processing means A, a server program B having an access processing means B capable of processing only a part of an access request sent from the client program, the server program A and the server program A. A server program comprising a switching means for switching between the server program B and the server program B. 2. The program determining means according to claim 1, further comprising: program determining means for determining a server program to be operated based on a free memory capacity of the server information processing device, wherein the switching means is based on information of the program determining means. A server program for performing the switching. 3. The method according to claim 1, based on the memory usage of the entire server program,
A server program comprising a program determining means for determining a server program to be operated, wherein the switching means performs the switching based on information from the program determining means. 4. The switching control means according to claim 1, further comprising storage means for holding a monitoring time, which is a cycle for confirming the arrival of the access request, and switching control means for performing the confirmation. A server program that calls the program determining unit and the switching unit to control the switching when the access request does not arrive within the period indicated by the monitoring time. 5. The server program A and the server program B according to claim 1, 2, 3 or 4.
Is a server program including the switching means, the program determining means, and the switching control means, respectively. 6. The server program according to claim 1, 2, 3 or 4, wherein the server program B has a smaller memory usage at the time of execution than the server program A. 7. The storage device according to claim 1, 2, 3, 4, 5 or 6, further comprising: storage means for storing an upper limit value of the issuance frequency of access requests that cannot be processed by the server program B. If the access request issuance history of the user of the information processing device is referred to, and the issuance frequency of the access request that cannot be processed by the server program B is below the value indicated by the upper limit value, the access request issued by the user is A server program which is accepted by the server program B and, when an unprocessable access request arrives, calls the switching means to switch the server program B to the server program A and control the access request to be processed. 8. The switching control means according to claim 1, when the user of the client information processing device does not issue an access request for a period indicated by the monitoring time. A server program that calls a switching means to switch the server program A to the server program B, and controls the server program B to accept an access request issued by the user.