JP5381242B2 - Multiprocessor system and control program - Google Patents

Description

The present invention relates to a multiprocessor system and a control program that enable interprocessor communication for the purpose of load distribution of processing by one processor in a network (Network: hereinafter referred to as NW) device having a multiprocessor environment.

In recent years, with increasing complexity of relay processing, security processing, and authentication processing in NW devices such as servers, the load on the processor mounted on the NW device has increased, and a load distribution technique using multiprocessors has been demanded. .
As a mechanism for performing load distribution in a multiprocessor environment, for example, three mechanisms as shown in FIGS. 8 and 9 are common.

  First, as shown in FIG. 8 (a), a plurality of NW devices (server A, server B) mounted with a general-purpose protocol are connected via a network, and a processor (processor A) mounted on each NW device is connected. , Processor B). In this case, using a general-purpose protocol such as TCP / IP (Transmission Control Protocol / Internet Protocol), a plurality of network devices are connected to each other through a network, and processing is shared by a plurality of processors. Load distribution is performed.

  Second, as shown in FIG. 8 (b), a plurality of NW devices (server A, server B) mounted with a unique protocol are connected via a network, and a processor (processor A) mounted on each NW device is connected. , Processor B). In this case, using a unique protocol, a plurality of NW devices are connected to each other via a network, and processing is shared by a plurality of processors, thereby speeding up and distributing the load.

  Third, as shown in FIG. 8C, in one NW device (server A), another processor is connected to one processor (processor A) via a PCI (Peripheral Component Interconnect) bus or the like. Insert an accelerator card or the like equipped with (Processor B). In this case, a unique driver and protocol are installed in each processor, and processing is shared by a plurality of processors, thereby speeding up and distributing the load.

However, with the mechanism described above, there is a problem that processing time is delayed due to being via a network or using a general protocol, and development by development of an original protocol or redevelopment of an application corresponding to the original protocol. There is a problem that the cost increases.
On the other hand, as shown in FIG. 9A, there is considered a mechanism that uses socket communication that is a general-purpose interface for interprocessor communication without going through a network.

  Note that socket communication between a server-side application and a client-side application operating on one processor (processor A) is generally used for communication as shown in FIG. 9B. That is, the socket communication is performed on the same server or host between the client application C and the server application D, or between the server application A and the client application B via another server or host via the network. Used for communication in

  In addition, an inter-processor communication system in a conventional parallel processing system using a single-processor OS operates a single-processor OS and existing applications on a multiprocessor. Then, on a parallel processing system using a single processor OS that realizes parallel processing by a multiprocessor for an application, each processor is provided with a communication proxy means that performs data transfer between tasks between the processors as a proxy (for example, Patent Document 1). This conventional parallel processing system mainly describes a UNIX (R) domain socket as an inter-process communication method capable of communicating only within its own processor. Regarding the TCP / IP INET domain, It is only partly described and not disclosed in detail.

Japanese Patent Laying-Open No. 2005-267118

  Here, socket communication is based on the premise that a system call related to a socket issued from an application running on a processor is processed by the kernel of the processor, and cannot be processed by a kernel of another processor. . Therefore, for example, as shown in FIG. 9B, a client application E that operates on one processor A and a server application G that operates on another processor B outside the NW device in which the processor A is installed. There is a problem that socket communication cannot be performed. Similarly, there is a problem that socket communication cannot be performed between the server application F that operates on one processor A and the server application H that operates on another processor B outside the NW device in which the processor A is mounted. .

Multiprocessor system, one processor on the basis of the port number and IP address, comprising in one processor or other processor, the determination condition storing unit for storing a condition to determine the kernel as a destination of the system call. Further, the one processor includes a system call holding unit that holds a socket system call from the application. Also, in response to a socket system call from an application, one processor generates a temporary descriptor number corresponding to a descriptor number that is a socket identifier, and a temporary descriptor number issuing unit that returns the temporary descriptor number to the application. I have. In addition, the one processor identifies the kernel that is the destination of the system call based on the IP address and port number specified in the system call from the application and the determination condition stored in the determination condition storage unit, and the system call A system call reissuing unit for transmitting the system call held in the holding unit to the kernel is provided. In addition, the one processor stores a descriptor number returned from the kernel that received the socket system call, a temporary descriptor number, and a destination flag that identifies the kernel specified as the destination of the socket system call in association with each other. A storage unit is provided. Further, the one processor extracts a destination flag corresponding to the temporary descriptor number specified in the system call from the application from the management table storage unit, and based on the extracted destination flag, the kernel serving as the destination of the system call Is provided with a descriptor number conversion unit for transmitting the system call.

The disclosed multiprocessor system allows system calls to be transferred between applications of a plurality of processors connected via an expansion bus, and has the effect of distributing the load on one processor to other processors.

It is a block diagram which shows an example of NW apparatus carrying the multiprocessor system which concerns on this embodiment. FIG. 2 is a functional block diagram showing a schematic configuration of a unique driver in the kernel of the processor shown in FIG. 1, (a) is a functional block diagram showing a data flow for a system call issued from a server application, and (b) is a client. It is a functional block diagram which shows the flow of the data with respect to the system call issued from an application. It is a sequence diagram for demonstrating the processing operation of the original driver with respect to the system call issued from a server application. It is a sequence diagram for demonstrating the processing operation of the original driver with respect to the system call issued from a client application. FIG. 5 is an explanatory diagram showing an example of a data update flow corresponding to FIGS. 3 and 4 in the management table storage unit shown in FIG. 2. It is explanatory drawing which shows an example of the flow of the data update in the management table storage part shown in FIG. It is explanatory drawing for demonstrating the effect by the multiprocessor system which concerns on this embodiment, (a) is a block diagram which shows an example of NW apparatus before mounting the client application of a 1st processor in a 3rd processor (A) is a block diagram showing an example of an NW device after the client application of the first processor is mounted on the third processor. (A) is explanatory drawing for demonstrating the mechanism of load distribution of the conventional processor, (b) is explanatory drawing for demonstrating the other mechanism of load distribution of the conventional processor, (c) is the explanatory drawing of the conventional processor. It is explanatory drawing for demonstrating the further another mechanism of load distribution. (A) is explanatory drawing for demonstrating the mechanism using socket communication, (b) is explanatory drawing for demonstrating the subject of the communication between the conventional processors.

  Here, the present invention can be implemented in many different forms. Therefore, it should not be interpreted only by the description of the following embodiment. Also, the same reference numerals are given to the same elements throughout the embodiment.

  In the embodiment, the system will be mainly described. However, as will be apparent to those skilled in the art, the present invention can also be implemented as a program and method usable on a computer. In addition, the present invention can be implemented in hardware, software, or software and hardware embodiments. The program can be recorded on any computer-readable medium such as a hard disk, CD-ROM, DVD-ROM, optical storage device, or magnetic storage device. Furthermore, the program can be recorded on another computer via a network.

(First embodiment of the present invention)
The multiprocessor system according to this embodiment includes one processor that operates a server-type application or a client-type application, and another processor that operates a client-type application or a server-type application that performs socket communication with the application. And.

  Here, the server-type application is an application that issues socket, bind, listen, and accept system calls to connect sockets to establish a communication path, and is hereinafter referred to as a server application. A client-type application is an application that issues a socket and connect system call in order to connect sockets and establish a communication path, and is hereinafter referred to as a client application.

  The other processors described above are one or a plurality of processors, and in the following description, as shown in FIG. 1, as an example, the first processor 110 is mounted on the NW device 100 as one processor. Will be described. In the following description, as the other processor, the second processor 210 is mounted on another NW device such as a server or a host (hereinafter referred to as another NW device 200), and the third processor 310 is a processor card. A case where it is mounted on the expansion card 300 will be described as an example. The NW device 100 and the other NW device 200 are connected via the network 400, and the NW device 100 and the expansion card 300 are connected via the expansion bus 500 such as a PCI bus.

  The one processor and the other processors described above each include a kernel 10 which will be described later and a user 20 that implements the server application 21 and / or the client application 22.

  In the following description, for an application, the kernel 10 inside the processor including the user 20 in which the application is installed is referred to as a self-kernel. Further, for the application, the kernel 10 inside another processor which is a socket communication partner outside the processor including the user 20 in which the application is mounted will be referred to as a partner kernel.

  Here, the kernel 10 is software that implements the basic functions of an OS (Operating System), such as monitoring of application software and peripheral devices, management of resources such as disks and memories, interrupt processing or inter-process communication, etc. As a basic function. In particular, the kernel 10 can modularize additional functions and control software (drivers) for peripheral devices and add them later.

  The kernel 10 is mounted with a unique driver 11 and a socket interface (hereinafter referred to as I / F) 12 described later, and an I / F driver 13 and / or a network card (NIC) as required. The network I / F 14 is installed.

  2, the unique driver 11 includes a server application side transmission / reception unit 1, a client application side transmission / reception unit 2, a determination condition storage unit 3, a system call holding unit 4, a temporary descriptor number issuing unit 5, and a system call reissuing unit 6. A management table storage unit 7 and a descriptor number conversion unit 8.

  In FIG. 2A, the server application side transmitting / receiving unit 1 receives a system call transmitted from the server application 21, and depending on the type of the system call, the temporary descriptor number issuing unit 5, the system call reissuing unit 6 or A system call is output to the descriptor number conversion unit 8. That is, the server application side transmitting / receiving unit 1 outputs a socket system call to the temporary descriptor number issuing unit 5, outputs a bind system call to the system call reissuing unit 6, and listen, accept, send, recv, shutdown, and close systems. The call is output to the descriptor number conversion unit 8.

  Further, the server application-side transmitting / receiving unit 1 transmits a temporary descriptor number corresponding to a descriptor number, which is a socket identifier (ID), input from the temporary descriptor number issuing unit 5 to the server application 21.

  Here, the descriptor number corresponds to the ID of the socket assigned by the kernel 10 when the socket is generated, and the application designates the socket to be accessed by designating the descriptor number notified from the kernel 10. .

Further, in FIG. 2B, the server application side transmitting / receiving unit 1 transmits the socket and connect system call input from the system call reissuing unit 6 to the kernel 10 on the server application 21 side. Further, the server application side transmitting / receiving unit 1 transmits the send, recv, shutdown, and close system calls input from the descriptor number conversion unit 8 to the kernel 10 on the server application 21 side.
Further, the server application side transmitting / receiving unit 1 receives the descriptor number transmitted from the kernel 10 on the server application 21 side and outputs the descriptor number to the descriptor number converting unit 8.

In FIG. 2B, the client application side transmitting / receiving unit 2 receives the system call transmitted from the client application 22, and depending on the type of the system call, the temporary descriptor number issuing unit 5, the system call reissuing unit 6 or A system call is output to the descriptor number conversion unit 8. In other words, the client application side transmitting / receiving unit 2 outputs a socket system call to the temporary descriptor number issuing unit 5, outputs a connect system call to the system call reissuing unit 6, and sends send, recv, shutdown, and close system calls to the descriptor number. Output to the converter 8.
Further, the client application side transmitting / receiving unit 2 transmits the temporary descriptor number input from the temporary descriptor number issuing unit 5 to the client application 22.

Further, in FIG. 2A, the client application side transmitting / receiving unit 2 transmits the socket and bind system call input from the system call reissuing unit 6 to the kernel 10 on the client application 22 side. In addition, the client application side transmission / reception unit 2 transmits the listen, accept, send, recv, shutdown, and close system calls input from the descriptor number conversion unit 8 to the kernel 10 on the client application 22 side.
Further, the client application side transmitting / receiving unit 2 receives the descriptor number transmitted from the kernel 10 on the client application 22 side and outputs the descriptor number to the descriptor number converting unit 8.

  The determination condition storage unit 3 stores conditions for determining the kernel 10 that is the destination of the system call based on the port number in the server application 21 that is the transmission source of the bind system call and the IP address in the processor that operates the application. To do. Further, the determination condition storage unit 3 determines the kernel 10 that is the destination of the system call based on the port number in the client application 22 that is the transmission source of the connect system call and the IP address in the processor that operates the application. Is stored.

  The system call holding unit 4 holds a socket system call from the server application 21 or the client application 22. The system call holding unit 4 holds a bind system call from the server application 21 or a connect system call from the client application 22, and a system call issued before the bind or connect system call.

  The temporary descriptor number issuing unit 5 generates a temporary descriptor number corresponding to the descriptor number in response to a socket system call from the server application 21 or the client application 22. Further, the temporary descriptor number issuing unit 5 returns the generated temporary descriptor number to the server application 21 or the client application 22 that has transmitted the socket system call. The temporary descriptor number issuing unit 5 stores the generated temporary descriptor number in the management table storage unit 7.

  The temporary descriptor number issuing unit 5 assigns temporary descriptor numbers so that the temporary descriptor numbers stored in the management table storage unit 7 do not overlap. As a result, even if the same descriptor number is assigned by the own kernel 10 and the partner kernel 10 and stored in the management table storage unit 7, the system call reissue unit 6 uses the different temporary descriptor numbers to Can be uniquely identified.

  Based on the IP address and port number specified in the bind system call from the server application 21 and the discrimination condition stored in the discrimination condition storage unit 3, the system call reissue unit 6 is the kernel 10 that is the destination of the system call. Is identified. Further, the system call reissue unit 6 becomes a destination of the system call based on the IP address and port number specified in the connect system call from the client application 22 and the determination condition stored in the determination condition storage unit 3. The kernel 10 is specified. Further, the system call reissue unit 6 transmits the system call held in the system call holding unit 4 to the identified kernel 10. Further, the system call reissue unit 6 transmits a system call other than the socket system call held in the system call holding unit 4 to the specified kernel 10 by specifying a descriptor number.

  The management table storage unit 7 uses the descriptor number returned from the kernel 10 that received the socket system call, the temporary descriptor number generated for the socket system call, and the kernel 10 specified as the destination of the socket system call. A destination flag to be identified is stored in association with each other. As the destination flag, for example, the own kernel 10 may be set to “0” and the counterpart kernel 10 may be set to “1”.

  The descriptor number conversion unit 8 extracts a destination flag corresponding to the temporary descriptor number specified in the listen, accept, send, recv, shutdown, or close system call from the server application 21 from the management table storage unit 7. Further, the descriptor number conversion unit 8 extracts a destination flag corresponding to the temporary descriptor number designated by the send, recv, shutdown, or close system call from the client application 22 from the management table storage unit 7. Further, the descriptor number conversion unit 8 transmits the system call to the kernel 10 that is the destination of the system call based on the extracted destination flag.

Next, processing operations in the multiprocessor system according to the present embodiment will be described.
First, the processing operation of the unique driver 11 for the system call issued by the server application 21 will be described with reference to FIGS. 2A, 3 and 5A to 5C.

  The server application 21 issues a socket system call for requesting generation of a socket for accepting connection of the client application 22 to the own kernel 10 (step S1).

  When the server application side transmitting / receiving unit 1 of the unique driver 11 in the own kernel 10 receives the socket system call, it outputs the socket system call to the temporary descriptor number issuing unit 5.

  When the socket system call is input, the temporary descriptor number issuing unit 5 generates a temporary descriptor number corresponding to the descriptor number that is the identifier of the socket (step S2).

  Then, the temporary descriptor number issuing unit 5 newly registers the generated temporary descriptor number in the management table storage unit 7 (step S3, FIG. 5A). In FIG. 5A, the case where “10” is registered as the temporary descriptor number is shown as an example.

  The temporary descriptor number issuing unit 5 outputs the generated temporary descriptor number to the server application side transmission / reception unit 1, and the server application side transmission / reception unit 1 returns the temporary descriptor number to the server application 21 that transmitted the socket system call. (Step S4). The temporary descriptor number issuing unit 5 outputs the socket system call to the system call holding unit 4, and the system call holding unit 4 temporarily holds the socket system call.

  The server application 21 issues a bind system call for setting the socket communication port number set for itself and the IP address of the processor that operates the server application 21 to the socket. At this time, the server application 21 designates a temporary descriptor number for designating a socket and issues a bind system call (step S5).

  In general, after receiving the descriptor number (temporary descriptor number) for the socket system call, the server application 21 issues a bind system call without issuing another system call. However, depending on the option setting of the application, another system call may be issued between the socket system call and the bind system call (step S4a). In this case, when the server application side transmitting / receiving unit 1 receives another system call, the server application side transmitting / receiving unit 1 outputs the other system call to the system call holding unit 4 via the system call reissuing unit 6. The system call holding unit 4 temporarily holds other system calls (step S4b), and returns an appropriate return value to the server application 21 (step S4c).

When receiving the bind system call, the server application side transmitting / receiving unit 1 outputs the bind system call to the system call reissuing unit 6.
When a bind system call is input, the system call reissue unit 6 refers to the determination condition storage unit 3 based on the IP address and port number specified in the bind system call, and the kernel 10 serving as the destination of the system call. Is specified (step S6).

  Then, the system call reissue unit 6 registers the identified kernel 10 in the management table storage unit 7 in association with the temporary descriptor number registered in step S3 described above (step S7, FIG. 5B). In FIG. 5B, the case where “1” (partner kernel 10) is registered as the destination flag is shown as an example.

  Further, the system call reissuing unit 6 extracts the socket system call held in the system call holding unit 4 and outputs it to the client application side transmitting / receiving unit 2 together with the specified information of the kernel 10. Then, the client application side transmitting / receiving unit 2 transmits a socket system call to the identified kernel 10 (step S8). The system call reissue unit 6 outputs a bind system call to the system call holding unit 4, and the system call holding unit 4 temporarily holds the bind system call.

  In response to the socket system call, the client application side transmitting / receiving unit 2 receives the descriptor number transmitted from the kernel 10 on the client application 22 side, and outputs the descriptor number to the descriptor number conversion unit 8 (step S9).

  When the descriptor number from the client application 22 is input, the descriptor number conversion unit 8 registers the descriptor number in the management table storage unit 7 in association with the temporary descriptor number registered in step S3 described above (step S10, FIG. 5 (c)). In FIG. 5C, the case where “50” is registered as the descriptor number is shown as an example.

  Then, the system call reissuing unit 6 extracts the bind system call held in the system call holding unit 4, and together with the information of the kernel 10 corresponding to the descriptor number registered in step S10, the client application side transmitting / receiving unit 2 Output to. Then, the client application side transmitting / receiving unit 2 specifies a descriptor number and transmits a bind system call to the corresponding kernel 10 (step S11).

  In step S4b described above, if the system call holding unit 4 holds another system call, the other system call held in the system call holding unit 4 can be handled by specifying the descriptor number. Is transmitted to the kernel 10 (step S10a).

Then, the server application 21 issues a listen system call for creating a socket queue that is a queue for receiving connections of a plurality of client applications 22 to the own kernel 10. At this time, the server application 21 issues a listen system call by designating a temporary descriptor number for designating a socket (step S12).
When receiving the listen system call, the server application side transmitting / receiving unit 1 outputs the listen system call to the descriptor number conversion unit 8.

  When a listen system call is input, the descriptor number conversion unit 8 refers to the management table storage unit 7 based on the temporary descriptor number specified in the listen system call, and information on the kernel 10 serving as the destination of the system call. , The corresponding descriptor number is extracted.

  Further, the descriptor number conversion unit 8 outputs a listen system call to the client application side transmission / reception unit 2 together with the extracted information of the kernel 10 and the descriptor number. Then, the client application side transmitting / receiving unit 2 specifies a descriptor number and transmits a listen system call to the corresponding kernel 10 (step S13).

Then, the server application 21 issues an accept system call for waiting for the client application 22 to connect to the socket with respect to the own kernel 10. At this time, the server application 21 designates a temporary descriptor number for designating a socket and issues an accept system call (step S14).
When receiving the accept system call, the server application side transmitting / receiving unit 1 outputs the accept system call to the descriptor number converting unit 8.

  When an accept system call is input, the descriptor number conversion unit 8 refers to the management table storage unit 7 based on the temporary descriptor number specified in the accept system call, and information on the kernel 10 that is the destination of the system call. , The corresponding descriptor number is extracted.

  Further, the descriptor number conversion unit 8 outputs an accept system call to the client application side transmission / reception unit 2 together with the extracted information of the kernel 10 and the descriptor number. Then, the client application transmitting / receiving unit 2 designates a descriptor number and transmits an accept system call to the corresponding kernel 10 (step S15).

  When a connect system call, which will be described later, is issued from the client application 22, a communication path through the sockets of the server application 21 and the client application 22 is established, and data can be transmitted / received (step S16). In the data transmission / reception, a send system call and a recv system call are issued from the server application 21. The same processing as the listen and accept system calls is performed in the original driver 11 for the send and recv system calls. Will be done.

Then, when the data transmission / reception is completed and the socket communication is terminated, the server application 21 issues a close system call for opening the socket to the own kernel 10. At this time, the server application 21 designates a temporary descriptor number for designating a socket and issues a close system call (step S17).
When receiving the close system call, the server application side transmitting / receiving unit 1 outputs the close system call to the descriptor number conversion unit 8.

  When the close system call is input, the descriptor number conversion unit 8 refers to the management table storage unit 7 based on the temporary descriptor number specified in the close system call, and information on the kernel 10 that is the destination of the system call. , The corresponding descriptor number is extracted.

  Further, the descriptor number conversion unit 8 outputs a close system call to the client application side transmission / reception unit 2 together with the extracted information of the kernel 10 and the descriptor number. Then, the client application side transceiver unit 2 designates the descriptor number and transmits a close system call to the corresponding kernel 10 (step S18).

  To terminate socket communication, the shutdown system call can be used to explicitly disconnect the connection. However, if the socket is released, the connection disconnection process is also performed. Issuance may be omitted.

Next, the processing operation of the unique driver 11 for the system call issued by the client application 22 will be described with reference to FIGS. 2B, 4 and 5D to 5F.
The client application 22 issues a socket system call for requesting generation of a socket for accepting connection of the server application 21 to the own kernel 10 (step S101).

  When the client application side transmitting / receiving unit 2 of the unique driver 11 in the own kernel 10 receives the socket system call, it outputs the socket system call to the temporary descriptor number issuing unit 5.

  When the socket system call is input, the temporary descriptor number issuing unit 5 generates a temporary descriptor number corresponding to the descriptor number that is the identifier of the socket (step S102).

  Then, the temporary descriptor number issuing unit 5 newly registers the generated temporary descriptor number in the management table storage unit 7 (step S103, FIG. 5 (d)). FIG. 5D shows an example in which “11” is registered as the temporary descriptor number.

  Further, the temporary descriptor number issuing unit 5 outputs the generated temporary descriptor number to the client application side transmission / reception unit 2, and the client application side transmission / reception unit 2 returns the temporary descriptor number to the client application 22 that transmitted the socket system call. (Step S104). The temporary descriptor number issuing unit 5 outputs the socket system call to the system call holding unit 4, and the system call holding unit 4 temporarily holds the socket system call.

  The client application 22 issues a connect system call for setting the socket communication port number set for itself and the IP address of the processor that operates the client application 22 to the socket. At this time, the client application 22 issues a connect system call by specifying a temporary descriptor number for specifying a socket (step S105).

  In general, the client application 22 issues a connect system call without issuing another system call after receiving a descriptor number (temporary descriptor number) for the socket system call. However, depending on the option setting of the application, another system call may be issued between the socket system call and the connect system call (step S104a). In this case, when the client application side transmitting / receiving unit 2 receives another system call, the client application side transmitting / receiving unit 2 outputs the other system call to the system call holding unit 4 via the system call reissuing unit 6. The system call holding unit 4 temporarily holds other system calls (step S104b), and returns an appropriate return value to the client application 22 (step S104c).

  Upon receiving the connect system call, the client application side transmitting / receiving unit 2 outputs the connect system call to the system call reissue unit 6.

  When the connect system call is input, the system call reissue unit 6 refers to the determination condition storage unit 3 based on the IP address and port number specified in the connect system call, and the kernel 10 serving as the destination of the system call. Is specified (step S106).

  Then, the system call reissue unit 6 registers the specified kernel 10 in the management table storage unit 7 in correspondence with the temporary descriptor number registered in step S103 described above (step S107, FIG. 5E). FIG. 5E shows an example in which “1” (the partner kernel 10) is registered as the destination flag.

  Further, the system call reissue unit 6 extracts the socket system call held in the system call holding unit 4 and outputs it to the server application side transmitting / receiving unit 1 together with the specified information of the kernel 10. Then, the server application side transmitting / receiving unit 1 transmits a socket system call to the identified kernel 10 (step S108). The system call reissue unit 6 outputs a connect system call to the system call holding unit 4, and the system call holding unit 4 temporarily holds the connect system call.

  In response to the socket system call, the server application side transmitting / receiving unit 1 receives the descriptor number transmitted from the kernel 10 on the server application 21 side and outputs the descriptor number to the descriptor number converting unit 8 (step S109).

  When the descriptor number from the client application 22 is input, the descriptor number conversion unit 8 registers the descriptor number in the management table storage unit 7 in association with the temporary descriptor number registered in step S103 described above (step S110, FIG. 5 (f)). In FIG. 5F, the case where “51” is registered as the descriptor number is shown as an example.

  Then, the system call reissuing unit 6 extracts the connect system call held in the system call holding unit 4, and together with the information of the kernel 10 corresponding to the descriptor number registered in step S110, the server application side transmitting / receiving unit 1 Output to. Then, the server application-side transmitting / receiving unit 1 specifies a descriptor number and transmits a connect system call to the corresponding kernel 10 (step S111).

  In step S104b described above, if the system call holding unit 4 holds another system call, the other system call held in the system call holding unit 4 is specified by specifying a descriptor number. To the kernel 10 to be executed (step S110a).

  When the communication path via the sockets of the server application 21 and the client application 22 is established, data can be transmitted / received (step S112). In the data transmission / reception, a send system call and a recv system call are issued from the client application 22, and this send and recv system call is the same as the listen and accept system calls described above in the original driver 11. Processing will be performed.

The client application 22 issues a close system call for opening the socket to the own kernel 10 in order to end the socket communication by completing the data transmission / reception. At this time, the client application 22 issues a close system call by designating a temporary descriptor number for designating a socket (step S113).
Upon receiving the close system call, the client application side transmitting / receiving unit 2 outputs the close system call to the descriptor number conversion unit 8.

  When the close system call is input, the descriptor number conversion unit 8 refers to the management table storage unit 7 based on the temporary descriptor number specified in the close system call, and information on the kernel 10 that is the destination of the system call. , The corresponding descriptor number is extracted.

  Further, the descriptor number conversion unit 8 outputs a close system call to the server application side transmitting / receiving unit 1 together with the extracted information of the kernel 10 and the descriptor number. Then, the server application side transmitting / receiving unit 1 designates the descriptor number and transmits a close system call to the corresponding kernel 10 (step S114).

  To terminate socket communication, the shutdown system call can be used to explicitly disconnect the connection. However, if the socket is released, the connection disconnection process is also performed. Issuance may be omitted.

  Next, as a specific example, a processing operation of the unique driver 11 for a system call issued by each application installed in the user 20 in the first processor 110 of the NW device 100 illustrated in FIG. 1 will be described.

  In the following description, as shown in FIG. 1, a case where the server application 21a, the client application 22c, the server application 21d, and the server application 21f are installed in the user 20 of the first processor 110 is described as an example. To do. Further, as illustrated in FIG. 1, the case where the client application 22b is mounted on the user 20 of the second processor 210 and the client application 22e is mounted on the user 20 of the third processor 310 will be described as an example.

  Further, in FIG. 1, a client application 22c and a server application 21d perform socket communication by using the kernel 10 of the first processor 110 with each other. The server application 21a performs socket communication with the client application 22b that operates on the second processor 210, and the server application 21f performs socket communication with the client application 22e that operates on the third processor 310. It is.

  Here, it is assumed that the network device 100 has “Ay” set as the IP address of the network I / F 14 and “Af” set as the IP address used for communication in the server application F. Further, it is assumed that “Ax” is set as the IP address of the network I / F 14 in the other NW device 200.

  The NW device 100 also uses an internal loop address “Al” that is a loop address in the kernel 10 as an IP address used for communication between the client application 22c and the server application 21d installed in the kernel 10 of the first processor 110. Is set.

  Each application is set with a port number for socket communication. That is, the port number “Pa” is set for the server application 21a, the port number “Pc” is set for the client application 22c, the port number “Pd” is set for the server application 21d, and the port number is set for the server application 21f. It is assumed that the number “Pf” is set. Further, it is assumed that the port number “Pb” is set in the client application 22b and the port number “Pe” is set in the client application 22e.

  Further, it is assumed that the unique driver 11 in the kernel 10 of the first processor 110 is set with the conditions shown in Table 1 below as the determination conditions stored in the determination condition storage unit 3, for example. The conditions shown in Table 1 below are appropriately set by the system designer of the processor, and it is preferable that the set values can be reconfigured by a programmable logic device or the like.

  Hereinafter, the processing operation of the unique driver 11 when each application issues a socket-related system call in the order of the server application 21a, the client application 22c, the server application 21d, and the server application 21f in the above-described environment will be described.

  Note that the operation of the unique driver 11 in response to a system call issued from the server application 21a, the server application 21d, and the server application 21f follows steps S1 to S18 shown in FIG. Further, the operation of the unique driver 11 for the system call issued from the client application 22c follows the above-described steps S101 to S114 shown in FIG.

Therefore, in the following description, the flow of registration of the temporary descriptor number, the descriptor number, and the destination flag for the management table storage unit 7 will be mainly described with reference to FIG.
First, the operation of the unique driver 11 in response to a system call issued from the server application 21a will be described.

  When the unique driver 11 receives the socket system call issued from the server application 21a (step S1), the unique driver 11 newly registers the temporary descriptor number “10” in the management table storage unit (step S2, step S3, FIG. 6A). )). The unique driver 11 returns the temporary descriptor number “10” to the server application 21a (step S4).

  Then, the unique driver 11 receives the bind system call issued from the server application 21a (step S5). At this time, in the bind system call, the IP address “Ay” is designated, and the port number “Pa” is designated.

  The unique driver 11 determines that it is addressed to its own kernel based on the determination condition (condition 2 in Table 1) stored in the determination condition storage unit 3 (step S6), and sends a destination flag “0” to the management table storage unit 7. Is set (step S7, FIG. 6B), and a socket system call is issued to the own kernel 10 (step S8).

  When the unique driver 11 returns the decryptor number “50” from its own kernel 10 (step S9), it sets the decryptor number “50” in the management table storage unit 7 (step S10, FIG. 6C). Then, a bind system call is issued to the own kernel 10 (step S11).

  Thereafter, when the server application 21a designates the temporary descriptor number “10” and issues a system call, the unique driver 11 searches the management table storage unit 7 based on the temporary descriptor number “10”, and It is determined that the call is addressed to its own kernel. Then, the unique driver 11 designates the descriptor number “50” obtained from the management table storage unit 7 based on the temporary descriptor number “10”, and issues the received system call to the own kernel 10.

Next, the operation of the unique driver 11 in response to a system call issued from the client application 22c will be described.
When the unique driver 11 receives the socket system call issued from the client application 22c (step S101), the unique driver 11 newly registers the temporary descriptor number “11” in the management table storage unit (step S102, step S103, FIG. 6D). )). The unique driver 11 returns the temporary descriptor number “11” to the client application 22c (step S104).

  Then, the unique driver 11 receives a connect system call issued from the client application 22c (step S105). At this time, the IP address “Al” is specified for the connect system call, and the port number “Pc” is specified.

  The unique driver 11 determines that it is addressed to its own kernel based on the determination condition (condition 3 in Table 1) stored in the determination condition storage unit 3 (step S106). The unique driver 11 sets the destination flag “0” in the management table storage unit 7 (step S107, FIG. 6E), and issues a socket system call to the own kernel 10 (step S108).

  When the unique driver 11 returns the decryptor number “51” from the own kernel 10 (step S109), the unique driver 11 sets the decryptor number “51” in the management table storage unit 7 (step S110, FIG. 6 (f)). Then, a connect system call is issued to the own kernel 10 (step S111).

  Thereafter, when the client application 22c issues a system call specifying the temporary descriptor number “11”, the unique driver 11 searches the management table storage unit 7 based on the temporary descriptor number “11”, and It is determined that the call is addressed to its own kernel. Then, the unique driver 11 specifies the descriptor number “51” obtained from the management table storage unit 7 based on the temporary descriptor number “11”, and issues the received system call to the own kernel 10.

Next, the operation of the unique driver 11 in response to a system call issued from the server application 21d will be described.
When the unique driver 11 receives the socket system call issued from the server application 21d (step S1), the unique driver 11 newly registers the temporary descriptor number “12” in the management table storage unit (step S2, step S3, FIG. 6G). )). The unique driver 11 returns the temporary descriptor number “12” to the server application 21d (step S4).

  Then, the unique driver 11 receives the bind system call issued from the server application 21d (step S5). At this time, in the bind system call, the IP address “Al” is designated and the port number “Pd” is designated.

  The unique driver 11 determines that it is addressed to its own kernel based on the determination condition (condition 4 in Table 1) stored in the determination condition storage unit 3 (step S6), and sends a destination flag “0” to the management table storage unit 7. Is set (step S7, FIG. 6 (h)), and a socket system call is issued to the own kernel 10 (step S8).

  When the unique driver 11 returns the decryptor number “52” from its own kernel 10 (step S9), it sets the decryptor number “52” in the management table storage unit 7 (step S10, FIG. 6 (i)). Then, a bind system call is issued to the own kernel 10 (step S11).

  Thereafter, when the server application 21d designates the temporary descriptor number “12” and issues a system call, the unique driver 11 searches the management table storage unit 7 based on the temporary descriptor number “12”, and It is determined that the call is addressed to its own kernel. Then, the unique driver 11 specifies the descriptor number “52” obtained from the management table storage unit 7 based on the temporary descriptor number “12”, and issues the received system call to the own kernel 10.

Next, the operation of the unique driver 11 in response to a system call issued from the server application 21f will be described.
When the unique driver 11 receives the socket system call issued from the server application 21f (step S1), the unique driver 11 newly registers the temporary descriptor number “13” in the management table storage unit (step S2, step S3, FIG. 6 (j)). )). The unique driver 11 returns the temporary descriptor number “13” to the server application 21f (step S4).

  Then, the unique driver 11 receives the bind system call issued from the server application 21f (step S5). At this time, in the bind system call, the IP address “Af” is designated and the port number “Pf” is designated.

  The unique driver 11 determines that it is addressed to the partner kernel based on the determination condition (condition 5 in Table 1) stored in the determination condition storage unit 3 (step S6), and sends a destination flag “1” to the management table storage unit 7. Is set (step S7, FIG. 6 (k)), and a socket system call is issued to the partner kernel 10 (step S8).

  When the decryptor number “50” is returned from the partner kernel 10 (step S9), the unique driver 11 sets the decryptor number “50” in the management table storage unit 7 (step S10, FIG. 6 (l)). Then, a bind system call is issued to the partner kernel 10 (step S11).

  Thereafter, when the server application 21f designates the temporary descriptor number “13” and issues a system call, the unique driver 11 searches the management table storage unit 7 based on the temporary descriptor number “13”, and Determine that the call is destined for the opposite kernel. Then, the unique driver 11 designates the descriptor number “50” obtained from the management table storage unit 7 based on the temporary descriptor number “13”, and issues the received system call to the partner kernel 10.

As described above, the multiprocessor system according to the present embodiment has a plurality of applications connected not only between applications installed in one processor or between applications of a plurality of processors via a network, but also via an expansion bus. Allows system calls to be passed between applications on the processor. Thereby, the multiprocessor system according to the present embodiment can distribute the load on one processor to other processors, and has the effect of realizing the processing load distribution of the processors.

In particular, in the multiprocessor system according to the present embodiment, for example, as shown in FIG. 7A, the client application 22c processed by the first processor 110 is changed to It is deleted from the first processor 110 and mounted on the third processor 310. Accordingly, the multiprocessor system according to the present embodiment can cause the client application 22c to be processed by the third processor 310, and can reduce the load on the first processor 110. In addition, the multiprocessor system according to the present embodiment reduces the client application 22c without changing the client application 22c by moving the processor that processes the client application 22c from the first processor 110 to the third processor 310. Distribute the processing load of the cost processor.

DESCRIPTION OF SYMBOLS 1 Server application side transmission / reception part 2 Client application side transmission / reception part 3 Discrimination condition storage part 4 System call holding part 5 Temporary descriptor number issue part 6 System call reissue part 7 Management table storage part 8 Descriptor number conversion part 10 Kernel 11 Original driver 12 Socket interface 13 I / F driver 20 User 21, 21a, 21d, 21f Server application 22, 22b, 22c, 22e Client application 100 NW device 110 First processor 200 Other NW device 210 Second processor 300 Expansion card 310 Third Processor 400 network 500 expansion bus

Claims (4)

Comprising: a first processor for operating the server applications or client applications of the other processors to operate the client type of the application or server applications that perform socket communication with the application, and connecting the socket with each other In a multiprocessor system that establishes a communication path
The one processor is
Based on the port number in the application that is the source of the bind or connect system call and the IP address in the one processor or the other processor that operates the application, the system call of the one processor or the other processor A determination condition storage unit for storing a condition for determining a destination kernel;
A system call holding unit for holding a socket system call from the application;
In response to a socket system call from the application, a temporary descriptor number issuing unit that generates a temporary descriptor number corresponding to a descriptor number that is an identifier of the socket, and returns the temporary descriptor number to the application;
Based on the IP address and port number specified in the bind or connect system call from the application, and the determination condition stored in the determination condition storage unit, the kernel serving as the destination of the system call is specified, and the system call holding A system call reissue unit that sends the system call held in the unit to the kernel;
Corresponds the descriptor number returned from the kernel that received the socket system call, the temporary descriptor number generated for the socket system call, and the destination flag that identifies the kernel specified as the destination of the socket system call A management table storage unit for storing
A destination flag corresponding to the temporary descriptor number specified in the listen, accept, send, recv, shutdown or close system call from the application is extracted from the management table storage unit, and based on the extracted destination flag, A descriptor number converter that transmits the system call to the kernel that is the destination of the system call;
A multiprocessor system comprising: The multiprocessor system of claim 1, wherein
The system call holding unit holds a bind or connect system call from the application and a system call issued before the bind or connect system call;
The system call reissue unit sends a system call other than the socket system call held in the system call holding unit to the kernel specified for the system call by specifying the descriptor number. Multiprocessor system . In the multiprocessor system according to claim 1 or 2,
Mounting the one processor to the network device, by mounting the other processor to the expansion card, a multi-processor system via an expansion bus, and wherein the connecting the network device and the expansion card. One processor that operates a server-type application or a client-type application, and another processor that operates a client-type application or a server-type application that performs socket communication with the application, and connects sockets to each other A control program for causing the one processor to function in a multiprocessor system that establishes a communication path by
The one processor or the other processor based on the port number in the application that is the source of the bind or connect system call and the IP address in the one processor or the other processor that operates the application. A determination condition storage means for storing a condition for determining a kernel as a destination of the system call, a system call holding means for holding a socket system call from the application, and a socket system call from the application, A temporary descriptor number issuing means for generating a temporary descriptor number corresponding to a descriptor number that is an identifier of the socket and returning the temporary descriptor number to the application; and a bind from the application Identifies the kernel that is the destination of the system call based on the IP address and port number specified in the connect system call and the discrimination condition stored in the discrimination condition storage means, and is held in the system call holding means A system call reissuing means for transmitting a system call to the kernel; a descriptor number of a socket returned from the kernel that has received the socket system call; the temporary descriptor number generated for the socket system call; and the socket Management table storage means for associating and storing a destination flag for identifying a kernel specified as a system call destination, and the temporary descriptor specified in a listen, accept, send, recv, shutdown, or close system call from the application Destination file corresponding to the number The grayed, the extracts from the management table storage unit, based on the destination flags the extracted control program to function as a descriptor number conversion means for transmitting the system call to the kernel as a destination of the system call.

Images