JPH07244627A - Request control unit - Google Patents

Abstract

PURPOSE:To reduce the overhead of the generation and start of processing parts which perform request processings and eliminate the upper limit of the number of accepted requests as to a system which accepts plural requests and performs processings corresponding to them. CONSTITUTION:The request processing parts 403-406 are previously generated and held in a wait state. As a request is received, a request reception part calls a request control part. The request processing part start part in the called request control part actuates the request processing parts 403-406. At this time, when there is no request processing part to be actuated at this time, a request processing part generation part generates a new request processing part. Then the actuated request processing part performs a processing for the request and when the processing ends, the processing of a request control unit 401 ends.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a request control device, and more particularly to a system in which a plurality of clients and servers are connected via a network, and the clients request requests from the server. To
Multiple processes that process requests at startup etc. are created in advance and made to wait, and even if more than that number of requests are requested by the client, it is possible to process all requests in parallel. Regarding the control device.

[0002]

2. Description of the Related Art First, a client-server system which is the object of the present invention will be described with reference to FIG. FIG. 1 is a diagram showing a state in which a server and n clients are connected via a network, the client requests a server for a request, and the server processes the request. First, the configuration will be described. The server 101 is an information device that processes requests from multiple clients, and is a PC (Personal).
Computer), WS (Work Status)
n) etc., and the disk 102 is connected. The disk 102 is a storage device including a file 107, a file 108, and a file 109, and each file is a client 103,
It is accessed from the clients 104 and 105. Client 103, Client 104, Client 10
Reference numeral 5 denotes an information device that makes a request to the server 101, such as a PC or WS. Network 106 is server 101
It connects a client and a client, and generally, Ethernet and FDDI (Fiber Dis) are used.
There is a Tributed Data Interface). Ethernet is a registered trademark of Xerox. Next, the processing will be described. First Client 103
Files on disk 102 connected to server 101
In order to access (read and write data) 107, a request request is made to the server 101. After receiving the request, the server 101 issues an access request to the disk 102. Then, the disk 102 executes the requested processing, and the processing for the request ends. Request requests from the clients 104 and 105 are similarly made. Here, when the files accessed by the client are independent as shown in FIG. 1, the processing of the server 101 and the processing of the disk 102 are performed in parallel.
Therefore, by providing the server 101 with a mechanism for receiving a plurality of requests and processing the requests, the requests from the client 103, the client 104, and the client 105 can be processed in parallel. Conventionally, two methods have been used to realize parallel processing.

The first is a method in which a process for processing a request is newly generated in response to the acceptance of the request, and the process is caused to perform the processing. A process is the substance of a program running on a computer. This method is based on the "UNIX NET" of PRENTICE HALL.
WORK PROGRAMMING ”, and the main ones are
Telnet, ft operating on CP / IP protocol
There are p etc. Here, the processing by this method will be described with reference to FIG. FIG. 2 shows an example of a case where the request receiving unit 201 is provided in the server 101 of FIG. 1 to receive n requests and process the requests. First, the request receiving unit 201 receives n requests. Next, the request receiving unit 201 includes n request processing units (request processing unit 202, request processing unit 203, ...
The request processing unit n204) is sequentially generated. Then, after the request receiving unit 201 registers the request in the request processing unit, the request processing unit starts processing for the request. The request processing unit that has completed processing is deleted by the request receiving unit 201, and the series of processing for the request ends. By thus generating the request processing unit as needed, it is possible to communicate with an unspecified number of opponents.

The second is a method in which a plurality of daemons for processing a request are generated in advance and waited, and when a request is accepted, a daemon on standby is activated and the daemons perform the processing. A daemon is a process that is created when a machine is started up, waits for a processing request, and waits again when the processing ends. This method is described by ASCII publisher "NFS and NI
S ”, and the main ones are NFS (Network Fi
le System). Note that NFS is a registered trademark of Sun Microsystems. Here, the processing by this method will be described with reference to FIG. FIG. 3 shows the server 10 of FIG.
This is an example of a case where the request receiving unit 301 is provided in 1, the m daemons are generated and made to stand by in advance, and the n requests are received and the requests are processed. First, the request receiving unit 301 sets m when the server starts up.
Request processing unit group 305 (request processing unit 302, request processing unit 303, ..., Request processing unit 304) is generated, and all of them are placed in a standby state. Next, the request receiving unit 301 that has received n requests activates the request processing unit group 305 on standby. Then, the activated request processing unit group 305 performs a process for the request, the request processing unit that has completed the process returns to the standby state again, and the series of processes for the request ends. By thus generating and waiting a plurality of request processing units in advance and activating them, it is not necessary to generate the request processing process each time a request is received, and the overhead required for generation can be reduced.

[0005]

When the client / server system is constructed by the above-mentioned two methods of the prior art, there are the following problems.

In the case of the first process generation method, since the process is generated, processed, and deleted each time a request is received, the overhead of those processes deteriorates the processing performance.

In the case of the second process standby activation method, only the number of requests generated and waited in advance can be accepted, and even if there is the ability to process the requests, the number of requests or more is exceeded. Cannot process the request of.

An object of the present invention is to solve the above problems.

[0009]

In order to solve the above problems, the following means are provided in addition to the conventional system.

A request receiving section for accepting requests, a processing section management table for registering the states of a plurality of request processing sections that have been generated and made to stand by in advance, a request processing section starting section for starting the request processing section, A request control unit including a request processing unit generation unit that newly generates a request processing unit when all the request processing units that have been generated and waited are being processed.

[0011]

First, the request control unit registers a state of the request processing unit by generating and waiting a plurality of request processing units and registering them in the processing unit management table. Next, the request receiving unit receives the request and calls the request control unit. Next, the request processing unit activation unit in the called request control unit refers to the processing unit management table and activates the request processing unit. If there is no request processing unit to be activated, the request processing unit generation unit generates a new request processing unit and registers it in the processing unit management table. The activated request processing unit processes the request, and when the processing is completed, updates the processing unit management table in the request control unit. When the update is completed, the request processing unit enters the standby state again, and the processing of the request control device ends.

[0012]

EXAMPLES An example of the present invention will be described below.
In this embodiment, it is assumed that the number of request processing units that are previously generated and made to stand by is four.

First, the request control device is provided with a CSS (Client Se) which is composed of a server and a plurality of clients.
The case of implementation in the Rever System) will be described with reference to FIG. FIG. 4 shows that the request control device 401 is provided in the server 101 of the client server system of FIG.
FIG. 11 is a diagram showing a state in which the server 101 performs request processing in parallel by generating and waiting a request processing unit group 402 including four request processing units in advance.
First, the configuration will be described. The server 101 is an information device that processes requests requested by a plurality of clients, and includes a PC and WS. The server 101 also includes a request control device 401 and a request processing unit group 402 including a plurality of request processing units, to which the disk 102 is connected. The request control device 401 manages the request processing unit group 402. The request processing unit group 402 includes a request processing unit 403, a request processing unit 404, a request processing unit 405, and a request processing unit 406. The request processing unit generates and waits the number specified by the user when the machine is started up, and each process the request. Disk 102 has file 107, file 10
8 files 109, each of which is client 103,
It is accessed from the clients 104 and 105. Client 103, Client 104, Client 10
Reference numeral 5 denotes an information device that makes a request to the server 101, such as a PC or WS. Network 106 is server 101
And Ethernet and FDDI are common ones for connecting the client and the client. Next, the processing will be described. First, the client 103 makes a request request to the server 101 to access (read or write data) the file 107 of the disk 102 connected to the server 101. After the server 101 receives the request, it passes the request to the request control device 401,
The request control device 401 is activated. The activated request control device 401 assigns a request to the request processing unit 403 in the waiting request processing unit group 402, passes the request to the request processing unit 403, and activates the request processing unit 403. The activated request processing unit 401 issues an access request to the disk 102 as processing for the request. Then, the disk 102 executes the requested processing, and the processing for the request ends. Similarly, the client 104 accesses the file 109 by the request processing unit 404, and the client 105
The file 108 is accessed by the request processing unit 405. At this time, if all request processing units are running,
The request control device 401 newly generates a request processing unit and causes it to process it. Therefore, there is no upper limit to the number of requests that can be received. In addition, since the request processing unit is limitedly activated for accepting a request, unnecessary activation of the request processing unit does not occur.

Next, the request control device will be described with reference to FIGS.
This will be described with reference to FIG.

First, the overall structure will be described with reference to FIG. FIG. 5 is a diagram showing the structure of the request control device 401 provided in the server 101 of FIG. 4 and the operation when receiving a request. The request receiving unit 501 receives a request and calls the request control unit 502. The request control unit 502 includes a processing unit management table 503, a request processing unit activation unit 504, and a request processing unit generation unit 505, and manages the request processing unit group 402. The state of the request processing unit group 402 is registered in the processing unit management table 503. The request processing unit activation unit 504 activates one request processing unit in the request processing unit group 402 and updates the processing unit management table according to the processing unit management table 503. The request processing unit generation unit 505 generates a new request processing unit 508 and adds it to the processing unit management table when all the request processing units prepared in advance are activated. The request processing unit group 402 includes a request processing unit 403, a request processing unit 404, a request processing unit 405, and a request processing unit 406. Request processing unit 403, request processing unit 404, request processing unit 405, request processing unit 40
6 performs processing for the request and updates the processing unit management table.

The structure of the processing unit management table 503 and its registration example will be described with reference to FIG. FIG. 6 is a diagram showing the structure of a processing unit management table 503 that manages four request processing units. The processing unit management table 503 includes a processing unit name storage area 601 for registering a request processing unit name,
Status area 60 for registering the current status of the request processing unit
Composed of two. In the processing unit name storage area 601, an example in which a name is registered is given here as the case where activation can be performed by name. However, when the activation is performed by other than the name, the object indicating the activation destination may be registered, and examples thereof include the position of the processing unit (address on the memory). Status area 60
The state managed by 2 is R (Run) indicating that it cannot be activated because it is currently activated, and F (Free) that indicates that it can be activated because it is currently waiting.
There are two types. In the case of FIG. 6, the request processing unit 1 is active, and the request processing unit 2, the request processing unit 3, and the request processing 4 are on standby (free request processing unit). Further, at the time of initialization, the status areas 602 of all request processing units can be activated in F. In this way, by registering in the processing unit management table 503, the state management of the request processing unit group 402 is performed, and the request processing unit is activated, new generation, etc. are performed using it.

Initialization of the request processing unit group 402 performed by the request control unit 502 will be described with reference to FIG. FIG. 8 is a diagram showing an initialization flow of the request processing unit group 402. First, the request processing unit is generated 801. In this embodiment, since the initial value of the number of request processing units generated in advance is four, four are generated.
When the generation is completed, they are made to wait 802, finally registered 803 in the processing unit management table 503, and the initialization is completed. This process is performed once when the machine starts up.

Next, the overall flow will be described with reference to FIGS. FIG. 7 is a diagram showing the overall flow of the request control device 402. First, the processing of the request receiving unit 501 is performed 701. Next, the processing of the request control unit 502 is performed 702. Finally, the processing of the request processing unit is performed 703,
The process of the request control device 401 ends.

Next, the processing 701 performed by the request receiving section 501 will be described with reference to FIG. FIG. 9 is a diagram showing processing of the request receiving unit 501 provided in the request control device 401 of FIG. The request receiving unit 501 first receives 901 a request. Then, the request is passed to the request control unit, the request control unit 502 is called 903,
The process 702 of the request receiving unit 501 ends. Next, the process 702 of the request control unit 502 will be described with reference to FIGS. 5 and 10. 10 is provided in the request control device 401 of FIG. 4,
FIG. 6 is a diagram showing a process of a request control unit 502. First, the processing unit management table 503 is used to search 1001 for a free request processing unit. If there is F in the status area of the processing unit management table 503, there is still a free request processing unit, so the process proceeds to the next process. If not (only R), the request processing unit generation unit 505 generates a new request processing unit 506 and puts it on standby 1002. When generation and waiting are completed,
The new request processing unit 506 is added to the processing unit management table 503 1003. When there is a free request processing unit or when new generation and addition are completed, the request processing unit whose state area 602 of the processing unit management table 503 is F is searched,
By changing the status area 602 from F to R, the processing unit management table 503 is updated 1005. By updating the processing unit management table 503, it can be seen that the request processing unit is currently processing and cannot be activated at that time. Then, the request processing unit whose status area 602 is changed from F to R is activated, and the request is passed to the activated request processing unit 1005, and the process 702 of the request control unit 502 ends.

Here, the addition processing 1003 to the processing unit management table 503 performed by the request processing unit generation unit 505 will be described with reference to FIG. FIG. 11 is a diagram showing the addition of the newly generated request processing unit 5 to the processing unit management table 503 in which four request processing units are registered. First, a new area is newly provided at the very end of the processing unit management table 503, and the request processing unit 5, which is the name of the request processing unit to be added to the processing unit name storage area 1101, and the status area 11
F indicating the free request processing unit is registered in 02, and the process ends.

Next, the processing 703 of the request processing unit will be described with reference to FIG. First, the started request processing unit 1201 processes the request passed from the request control unit 502. When the processing is completed, the processing unit management table 503 in the request control unit 502 is updated 1202. The processing unit management table 503 is updated by searching the processing unit name storage area 601 of the processing unit management table 503 for the own request processing unit name and changing the status area 602 there from R to F. By this processing, the request processing unit enters the standby state, and the request control unit 502 can be activated again. When the updating of the processing unit management table is completed, the processing of the request processing unit is put in a standby state, and the processing of the request processing unit is completed.

As described above, the request control device 40
Since 1 manages the request processing unit group 402, there is no upper limit on the number of requests that can be received, and unnecessary request processing units are not activated.

In this embodiment, the request acceptance, control, and processing have been described on the assumption that the system is composed of a single CPU. In the case of a system consisting of multiple CPUs, the request control unit initializes the request processing unit by allocating it to each CPU,
By causing each CPU to process the request, it is possible to perform parallel processing by a plurality of CPUs.

[0024]

When the system for processing a plurality of requests is constructed by the request control device, the following two effects are obtained.

(1) Managing the status of the request processing unit,
Since the request processing unit is newly generated due to the shortage of request processing units, there is no upper limit to the number of received requests.

(2) Since a plurality of request processing units are generated and made to stand by in advance and the same number of request processing units as the number of requests are activated, the generation overhead of the request processing units and unnecessary activation overhead are generated. It does not have to occur.

[Brief description of drawings]

FIG. 1 is a diagram showing a model of a client-server system in which a plurality of clients and a server are connected by a network.

FIG. 2 is a diagram showing a conventional one method of generating a request processing unit when a request is received.

FIG. 3 is a diagram showing one conventional method in which a request processing unit is generated and made to stand by in advance, and request processing in standby is activated when a request is received.

FIG. 4 is a diagram in which a request control device according to the present invention is installed in a client-server system in which a plurality of clients and a server are connected by a network.

FIG. 5 is an overall configuration diagram of a request control device.

FIG. 6 is a diagram showing a processing unit management table which is provided in the request control unit and manages the state of the request processing unit.

FIG. 7 is an overall flow diagram of a request control device.

FIG. 8 is a diagram showing initialization of a request processing unit group performed by a request control unit.

FIG. 9 is a processing flow diagram of a request receiving unit.

FIG. 10 is a diagram showing processing of a request control unit.

FIG. 11 is a diagram showing an addition process to the processing unit management table.

FIG. 12 is a diagram showing processing of a request processing unit.

[Explanation of symbols]

 101 ... Server, 102 ... Disk, 103 ... Client, 104 ... Client, 105 ... Client, 106 ... Network, 107 ... File, 108 ... File, 109 ... File, 401 ... Request control device, 402 ... Request processing unit group, 403 Request processing unit, 404 Request processing unit, 405 Request processing unit, 406 Request processing unit

Front Page Continuation (72) Inventor Norihiro Goto 5030 Totsuka-cho, Totsuka-ku, Yokohama-shi, Kanagawa Ltd. Software Development Division, Hitachi, Ltd.

Claims (4)

[Claims] 1. In a system in which a server and a plurality of clients are connected via a network, and the server processes a request from the client, 1 to n units that process the request in the server. Request processing units are previously generated and made to wait, and when a request more than the number of the request processing units is received, a request control unit that newly generates the request processing units and causes the request processing units to process is provided. According to the request control device, the number of requests does not have an upper limit. 2. The processing unit management table according to claim 1, wherein a plurality of the request processing units that have been generated and made to stand by in advance are registered in the request control unit, and the state management of the request processing unit is performed, It is checked from the processing unit management table whether there is the request processing unit (hereinafter referred to as a free request processing unit) that has not processed the request, and if there is no free request processing unit, a new request processing unit is newly generated. However, the request control device is characterized in that an upper limit is set on the number of received requests by providing a request processing unit generation unit to be registered in the processing unit management table. 3. The request receiving unit for receiving a request is provided in the server, and the request control unit activates a request processing unit registered in the processing unit management table. The request control device is characterized in that, by providing the request processing unit activation unit, the request processing unit is activated for the number of received requests among the request processing units that have been put on standby. 4. In a system in which a server and a plurality of clients are connected via a network, and the server processes a request from the client, the number of request processing units designated by the user is provided in the server. Pre-generated,
When the number of requests that are in standby is received and more than the number of request processing units is received, a new request processing unit is generated and a request control unit that causes the request processing unit to process is provided so that the number of requests has an upper limit. A request control device characterized by the absence thereof.