JP2017151765A - Monitoring device, monitoring method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To monitor a life-and-death state of processing standing by for reception or transmission of a packet by loop processing.SOLUTION: A packet reception driver 111 stands by for reception of a packet by a network interface by loop processing and stores the received packet in a packet storage section 115. A packet reception driver writes information indicating a life-and-death state of at least one of the network interface 105 and the packet reception driver in a life-and-death information storage section 117r in the interim of the loop processing. A monitoring section 114 of a monitoring device refers to the life-and-death information storage section and monitors the life-and-death information of at least one of the network interface and the packet reception driver.SELECTED DRAWING: Figure 4

Description

  The present invention relates to a monitoring device, a monitoring method, and a program.

  In recent years, a library called DPDK (Data Plane Development Kit) shown in Non-Patent Document 1 has been released in order to speed up applications on a computer system.

  Since the DPDK library can directly send processing instructions from an application to a CPU (Central Processing Unit), the processing speed can be increased. Further, DPDK provides a packet reception driver and a packet transmission driver called PDM (Poll Mode Driver). The PMD operates with an algorithm based on the busy wait method as shown in FIGS. 1 and 2 show an algorithm of a spin lock method that is one implementation of the busy wait method.

  As shown in FIG. 1, the packet reception driver confirms whether or not a packet is received with a NIC (Network Interface Card), and if a packet has been received, the packet reception driver is installed as a device in which the packet reception driver is installed. Stored in the packet storage unit. A series of these processes is repeated at high speed. The packet stored in the packet storage unit is read by the application.

  As shown in FIG. 2, the packet transmission driver reads a packet written by an application in a packet storage unit for transmission in the device, and sends the packet to the NIC. A series of these processes is repeated at high speed.

  Alternatively, when a plurality of drivers refer to one packet storage unit, while one driver (hereinafter referred to as “driver A”) is executing processing, the other driver completes processing of driver A. Until then, the packet storage unit is repeatedly referred to. In this manner, an operation of repeating a certain process in a high-speed loop is called busy wait.

  When packet reception processing or packet transmission processing to which the busy wait method is applied is executed, the CPU during that time is not interrupted by other processing. Therefore, driver developers also employ busy waits to reduce processing delays due to interrupt processing to the CPU. On the other hand, the CPU is used up to the performance limit regardless of the presence or absence of a packet.

  In the first half of the 2000s, busy waits were generally used for processes and threads that were very short in processing time and started and immediately terminated. That is, almost no processes or threads that maintain the busy wait state for a long time have been assumed. This is because, as described above, when a process or thread that maintains the busy wait state for a long time is driven, the CPU is used to the performance limit for a long time, and other processes cannot be executed for a long time. .

  However, in recent years, multi-core CPUs and multi-CPU socket servers have become widespread, and the number of CPU cores has increased greatly. As with PMDK of DPDK, it is possible to occupy CPU processing performance and speed up packet processing. became.

Yukimura Yuki, Packet Forwarding Technology, Internet Week 2012, November 20, 2012 N. McKeown, T. Anderson, H. Balakrishnan, G. Parulkar, L. Peterson, J. Rexford, S. Shenker, and J. Turner.OpenFlow: Enabling innovation in campus networks. SIGCOMM Comput. Commun. Rev., 38 (2): 69-74, 2008. Yoshihiro Nakajima, High-speed software packet processing technology using general-purpose x86 server, SDN Japan2014 (2014)

  However, the development trend of commercial technology is not taken into consideration that processes and threads such as PMD are driven for a long time. Also, it is not technically guaranteed that busy wait processes and threads such as PMD operate normally over a long period of time. Therefore, when busy-process processes and threads such as PMD are operated over a long period of time, a means for confirming their normality is indispensable. This is because if the process or thread is stopped, the process or thread must be restarted.

  However, processes and threads that perform high-speed processing using the busy wait method repeatedly execute processing at high speed, and thus cannot respond to a normality confirmation request from the outside.

  The present invention has been made in view of the above points, and an object of the present invention is to make it possible to monitor the status of a process in which reception or transmission of a packet is waited by a loop process.

  Therefore, in order to solve the above problem, the monitoring device waits for reception of a packet by the network interface by a loop process and stores the received packet in a packet storage unit, and the network interface and the packet reception driver. A life / death information storage unit that stores information indicating at least one of the life / death statuses, and the life / death information storage unit, to determine a life / life status of at least one of the network interface and the packet reception driver. The packet reception driver writes information indicating the life / death state in the life / death information storage section between the loop processes.

  It is possible to monitor the status of processing that waits for reception or transmission of a packet by loop processing.

It is a figure which shows the algorithm of the packet reception driver of the conventional spin lock system. It is a figure which shows the algorithm of the packet transmission driver of the conventional spin lock system. It is a figure which shows the hardware structural example of the monitoring apparatus in embodiment of this invention. It is a figure which shows the function structural example of the monitoring apparatus in embodiment of this invention. It is a figure which shows an example of the logical relationship about the function structure in this Embodiment. It is a flowchart for demonstrating an example of the process sequence which a packet reception driver performs. It is a flowchart for demonstrating an example of the process sequence which a packet transmission driver performs. It is a flowchart for demonstrating an example of the process sequence which a monitoring part performs.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 3 is a diagram illustrating a hardware configuration example of the monitoring device according to the embodiment of the present invention. The monitoring device 10 in FIG. 3 includes a drive device 100, an auxiliary storage device 102, a memory device 103, a CPU 104, an interface device 105, and the like that are mutually connected by a bus B.

  A program that realizes processing in the monitoring apparatus 10 is provided by a recording medium 101 such as a CD-ROM. When the recording medium 101 storing the program is set in the drive device 100, the program is installed from the recording medium 101 to the auxiliary storage device 102 via the drive device 100. However, the program need not be installed from the recording medium 101 and may be downloaded from another computer via a network. The auxiliary storage device 102 stores the installed program and also stores necessary files and data.

  The memory device 103 reads the program from the auxiliary storage device 102 and stores it when there is an instruction to start the program. The CPU 104 executes a function related to the monitoring device 10 according to a program stored in the memory device 103. The interface device 105 is, for example, a NIC (Network Interface Card).

  In FIG. 3, the monitoring device 10 may include a plurality of CPUs 104, memory devices 103, interface devices 105, and the like. The interface device 105 may have a plurality of ports.

  FIG. 4 is a diagram illustrating a functional configuration example of the monitoring device according to the embodiment of the present invention. In FIG. 4, the interface device 105 includes a packet receiving unit 151, a packet transmitting unit 152, and the like.

  The packet reception unit 151 corresponds to a part including a line and a circuit on the packet reception side in the interface device 105. When receiving a packet from the network, the packet receiving unit 151 stores the packet in the reception buffer 151m belonging to the packet receiving unit 151.

  The packet transmission unit 152 corresponds to a part including a line and a circuit on the packet transmission side in the interface device 105. The packet transmitter 152 transmits the packet written in the transmission buffer 152m belonging to the packet transmitter 152 to the network.

  The reception buffer 151m and the transmission buffer 152m are realized using a memory included in the interface device 105.

  On the other hand, the user space 11 is a software space that is realized on the OS (Operating System) of the monitoring apparatus 10 by processing that one or more programs installed in the monitoring apparatus 10 cause the CPU 104 to execute. The user space 11 includes a packet reception driver 111, a packet transmission driver 112, an application 113, a monitoring unit 114, and the like. Each of these units is realized by processing that one or more programs installed in the monitoring apparatus 10 cause the CPU 104 to execute.

  The packet reception driver 111 repeatedly refers to the reception buffer 151m by loop processing, and waits for the arrival of the reception packet to the packet reception unit 151. When the reception packet is stored in the reception buffer 151m, the packet reception driver 111 acquires the reception packet from the reception buffer 151m and writes the reception packet in the reception packet storage unit 115. The packet reception driver 111 is activated as a process or thread that repeats the above series of processing at high speed based on the busy wait method or the spin lock method.

  The reception packet storage unit 115 stores the reception packet written by the packet reception driver 111. The received packet storage unit 115 is realized using the memory device 103, for example.

  The application 113 acquires the received packet stored in the received packet storage unit 115 and executes a predetermined process on the received packet. The application 113 also writes a transmission packet related to the processing result or processing request in the transmission packet storage unit 116.

  The transmission packet storage unit 116 stores the transmission packet written by the application 113. Note that the transmission packet storage unit 116 is realized using the memory device 103, for example.

  The packet transmission driver 112 repeatedly refers to the transmission packet storage unit 116 by loop processing, and waits for writing of the transmission packet to the transmission packet storage unit 116. When the transmission packet is written in the transmission packet storage unit 116, the packet transmission driver 112 reads the transmission packet and writes the transmission packet in the transmission buffer 152m. The packet transmission driver 112 is activated as a process or thread that repeats the above series of processes at high speed based on the busy wait method or the spin lock method.

  The life / death information storage unit 117r stores information (hereinafter referred to as “life / life information”) indicating a life / death state (normality) of at least one of the packet reception unit 151 and the packet reception driver 111. That is, for example, the packet reception driver 111 stores the life / death information in the life / death information storage unit 117r between the loop processes (for example, periodically).

  The life / death information storage unit 117t stores life / life information of the packet transmission unit 152 or the packet transmission driver 112. That is, the packet transmission driver 112 stores the life / death information in the life / death information storage unit 117t, for example, between the loop processes (for example, periodically).

  The monitoring unit 114 monitors the normality of at least one of the packet reception unit 151 and the packet reception driver 111 with reference to the life / death information storage unit 117r. The monitoring unit 114 also monitors the normality of at least one of the packet transmission unit 152 and the packet transmission driver 112 with reference to the life / death information storage unit 117t.

  Note that the life and death information storage unit 117r and the life and death information storage unit 117t are realized by using the memory device 103, for example.

  Note that one packet core may be assigned to each of the packet reception driver 111 and the packet transmission driver 112.

  Further, the present embodiment is one of software OpenFlow switches (Non-Patent Document 2) using PDM (Poll Mode Driver) of DPDK (Data Plane Development Kit) library of Intel (registered trademark). Lagopus (Non-Patent Document 3) may be applied. That is, the packet reception driver 111 and the packet transmission driver 112 may be realized by PDM.

  FIG. 5 is a diagram illustrating an example of a logical relationship regarding the functional configuration according to the present embodiment. In FIG. 5, there are four packet receivers 151. In addition, there are two packet reception drivers 111 and eight reception packet storage units 115. There are four applications 113. The number of transmission packet storage units 116 is eight, and the number of packet transmission drivers 112 is two. There are four packet transmitters 152.

  Each packet receiver 151 drives PMD. When each packet receiving unit 151 receives a packet, each packet receiving unit 151 writes the received packet in the reception buffer 151 m of each packet receiving unit 151. Each packet reception driver 111 acquires a reception packet from two reception buffers 151m corresponding to each packet reception driver 111, and writes the reception packet in one of the four reception packet storage units 115 corresponding to each packet reception driver 111. Each application 113 is, for example, Flow Lookup Packet Processing. Each application 113 acquires a received packet from two received packet storage units 115 corresponding to each application 113. Each application 113 writes a transmission packet in two transmission packet storage units 116 corresponding to each application 113. Each application 113 may also drive the PMD.

  Each packet transmission driver 112 drives PMD. Each packet transmission driver 112 acquires a transmission packet from the four transmission packet storage units 116 corresponding to the packet transmission driver 112, and writes the transmission packet in one of the two transmission buffers 152m corresponding to each packet transmission driver 112. Each packet transmission unit 152 transmits the transmission packet written in the transmission buffer 152m.

  In FIG. 5, there is one monitoring unit 114, but the monitoring unit 114 may be provided for each life and death information storage unit 117 r and each life and death information storage unit 117 t.

  Alternatively, in FIG. 5, a life / death information storage unit 117r is arranged for each packet reception driver 111, and a life / death information storage unit 117t is arranged for each packet transmission driver 112. However, a plurality of packet reception drivers 111 or a plurality of packet transmissions are transmitted. One life / death information storage unit 117 may be arranged for the driver 112. In this case, the life / death information may be stored separately for each packet reception driver 111 or packet transmission driver 112.

  Hereinafter, a processing procedure to be executed in the present embodiment will be described. FIG. 6 is a flowchart for explaining an example of a processing procedure executed by the packet reception driver.

  The packet reception driver 111 refers to the reception buffer 151m and confirms whether or not there is a reception packet (S102), when one cycle of N times does not arrive in the high-speed loop processing (No in S101). If there is no received packet (No in S102), the process returns to step S101. When there is a received packet (Yes in S102), the packet reception driver 111 acquires the received packet (S103) and writes it in the received packet storage unit 115 (S104).

On the other hand, when one cycle has arrived every N times (Yes in S101), the packet reception driver 111 checks the alive state (normality) of the packet reception unit 151 (S105). The life / death information of the packet receiver 151 is confirmed as follows, for example. The packet reception driver 111 can send a signal to the hardware packet reception unit 151 and receive a response. Therefore, if the response can be received, the packet reception driver 111 determines that the packet reception unit 151 is in a normal state. Alternatively, the packet reception driver 111 can refer to the reception buffer 151m that is a memory of the packet reception unit 151. If the packet reception driver 111 can refer to the reception buffer 151m, it may be determined that the packet reception unit 151 is in a normal state. Subsequently, the packet reception driver 111 writes life / death information indicating the confirmation result in the life / death information storage unit 117r. (S106). At this time, life and death information written in the past is overwritten with new life and death information.

  Here, if the packet reception driver 111 is not normal (when stopped), steps S105 and S106 are not executed. In this case, life / death information is not written. Therefore, the life and death states of the packet reception driver 111 and the packet reception unit 151 can be distinguished as follows according to the presence or absence of life and death information and the content of life and death information.

  When the life / death information is not stored in the life / death information storage unit 117r, there is an abnormality in at least the packet reception driver 111, and the life / death state of the packet reception unit 151 is unknown.

  When the life / death information is stored in the life / death information storage unit 117r and the life / death information indicates an abnormal state, the packet reception driver 111 is normal, but the packet reception unit 151 is abnormal.

  When the life / death information is stored in the life / death information storage unit 117r and the life / death information indicates a normal state, the packet reception driver 111 and the packet reception unit 151 are normal.

  In this way, the packet reception driver 111 can periodically write life / death information indicating the normality of itself and the packet reception unit 151 in the life / death information storage unit 117r.

  FIG. 7 is a flowchart for explaining an example of a processing procedure executed by the packet transmission driver.

  The packet transmission driver 112 refers to the transmission packet storage unit 116 to confirm the presence / absence of a transmission packet (S202), when one cycle of N times does not arrive in the high-speed loop processing (No in S201). . If there is no transmission packet (No in S202), the process returns to step S201. When there is a transmission packet (Yes in S202), the packet transmission driver 112 acquires the transmission packet (S203) and writes it in the transmission buffer 152m (S204).

On the other hand, when one cycle has arrived every N times (Yes in S201), the packet transmission driver 112 checks the alive state (normality) of the packet transmission unit 152 (S205). The life / death information of the packet transmission unit 152 is confirmed as follows, for example. The packet transmission driver 112 can send a signal to the hardware packet transmission unit 152 and receive a response. Therefore, if the response can be received, the packet transmission driver 112 determines that the packet transmission unit 152 is in a normal state. Alternatively, the packet transmission driver 112 can refer to the transmission packet storage unit 116 that is a memory of the packet transmission unit 152. If the packet transmission driver 112 can refer to the transmission buffer 152m, the packet transmission unit 152 may be determined to be in a normal state. Subsequently, the packet transmission driver 112 writes life / death information indicating the confirmation result to the life / death information storage unit 117t. (S206). At this time, life and death information written in the past is overwritten with new life and death information.

  Here, when the packet transmission driver 112 is not normal (when stopped), steps S205 and S206 are not executed. In this case, life / death information is not written. Therefore, the life and death states of the packet transmission driver 112 and the packet transmission unit 152 can be distinguished as follows depending on the presence or absence of life and death information and the content of life and death information.

  When the life / death information is not stored in the life / death information storage unit 117t, there is an abnormality in at least the packet transmission driver 112, and the life / death state of the packet transmission unit 152 is unknown.

  When the life / death information is stored in the life / death information storage unit 117t and the life / death information indicates an abnormal state, the packet transmission driver 112 is normal, but the packet transmission unit 152 has an abnormality.

  When the life / death information is stored in the life / death information storage unit 117t and the life / death information indicates a normal state, the packet transmission driver 112 and the packet transmission unit 152 are normal.

  As described above, the packet transmission driver 112 can periodically write the life / death information indicating the normality of itself and the packet transmission unit 152 in the life / death information storage unit 117r.

  FIG. 8 is a flowchart for explaining an example of a processing procedure executed by the monitoring unit. For example, FIG. 8 is executed in response to a command input by the user to the monitoring apparatus 10.

  In step S301, the monitoring unit 114 refers to the life / death information storage unit 117r. When the life and death information is stored in the life and death information storage unit 117r (Yes in S302), the monitoring unit 114 indicates that the packet reception driver 111 is normal and the state of the packet reception unit 151 is the state indicated by the life and death information. (S303). Subsequently, the monitoring unit 114 deletes the alive information from the alive information storage unit 117r (S304).

  On the other hand, when the life / death information is not stored in the life / death information storage unit 117r (No in S302), the monitoring unit 114 determines that there is an abnormality in the packet reception driver 111 (S305).

  Subsequent to step S304 or step S305, the monitoring unit 114 refers to the life / death information storage unit 117t (S306). When the life / death information is stored in the life / death information storage unit 117t (Yes in S307), the monitoring unit 114 indicates that the packet transmission driver 112 is normal and the state of the packet transmission unit 152 is the state indicated by the life / death information. (S308). Subsequently, the monitoring unit 114 deletes the life / death information from the life / death information storage unit 117t (S309).

  On the other hand, when the life / death information is not stored in the life / death information storage unit 117t (No in S307), the monitoring unit 114 determines that the packet transmission driver 112 has an abnormality (S310).

  Subsequent to step S309 or step S310, the monitoring unit 114 outputs the determination result (S311).

  It should be noted that a determination on the packet reception driver 111 side only or a determination on the packet transmission driver 112 side alone may be made according to the designation of the parameter for the command.

  By the way, when the processing procedure of FIG. 8 is executed in response to an input of a command, the output determination result may not necessarily be correct. For example, in the processing procedure of FIG. 6, it is assumed that the packet reception driver 111 stops after writing life / death information indicating a normal state to the life / death information storage unit 117r. When the monitoring unit 114 refers to the life / death information storage unit 117r according to the command input thereafter, the monitoring unit 114 determines that the packet reception driver 111 and the packet reception unit 151 are normal based on the life / death information. End up.

  However, such a determination result may be allowed to occur. In this case, if a user inputs a command multiple times in succession, the life / death information is deleted by the process according to the first command input, and the life / death is performed by the process according to the second command input. This is because it is possible to output a determination result indicating that there is an abnormality in the packet reception driver 111 based on the absence of information.

  Alternatively, the monitoring unit 114 may execute the processing procedure of FIG. 8 at a plurality of timings (for example, at regular intervals) regardless of whether or not a command is input by the user. In this case, the determination result may be stored in step S311. When a command is input by the user, the determination result stored last may be output, and the determination result obtained by executing the processing procedure of FIG. 8 is output again at that time. It may be.

  As described above, according to the present embodiment, a thread or process that reads a packet arriving at the NIC at a high speed by a method such as a busy wait method or a spin lock method, or a thread or process that sends a packet to the NIC at a high speed Status monitoring is possible. In other words, it is possible to monitor the status of processing that waits for reception or transmission of a packet by loop processing.

  In the present embodiment, the packet receiver 151, the packet transmitter 152, or the interface device 105 is an example of a network interface.

  As mentioned above, although the Example of this invention was explained in full detail, this invention is not limited to such specific embodiment, In the range of the summary of this invention described in the claim, various deformation | transformation・ Change is possible.

DESCRIPTION OF SYMBOLS 10 Monitoring apparatus 11 User space 100 Drive apparatus 101 Recording medium 102 Auxiliary storage apparatus 103 Memory apparatus 104 CPU
105 interface device 111 packet reception driver 112 packet transmission driver 113 application 114 monitoring unit 115 received packet storage unit 116 transmission packet storage unit 117r alive information storage unit 117t alive information storage unit 151 packet reception unit 151m reception buffer 152 packet transmission unit 152m transmission buffer B bus

Therefore in order to solve the above problems, the monitoring device indicates the reception of a packet by the network interface waits by the loop processing, a packet receiving driver for storing the received packet in the packet storage unit, the life-and-death states of the network interface a vital-information storage unit for storing information, the remove the reference information with reference to information stored in the life-and-death information storage unit, a monitoring unit for monitoring the life-and-death states of the network interface and said packet reception driver have the packet receiving driver, in interval of the loop processing, to check the life-and-death states of the network interface, write the information indicating the life-and-death states in the life-and-death information storage unit, the monitoring unit, If no information is stored in the life and death information storage unit, If the packet reception driver is abnormal and information is stored in the life and death information storage unit, it is determined that the packet reception driver is normal and the network interface is in a state indicated by the information. Judge that there is .

Claims (5)

A packet reception driver that waits for reception of a packet by the network interface by loop processing and stores the received packet in a packet storage unit;
A life / death information storage unit that stores information indicating a life / death state of at least one of the network interface and the packet reception driver;
With reference to the alive information storage unit, a monitoring unit that monitors the alive state of at least one of the network interface and the packet reception driver,
The packet reception driver writes information indicating the life and death state in the life and death information storage unit between the loop processes.
A monitoring device characterized by that. A packet transmission driver that waits for the presence or absence of a packet to be transmitted from the network interface by a loop process and transmits the packet to the network interface when there is a packet to be transmitted;
A life / death information storage unit that stores information indicating a life / death state of at least one of the network interface and the packet transmission driver;
With reference to the alive information storage unit, a monitoring unit that monitors the alive state of at least one of the network interface and the packet transmission driver,
The packet transmission driver writes information indicating the life and death state in the life and death information storage unit between the loop processes.
A monitoring device characterized by that. A packet reception procedure for waiting for reception of a packet by the network interface by loop processing and storing the received packet in a packet storage unit;
A storage procedure for storing information indicating a life / death state of at least one of the network interface and the packet reception procedure in a life / death information storage unit;
The computer executes a monitoring procedure for monitoring the alive state of at least one of the network interface and the packet reception procedure with reference to the alive information storage unit,
The packet reception procedure writes information indicating the life and death state in the life and death information storage unit between the loop processes.
A monitoring method characterized by that. A packet transmission procedure of waiting for the presence or absence of a packet to be transmitted from the network interface by a loop process and transmitting the packet to the network interface when there is a packet to be transmitted;
A storage procedure for storing information indicating a life / death state of at least one of the network interface and the packet transmission procedure in a life / death information storage unit;
The computer executes a monitoring procedure for monitoring the alive state of at least one of the network interface and the packet transmission procedure with reference to the alive information storage unit,
The packet transmission procedure writes information indicating the life and death state in the life and death information storage unit between the loop processes.
A monitoring method characterized by that.   A program that causes a computer to function as each unit according to claim 1.

Images