JP7073737B2 - Communication log recording device, communication log recording method, and communication log recording program - Google Patents

Description

The present invention relates to a communication log recording device, a communication log recording method, and a communication log recording program, particularly a device for efficiently recording a communication log including the order of reception requests issued by an application and received data.

The communication log containing the order of the reception request issued by the application and the reception data is useful data, and is suitable for use in, for example, a data recording type replay method.

Program debugging needs to reproduce the state of the problem. A program that communicates between processes and proceeds with processing, for example, a message passing type / distributed parallel program, communicates between processes and proceeds with processing, so that a communication result is required to reproduce the state. One of the solutions to this problem is a data recording type replay method (Non-Patent Document 1). This records the communication result performed by the debuggee process, and when debugging is executed (replay), the previously recorded communication result is referred to instead of the communication. This eliminates the need for actual communication and enables debugging by executing only the process to be debugged.

Patent Document 1 discloses an execution reproduction method of a parallel program. This method writes a record of access to shared data in main memory by a parallel program running in monitor mode to a system history tape in main memory. This method reproduces the execution of a parallel program using the records written on the system history tape in the replay mode.

In Patent Document 2, the communication log considered to be continuous is buffered in the primary storage area, and when the buffering period expires, the communication log stored in the primary storage area is stored in the secondary storage area. Disclose the information processing device to be processed.

Japanese Unexamined Patent Publication No. 03-240137 Japanese Unexamined Patent Publication No. 2011-060030

Parallel Program Debugging with Data Revival Method IPSJ Journal: Computing Systems, Vol. 46, No. SIG 12 (ACS11), pp. 214-224, August 2005.

Communication logs such as those used in the data recording type replay method of programs that involve data reception are characterized by a large amount of data because they include received data. Many such communication logs cannot be stored in the main memory as disclosed in Patent Document 1. Volatility can also be an issue.

On the other hand, as disclosed in Patent Document 2, when the communication log is buffered in the primary storage area such as main memory and the communication log is later re-stored in the secondary storage area such as a hard disk, this is the case. Input / output for this may adversely affect other processing. That is, when another process waits for the end of input / output of the communication log, this input / output delays the execution of the other process. Even when the input / output of the communication log and the other processing are executed in a row by asynchronous input / output or the like, this input / output has the following adverse effects on the other processing environment.

Problem (a) Special hardware such as a DMA (Direct Memory Access) engine is required even if the program being replayed does not use asynchronous I / O.

Problem (b) A mechanism and resources for the process thread of asynchronous I / O processing are required.

Problem (c) Due to asynchronous input / output processing, the number of CPU (Central Processing Unit) cores that can be used by the program decreases.
Problem (d) Context switch overhead occurs when a process thread and program for asynchronous I / O processing share a CPU core. In addition, when the program being calculated and asynchronous I / O processing are switched, the CPU core usage rate of the calculation decreases. In the present invention, the communication log is buffered in the main memory, etc., and the communication log is later stored in the hard disk, etc. It is an object of the present invention to provide a communication log recording device or the like that can suppress the influence of the input / output at the time of re-storing on other processes when re-storing.

The communication log recording device according to the embodiment of the present invention has a log storage means, a log temporary storage means faster than the log storage means, and a log ID indicating the issuing order of the reception request when the reception request is received. The log collection means that starts generation and reception and stores the log information including the log ID and the read reception data in the log temporary storage means at the end of the reception, and the requested transmission or reception is started. After that, the log storage means for re-storing the log information stored in the log temporary storage means in the log storage means is provided.

In the communication log recording method of one embodiment of the present invention, when a reception request is received, a log ID indicating the issuing order of the reception request is generated and reception is started, and the log ID and the reception are read at the end of the reception. The log information including the received data is stored in the log temporary storage means faster than the log storage means, and the log information stored in the log temporary storage means after the requested transmission or the reception is started. Is stored back in the log storage means.

When a reception request is received by a computer including a log storage means and a log temporary storage means faster than the log storage means, the communication log recording program according to the embodiment of the present invention receives the reception request in the order of issuance of the reception request. The log collection process that generates the log ID indicating the above and starts reception, and stores the log information including the log ID and the read received data in the log temporary storage means at the end of the reception, and the requested transmission or After the reception is started, the log storage process of re-storing the log information stored in the log temporary storage means in the log storage means is executed.

In the communication log recording device or the like according to the present invention, when the communication log is buffered in the main memory or the like and the communication log is later stored in the hard disk or the like, the input / output for re-storing is other. The effect on the processing of

FIG. 1 is a diagram showing a configuration of a communication log recording device 10 according to the first embodiment. FIG. 2 is a diagram showing a data structure of a communication log stored in the log temporary storage unit 15 and the log storage unit 13. FIG. 3 is a diagram showing a data structure of a table stored in the reception request storage unit 16. FIG. 4 is a diagram showing the configuration of the computer device 60. FIG. 5 is a flowchart showing the operation of the log collecting unit 11 when communication is requested. FIG. 6 is a flowchart showing the operation of the log collection unit 11 when a non-blocking communication end wait request is received. FIG. 7 is a flowchart showing the operation of the log storage unit 12. FIG. 8 is a diagram showing the difference in execution time between the case where the communication log of the communication is saved immediately after the end of the communication on the timeline (A) and the case of the communication log recording device 10 (B). FIG. 9 is a diagram showing the configuration of the log temporary storage unit 15 in the second embodiment. FIG. 10 is a flowchart showing the operation of the log storage unit 12 of the second embodiment. FIG. 11 is a timeline showing the effect of the communication log recording device 10 according to the present embodiment. FIG. 12 is a diagram showing the configuration of the communication log recording device 10 according to the third embodiment. FIG. 13 is a diagram showing the configuration of the communication log recording device 10 according to the fourth embodiment.

<First embodiment>
<Overview>
The communication log recording device 10 according to the present embodiment divides the recording of the communication log into two phases of collecting the log and saving the log. In the log collection phase, the communication log recording device 10 collects communication logs and temporarily records them in a high-speed recording medium, for example, a log temporary storage unit 15 such as a semiconductor memory. In the subsequent log storage phase, the communication log recording device 10 moves the communication log from the log temporary storage unit 15 to the log storage unit 13 such as an HDD (Hard Disk Drive) during the communication waiting time.

<Structure>
FIG. 1 is a diagram showing a configuration of a communication log recording device 10 according to the present embodiment. The communication log recording device 10 includes a log collecting unit 11, a log storage unit 12, a log storage unit 13, a communication counter 14, a log temporary storage unit 15, a reception request storage unit 16, a communication processing unit 21, and a communication waiting unit 22. Be prepared. Further, the communication log recording device 10 includes an application 17 which is a main body requesting communication. This subject may be a program or hardware such as an image processor.

The log collection unit 11 executes the log collection phase described above. That is, the log collection unit 11 executes the communication requested by the application 17, collects the communication log, and temporarily records it in the log temporary storage unit 15. The log storage unit 12 executes the above-mentioned log collection phase. That is, the log storage unit 12 reads the communication log from the log temporary storage unit 15 during the communication waiting time and stores it in the log storage unit 13 again. The communication log is accumulated in the log storage unit 13.

The communication counter 14 is a counter that records the order of communication requested by the application 17. The initial value is 1. When the log collection unit 11 receives a communication request from the application 17, the log ID (Identification) is generated in order from this, and the value of the communication counter 14 is incremented by one.

The communication processing unit 21 starts communication, and the communication waiting unit 22 waits for the end of communication. The communication referred to here is, for example, interprocess communication, but may be input / output to a disk device or communication with a remote device via a communication network. The reception request storage unit 16 stores a table for obtaining the log ID of the completed communication when the non-blocking type, that is, the asynchronous type communication is executed.

FIG. 2 is a diagram showing a data structure of a communication log stored in the log temporary storage unit 15 and the log storage unit 13. The communication log is acquired each time the application 17 requests communication, and is stored in one row of the table in FIG. The communication log includes each data item of log ID, communication procedure, execution result, received data, and end flag.

The log ID represents the order of communication requested by the application 17. The log ID may include other information, such as an application 17 identifier or a process identifier. The received data represents the content of the data received in the request. The log ID can be used, for example, to output correct received data in response to a communication request when the application 17 is replayed. That is, if the system that executes the replay is the nth (n is an integer) communication request is a reception request, the system may output the reception data of the communication log having the log ID indicating the nth to the application 17. good.

The communication procedure indicates the type of the request. The communication procedure indicates the distinction between reception / transmission and the distinction between synchronous communication / asynchronous communication. Synchronous input / output / asynchronous input / output may be referred to as blocking / non-blocking. The execution result indicates whether or not the communication has ended normally.

The end flag is held only in the communication log in the log temporary storage unit 15, and indicates whether or not the reception / transmission of the communication request has been completed. The end flag has an initial value of 0, indicating that communication is being executed, and becomes 1 when communication ends. The log storage unit 12 re-stores the communication log of the communication request for which reception / transmission has been completed from the log temporary storage unit 15 to the log storage unit 13. The log storage unit 12 removes the end flag when the communication log is re-stored in the log storage unit 13 from the log temporary storage unit 15.

If it is not necessary at the time of replay, the communication log does not have to include the communication procedure or the execution result. For example, when the communication result is always normal and the replay is performed. Further, if the transmission result is not a concern at the time of replay, for example, if the replay is always performed as a normal end, the communication log may be acquired only for reception.

FIG. 3 is a diagram showing a data structure of a table stored in the reception request storage unit 16. This table stores the association between the receive request ID and the log ID for the non-blocking type communication request being executed. The reception request ID is an identifier of the communication request issued by the application 17. The reception request ID may be any information that can identify the non-blocking type communication being executed. The reception request ID is, for example, the address of the control information case variable for managing the non-blocking type communication during execution or the subscript variable value of the array element.

Here, the log collection unit 11, the log storage unit 12, the communication processing unit 21, and the communication waiting unit 22 of the communication log recording device 10 are composed of a logic circuit or a dedicated processor and firmware. The log storage unit 13 is a storage device such as an HDD or an SDD (Solid State Drive). The communication counter 14, the log temporary storage unit 15, and the reception request storage unit 16 are semiconductor storage devices.

The communication log recording device 10 may be composed of a computer device 60. FIG. 4 is a diagram showing the configuration of the computer device 60. The computer device 60 includes a processor 61, a main storage device 63, and an external storage device 62, which are interconnected by a bus 64.

The processor 61 reads / writes data to / from the main storage device 63 and the external storage device 62 via the bus 64. Further, the processor 61 executes the communication log recording program 65 stored in the main storage device 63. The communication log recording program 65 is initially stored in the external storage device 62, and the processor 61 may load the communication log recording program 65 from the external storage device 62 to the main storage device 63 at the time of initial setting of the computer device 60.

Here, the main storage device 63 is a semiconductor storage device. The external storage device 62 is a storage device such as an HDD or an SDD.

By executing the communication log recording program 65, the processor 61 of the computer device 60 functions as a log collection unit 11, a log storage unit 12, a communication processing unit 21, and a communication waiting unit 22. That is, by executing the communication log recording program 65, the processor 61 executes the processing performed by the log collection unit 11, the log storage unit 12, the communication processing unit 21, and the communication waiting unit 22.

The main storage device 63 is used as a communication counter 14, a log temporary storage unit 15, and a reception request storage unit 16. The external storage device 62 is used as the log storage unit 13.

<Operation>
FIG. 5 is a flowchart showing the operation of the log collecting unit 11 when communication is requested.

The log collection unit 11 is started when the application 17 requests communication. When started, the log collection unit 11 requests the communication processing unit 21 to start communication (S11). After that, the log collection unit 11 generates a log ID by referring to the communication counter 14 (S12), and stores the log ID, communication procedure, execution result, and end flag in an empty line of the log temporary storage unit 15. (S13). Here, for the execution result, for example, the value reported by the communication processing unit 21 is set. The end flag is set to 0.

After that, the log collection unit 11 requests the log storage unit 12, and if the log temporary storage unit 15 has an unsaved communication log with an end flag of 1, the communication log is stored again in the log storage unit 13 ( S14). What is stored again here is the communication log for the communication executed in the past. FIG. 7 is a flowchart of this operation, which will be described later.

When the started communication is blocking type communication (YES in S15), the log collection unit 11 waits for the end of communication in the communication waiting unit 22, sets the end flag of the communication log stored in S14 to 1, and starts from the communication waiting unit 22. The obtained execution result is stored in the log temporary storage unit 15 (S17). In the case of reception, the log collecting unit 11 also stores the received data obtained from the communication waiting unit 22 in the log temporary storage unit 15. After that, the log collection unit 11 finishes the process.

When the started communication is non-blocking communication (NO in S15, YES in S16), the log collection unit 11 stores the reception request ID and the log ID in an empty line of the reception request storage unit 16 (S18). After that, the log collection unit 11 finishes the process.

If the started communication is other, for example, transmission (NO in S15, NO in S16), the log collection unit 11 ends the process.

FIG. 6 is a flowchart showing the operation of the log collection unit 11 when a non-blocking communication end wait request is received.

It is started when the application 17 requests the end wait request for non-blocking communication, and the log collection unit 11 waits for the end of the communication specified by the input reception request ID in the communication waiting unit 22 (S21). When the designated communication is completed, the log collection unit 11 searches the reception request storage unit 16 and acquires the log ID from the line whose reception request ID matches the specified reception request ID (S22).

Next, the log collection unit 11 searches the log temporary storage unit 15, accesses the communication log whose log ID matches the log ID acquired in the previous step, sets the end flag to 1, and starts from the communication waiting unit 22. The obtained execution result is stored (S23). In the case of reception, the log collecting unit 11 also stores the received data obtained from the communication waiting unit 22 in the communication log. After that, the log collection unit 11 deletes the data of the line accessed in S22 from the reception request storage unit 16 (S24), and ends the process.

The log collection unit 11 may provide the application 17 with an end confirmation request in addition to the end wait request as an interface for synchronizing the end of non-blocking communication. When the end confirmation is requested, the log collection unit 11 checks the end of communication instead of S21, executes the steps after S22 if it ends, and reports to the application 17 if it does not end. Just do it.

FIG. 7 is a flowchart showing the operation of the log storage unit 12. This flowchart illustrates the process of S14 in FIG. 5 in detail.

When the log storage unit 12 started from the log collection unit 11 has a communication being executed and a communication log having an end flag of 1 exists in the log temporary storage unit 15 (YES in S31), the log temporary storage unit 15 The communication log whose end flag is 1 is read from and stored in the log storage unit 13 (S32, S33). That is, the log storage unit 12 re-stores the communication log whose end flag is 1 from the log temporary storage unit 15 to the log storage unit 13. After that, the log storage unit 12 deletes the communication log that has been stored in the log storage unit 13 from the log temporary storage unit 15 (S34), and returns to S31.

If there is no running communication or there is no communication log with the end flag 1 in the log temporary storage unit 15 (NO in S31), the log storage unit 12 ends the process and restarts the log collection unit 11.

<Effect>
When the communication log recording device 10 according to the present embodiment buffers the communication log in the log temporary storage unit 15 such as main storage and later stores the communication log in the log storage unit 13 such as an HDD. , The influence of input / output for re-storing on other processing can be suppressed. The reason is that the communication log stored in the log temporary storage unit 15 is re-stored in the log storage unit 13 while the log storage unit 12 is executing the communication.

By using the communication waiting time for re-storing the communication log from the log temporary storage unit 15 to the log storage unit 13, the communication log recording device 10 is used for calculation without using asynchronous input / output. It is possible to reduce the increase in execution time due to the movement of communication logs without reducing the CPU resources required.

FIG. 8 shows execution when the communication log of the communication is saved immediately after the end of the communication on the timeline (A in the figure) and in the case of the communication log recording device 10 according to the present embodiment (B in the figure). It represents the difference in time. The communication log recording device 10 according to the present embodiment is timed so that, for example, the communication log of the communication a is not re-stored after the end of the communication a, but is performed in parallel during the execution of the next communication b. Is changed (arrow in the figure). As a result, the communication log recording device 10 prevents the delay in the calculation of the application 17 that occurs when the communication log of the communication a is re-stored by the synchronous input / output. Further, the communication log recording device 10 has an influence on the calculation of the application 17 (overhead of context change, etc.) that the input / output has when the communication log of the communication a is re-stored by the asynchronous input / output. It can be prevented.

<Second embodiment>
<Configuration and operation>
The communication log recording device 10 of the present embodiment includes a general-purpose OS (Operating System) and executes a plurality of processes in parallel. The log collection unit 11, the log storage unit 12, the application 17, the communication processing unit 21, and the communication waiting unit 22 are started by a process. The communication log recording device 10 of the present embodiment includes a log storage unit 13, a communication counter 14, a log temporary storage unit 15, and a reception request storage unit 16 for each process. However, the log storage unit 13 and the log temporary storage unit 15 can also be accessed from another process.

FIG. 9 is a diagram showing the configuration of the log temporary storage unit 15 in the present embodiment. The log temporary storage unit 15 for each process is arranged on the interprocess shared memory of the communication log recording device 10. The log temporary storage unit 15 for each process is the same as that of the first embodiment.

The log collection unit 11 stores the communication log reflecting the communication of the started process (also referred to as the own process) for each process in the log temporary storage unit 15 provided in the own process. The log storage unit 12 re-stores the communication log of the log temporary storage unit 15 provided in the own process in the log storage unit 13 provided in the own process. However, if the communication log with the end flag 1 does not exist in the log temporary storage unit 15 provided in the own process, the communication log of the log temporary storage unit 15 provided in the process other than the own process (also referred to as another process) is used. , It is stored again in the log storage unit 13 provided in another process.

FIG. 10 is a flowchart showing the operation of the log storage unit 12 of the present embodiment. When started from the log collection unit 11 started by the process, the log storage unit 12 first starts the next process and checks whether there is any communication that is being executed, that is, if there is communication that has not been completed yet (S41). NO) Ends the process.

If there is a communication being executed (YES in S41), the log storage unit 12 checks whether the communication log having the end flag of 1 exists in the log temporary storage unit 15 of the own process. If there is (YES in S42), the log storage unit 12 re-stores the communication log of the log temporary storage unit 15 provided in the own process in the log storage unit 13 provided in the own process, and stores the communication log. Delete from the log temporary storage unit 15 (S43 to S45), and return to S41.

If not (NO in S42), the log storage unit 12 checks whether the communication log having the end flag of 1 exists in the log temporary storage unit 15 of another process. If there is (YES in S46), the log storage unit 12 re-stores the communication log of the log temporary storage unit 15 provided in the other process in the log storage unit 13 provided in the other process, and performs the communication. The log is deleted from the log temporary storage unit 15 (S47 to S49), and the process returns to S41.

<Effect>
The communication log recording device 10 of the present embodiment uses the communication waiting time of a certain process for re-storing the communication log of another process from the log temporary storage unit 15 to the log storage unit 13, as described above. Can produce the desired effect. The reason is that the log storage unit 12 re-stores the communication log of the log temporary storage unit 15 provided in the other process in the log storage unit 13 provided in the other process.

FIG. 11 is a timeline showing the effect of the communication log recording device 10 according to the present embodiment. In the figure, it is assumed that the communication log of the communication a executed by the process A is acquired by the log temporary storage unit 15, and the communication wait does not occur in the subsequent communication b. In this case, in the communication log recording device 10 of the first embodiment, the communication log of the communication a is left in the log temporary storage unit 15 of the process A for a long time. In the worst case, the log storage unit 13 is re-stored in the process A termination process, and the termination process is delayed.

In the communication log recording device 10 of the present embodiment, the communication log of the communication a of the process A is stored as a log from the log temporary storage unit 15 of the process A by using the communication waiting time of the communication d of the other process B. It is stored back in the unit 13. As a result, the above-mentioned processing delay can be prevented.

<Third embodiment>
When the received data is very large, the time for re-storing the communication log from the log temporary storage unit 15 to the log storage unit 13 may be longer than the communication execution time. In this case, the processing of the application 17 is delayed by the excess time. In order to prevent this, the communication log recording device 10 of the present embodiment divides the storage of the communication log into a plurality of sections instead of the communication log unit.

FIG. 12 is a diagram showing the configuration of the communication log recording device 10 according to the present embodiment. The communication log recording device 10 according to the present embodiment includes a storage information storage unit 18 in addition to the configuration of the communication log recording device 10 according to the first embodiment. The storage information storage unit 18 stores storage information indicating which section divided into predetermined sizes has been re-stored in the log storage unit 13 from the log temporary storage unit 15, that is, saved information.

When it detects that the size of the communication log is equal to or larger than the predetermined number of bytes, the log storage unit 12 divides the communication log into sections of a predetermined size, and each time a waiting for the end of communication execution occurs, the log storage unit 12 sequentially starts from the beginning one section at a time. Is stored again in the log storage unit 13 from the log temporary storage unit 15. In the process, the log storage unit 12 records in the storage information storage unit 18 which section of the communication log has been re-stored, that is, whether the communication log has been stored. The log storage unit 12 re-stores the next section indicated by the storage information storage unit 18 from the log temporary storage unit 15 to the log storage unit 13 each time a communication execution end wait occurs. The log storage unit 12 repeats this operation until the re-storing of all the sections is completed, and then deletes the communication log from the log temporary storage unit 15.

<Fourth Embodiment>
FIG. 13 is a diagram showing the configuration of the communication log recording device 10 according to the present embodiment. The communication log recording device 10 according to the present embodiment includes a log storage unit 13, a log temporary storage unit 15 faster than the log storage unit 13, a log collection unit 11, and a log storage unit 12.

When the log collection unit 11 receives the reception request, it generates a log ID indicating the order in which the reception request is issued and starts reception, and temporarily stores the log information including the log ID and the read reception data at the end of reception. Store in unit 15. After the requested transmission or reception is started, the log storage unit 12 re-stores the log information stored in the log temporary storage unit 15 in the log storage unit 13.

When the communication log recording device 10 according to the present embodiment buffers the communication log in the log temporary storage unit 15 such as main storage and later stores the communication log in the log storage unit 13 such as an HDD. , The influence of input / output for re-storing on other processing can be suppressed. The reason is that the communication log stored in the log temporary storage unit 15 is re-stored in the log storage unit 13 while the log storage unit 12 is executing the communication.

Although the present invention has been described above with reference to the embodiments, the present invention is not limited to the above embodiments. Various modifications that can be understood by those skilled in the art can be made to the structure and details of the present invention within the scope of the present invention.

10 Communication log recording device 11 Log collection unit 12 Log storage unit 13 Log storage unit 14 Communication counter 15 Log temporary storage unit 16 Reception request storage unit 17 Application 18 Storage information storage unit 21 Communication processing unit 22 Communication waiting unit 60 Computer device 61 Processor 62 External storage device 63 Main storage device 64 Bus 65 Communication log recording program

Claims (10)

Log storage means and
A log temporary storage means faster than the log storage means,
When the reception request is received, a log ID indicating the issuing order of the reception request is generated and reception is started, and at the end of the reception, the log information including the log ID and the read reception data is stored in the log temporary storage means. Log collection means to store and
If there is communication in progress after the requested transmission or reception is started, and there is a communication log for which communication has ended in the log temporary storage means, the log of the communication log for which communication has ended. A communication log recording device including a log storage means for re-storing information in the log storage means. Log storage means and
A log temporary storage means faster than the log storage means,
When the reception request is received, a log ID indicating the issuing order of the reception request is generated and reception is started, and at the end of the reception, the log information including the log ID and the read reception data is stored in the log temporary storage means. Log collection means to store and
A log storage means for re-storing the log information stored in the log temporary storage means in the log storage means after the requested transmission or reception is started is provided.
When the log collecting means receives the synchronous reception request, the log ID is generated and the reception is started, and after waiting for the end of the reception, the log information including the generated log ID and the reception data is included. Is stored in the log temporary storage means.
Communication log recording device. Log storage means and
A log temporary storage means faster than the log storage means,
When the reception request is received, a log ID indicating the issuing order of the reception request is generated and reception is started, and at the end of the reception, the log information including the log ID and the read reception data is stored in the log temporary storage means. Log collection means to store and
After the requested transmission or reception is started, the log storage means for re-storing the log information stored in the log temporary storage means in the log storage means, and a log storage means.
It is provided with a reception request ID for identifying the asynchronous type reception request being executed and a reception request storage means for storing the log ID in association with each other.
The log collecting means 1) receives the asynchronous reception request, generates the log ID, acquires the reception request ID, associates the two, and stores the log ID in the reception request storage means. After executing the process of starting reception, the execution of the application that issued the reception request is restarted. 2) At the end of the reception, the reception request storage means associated with the reception request ID of the completed reception. The log ID stored in the log ID and the log information including the received data are stored in the log temporary storage means.
Communication log recording device. The log storage means and the log temporary storage means are provided for each process executed by the communication log recording device.
The log collecting means is started by each of the processes, and the log information is stored in the log temporary storage means provided in the started process.
The log storage means is executed by each of the processes, and the log information stored in the log temporary storage means provided in the process different from the started process can be used as another log information. The communication log recording device according to any one of claims 1 to 3, which is re-stored in the log storage means provided in the process. A storage information storage means for storing storage information indicating which section of the log information is divided into predetermined sizes is stored in the log storage means.
Claims 1 to claim 1, wherein the log storage means re-stores the next section indicated by the save information from the log temporary storage means into the log storage means, and records the section in the save information as saved. Communication log recording device according to any one of 4. When a reception request is received, a log ID indicating the issuing order of the reception request is generated and reception is started, and at the end of the reception, log information including the log ID and the read reception data is faster than the log storage means. Store in log temporary storage means,
If there is communication in progress after the requested transmission or reception is started, and there is a communication log for which communication has ended in the log temporary storage means, the log of the communication log for which communication has ended. A communication log recording method that stores information back in the log storage means. When a synchronous reception request is received , a log ID indicating the issuance order of the reception request is generated and reception is started, and after waiting for the end of the reception, the generated log ID and the read reception data are combined. The log information including is stored in the log temporary storage means, which is faster than the log storage means .
A communication log recording method for re-storing the log information in the log temporary storage means in the log storage means after the requested transmission or reception is started . When an asynchronous reception request is received, a log ID indicating the order in which the reception request is issued is generated and reception is started. 1 ) The log ID is generated and the running asynchronous reception request is identified. After executing the process of acquiring the reception request ID and storing the two in association with each other in the reception request storage means and the process of starting the reception, the execution of the application that issued the reception request is restarted. 2) The above. At the end of reception, the log ID stored in the reception request storage means associated with the reception request ID of the completed reception and the log information including the read reception data are stored in the log temporary storage means. Store in
A communication log recording method for re-storing the log information in the log temporary storage means in the log storage means after the requested transmission or reception is started . A computer provided with a log storage means and a log temporary storage means faster than the log storage means.
When the reception request is received, a log ID indicating the issuing order of the reception request is generated and reception is started, and at the end of the reception, the log information including the log ID and the read reception data is stored in the log temporary storage means. Log collection processing to be stored and
If there is communication in progress after the requested transmission or reception is started, and there is a communication log whose communication has ended in the log temporary storage means, the log of the communication log whose communication has ended. A communication log recording program that executes a log storage process that stores information back in the log storage means. A computer provided with a log storage means and a log temporary storage means faster than the log storage means.
When a synchronous reception request is received, a log ID indicating the issuance order of the reception request is generated and reception is started, and after waiting for the end of the reception, the generated log ID and the read reception data are combined. Log collection processing to store the included log information in the log temporary storage means ,
After the requested transmission or reception is started , the communication log recording for executing the log storage process of re-storing the log information stored in the log temporary storage means in the log storage means. program.

Images