JP7597355B2 - Information processing device - Google Patents

Description

The present invention relates to an information processing device, an initialization method, and a program.

In systems with peripheral devices connected, all paths to the peripheral devices may be initialized before the OS starts up in order to ensure I/O (Input/Output) performance and reliability after the OS (Operating System) starts up.

One example of a document that describes the initialization of such peripheral devices is Patent Document 1. Patent Document 1 describes a computer system having a main memory means for storing data indicating the internal state of the system, and an interface means for interfacing with at least one peripheral device including a communication device. According to Patent Document 1, the system has a storage means for storing the memory contents of the main memory means, a state storage processing means for storing the memory contents of the main memory means immediately before power is turned off in the storage means, a state recovery means for recovering the memory contents stored in the storage means when power is turned on again, and an initialization means for initializing a part of the memory contents recovered by the state recovery means based on the current state of the peripheral device obtained via the interface means.

Japanese Patent Application Publication No. 05-333962

In the case of the technology described in Patent Document 1, for example, there are cases where it is not possible to respond to cases where the device configuration changes while the power is off, and there are issues with ensuring reliability. Another method for ensuring reliability is to issue I/O to all paths before starting the OS and determine whether the paths are valid or not based on the results. However, when checking whether all paths are valid or not, it takes a very long time because I/O is issued for all paths.

As such, there has been a problem that it can be difficult to boot the OS quickly while ensuring reliability. Therefore, the objective of the present disclosure is to provide an information processing device, an initialization method, and a program that solve the problem that it can be difficult to boot the OS quickly while ensuring reliability.

In order to achieve this object, an information processing device according to one embodiment of the present disclosure includes:
An information processing device connected to a plurality of devices via a plurality of paths,
The system has an initialization unit that initializes only some of a plurality of paths connected to a device to be initialized.

In addition, an initialization method according to another aspect of the present disclosure includes:
An information processing device connected to each of a plurality of devices via a plurality of paths,
When initialization of one of a plurality of paths connecting to a device is successful, initialization is not performed on the other paths connecting to the device, but initialization is performed on paths connecting to other devices.

In addition, a program according to another aspect of the present disclosure includes:
An information processing device connected to each of a plurality of devices via a plurality of paths,
This is a program for realizing an initialization unit that initializes only some of the paths among a plurality of paths connected to a device to be initialized.

The above-mentioned configurations make it possible to boot the OS quickly while ensuring reliability.

FIG. 2 is a diagram illustrating a configuration example of a host device and a group of devices according to the first embodiment of the present disclosure. 2 is a block diagram showing a configuration example of a system initializer shown in FIG. 1; FIG. 3 is a diagram showing an example of a device management table shown in FIG. 2 . FIG. 3 is a diagram showing an example of a path management table shown in FIG. 2; FIG. 2 is a block diagram showing an example of the configuration of an OS shown in FIG. 1 . 11 is a flowchart showing an example of the operation of a system initializer at the time of initial startup. 13 is a flowchart showing an example of the operation of the system initializer from the second time onward. 10 is a flowchart showing an example of the operation of an OS at the time of initial booting. 13 is a flowchart illustrating an example of the operation of the OS from the second time onward. FIG. 11 is a diagram illustrating an example of a hardware configuration of an information processing device according to a second embodiment of the present disclosure. 1 is a block diagram showing an example of the configuration of an information processing device;

[First embodiment]
A first embodiment of the present disclosure will be described with reference to FIGS. 1 to 9. FIG.
FIG. 2 is a diagram showing an example of the configuration of a host device 100 and a device 200. FIG. 2 is a block diagram showing an example of the configuration of a system initializer 110. FIG. 3 is a diagram showing an example of a device management table 111. FIG. 4 is a diagram showing an example of a path management table 112. FIG. 5 is a block diagram showing an example of the configuration of an OS 130. FIGS. 6 and 7 are flow charts showing an example of the operation of the system initializer 110. FIGS. 8 and 9 are flow charts showing an example of the operation of the OS.

In the first embodiment of the present disclosure, a host device 100 connected to multiple devices 200 via paths will be described. In this embodiment, the host device 100 initializes paths connecting to the devices 200 at startup. As will be described later, in this embodiment, the host device 100 initializes only some of the multiple paths connecting to the devices 200 to be initialized and then starts the OS 130. Then, after starting the OS 130, the host device 100 initializes the remaining paths.

As described later, the device 200 to be initialized differs depending on whether or not a priority, which will be described later, has been acquired. For example, when a priority has been acquired, the device 200 to be initialized is one of the devices 200 connected to the host device 100 whose priority is equal to or higher than the priority threshold. In other words, when a priority has been acquired, the system initializer 110, which will be described later, selects one of the devices 200 connected to the host device 100 whose priority is equal to or higher than the priority threshold as a device 200 to be initialized. On the other hand, when a priority has not been acquired, the device 200 to be initialized is all the devices 200 connected to the host device 100. In other words, when a priority has not been acquired, the system initializer 110 selects all the devices 200 connected to the host device 100 as a device 200 to be initialized. Note that the device 200 to be initialized may be other than the above examples.

Figure 1 shows an example of the configuration of a host device 100. Referring to Figure 1, the host device 100 is connected to each device 200 constituting the peripheral device group using multiple paths. For example, in the case shown in Figure 1, the host device 100 is connected to each device 200 using four paths. Note that the host device 100 may be connected to the device 200 using a number of paths other than those shown in the above example, such as three paths. Also, the number of paths may differ for each device 200.

Referring to FIG. 1, the host device 100 has, for example, a system initializer 110, an OS start process 120, and an OS 130. For example, the host device 100 has a calculation device such as a CPU, and a storage device. For example, the host device 100 can realize each of the above-mentioned processing units by the calculation device executing a program stored in the storage device. The host device 100 may realize each of the above-mentioned processing units by hardware or a combination of hardware and software.

The system initializer 110 performs path initialization processing before starting the OS 130. FIG. 2 shows an example of the configuration of the system initializer 110. Referring to FIG. 2, for example, the system initializer 110 can have a device management table 111 and a path management table 112. The system initializer 110 also has, as its main processing units, a device management table copy unit 113, a path information acquisition unit 114, a path selection unit 115, an initialization I/O issuing unit 116, an I/O result checking unit 117, and a table update unit 118.

The device management table 111 is a table for managing each device 200, which is a group of peripheral devices connected to the host device 100. FIG. 3 shows an example of the configuration of the device management table 111. Referring to FIG. 3, the device management table 111 includes, for example, a device identification name, a path ID, and a validity flag.

Here, the device identification name is identification information that uniquely identifies the device 200. The device identification name is given in advance to each device 200. The connection path name is identification information for identifying a path connected to the device 200 indicated by the device identification name. The connection path name is given in advance to each path. The valid flag is a flag that indicates whether the path indicated by the connection path name is valid or invalid.

The path management table 112 is a table for managing the path initialization process. For example, the path management table 112 is generated by the device management table copy unit 113, which will be described later, copying the device management table 111. By managing the path initialization process using the path management table 112 generated by copying the device management table 111, it is possible to manage the path initialization process without interfering with other processing units that reference the device management table 111.

Figure 4 shows an example of the configuration of the path management table 112. Referring to Figure 4, the path management table 112 includes, for example, a device identification name, a path ID, a validity flag, an initialization flag, a priority, and an access time.

Here, the device identification name, path ID, and validity flag are the same as those in the device management table 111. Therefore, a description will be omitted. The initialization flag is a flag indicating whether or not initialization processing has been performed on the path indicated by the connection path name. The initialization flag is updated by performing the initialization processing. The priority indicates the priority when executing the initialization processing for the second or subsequent times. Details of the priority will be described later. The access time indicates the time of the first access to the device 200 indicated by the device identification name. For example, the access time indicates a relative time (e.g. μs) with the start of operation of the initializer 110 being 0 seconds.

The device management table copy unit 113 generates the path management table 112 by copying the device management table 111. In addition, when the device management table 111 is updated, the device management table copy unit 113 reflects the updated information in the path management table 112.

For example, when the path management table 112 has not been generated, such as when the system initializer 110 is started for the first time, the device management table copy unit 113 generates the path management table 112 by copying the device management table 111.

In addition, when the path management table 112 has already been generated, such as when the system initializer 110 is started for the second or subsequent time, the device management table copy unit 113 checks whether the device management table 111 has been updated by comparing the path management table 112 with the device management table 111. If the device management table 111 has been updated, the device management table copy unit 113 reflects the updated information in the path management table 112.

For example, as described above, the device management table copy unit 113 generates and updates the path management table 112 when the system initializer 110 is started.

The path information acquisition unit 114 acquires path information including the path ID by referring to the path management table 112.

The path information acquisition unit 114 acquires path information using different criteria depending on whether or not a priority has been set, for example. In other words, the path information acquisition unit 114 acquires path information selected using different criteria depending on whether a priority has not yet been acquired, such as when the system initializer 110 is started for the first time, and whether a priority has been acquired, such as when the system initializer 110 is started for the second or subsequent times.

For example, if the priority has not been acquired, the path information acquisition unit 114 acquires any path information corresponding to any device 200, such as the top of the table. After that, initialization processing, such as issuing an initialization I/O, is performed on the path indicated by the path information acquired by the path information acquisition unit 114.

The path information acquisition unit 114 also acquires path information according to the result of the initialization process. For example, if the initialization process fails, the path information acquisition unit 114 acquires other arbitrary path information corresponding to the same device 200 as the path for which the initialization process was performed. On the other hand, if the initialization is successful, the path information acquisition unit 114 acquires arbitrary path information corresponding to the next device 200. The next device 200 may be determined in any manner, such as according to the order of the table.

For example, as described above, when the priority has not been acquired, the path information acquisition unit 114 acquires any path information corresponding to any device 200. Furthermore, the path information acquisition unit 114 acquires path information so that initialization is successful for one of the multiple paths connecting to the device 200. In other words, when initialization is successful for one of the multiple paths connecting to the device 200, the path information acquisition unit 114 acquires path information corresponding to the other devices 200 without acquiring other path information corresponding to the device 200 for which the initialization has been successful.

Also, for example, when the priority has been acquired, the path information acquisition unit 114 acquires any path information corresponding to the device 200 with the highest priority among the devices 200 whose priority is equal to or greater than the priority threshold. After that, initialization processing such as issuing an initialization I/O is performed on the path indicated by the path information acquired by the path information acquisition unit 114. Note that the priority threshold may be any value.

The path information acquisition unit 114 also acquires path information according to the result of the initialization process. For example, if the initialization process fails, the path information acquisition unit 114 acquires any other path information corresponding to the same device 200 as the path for which the initialization process was performed. On the other hand, if the initialization is successful, the path information acquisition unit 114 acquires any path information corresponding to the device 200 with the next highest priority.

For example, as described above, when the priority has been acquired, the path information acquisition unit 114 performs the initialization process on the devices 200 whose priority is equal to or greater than the priority threshold, in descending order of priority. In other words, the path information acquisition unit 114 does not acquire path information corresponding to the devices 200 whose priority is less than the priority threshold. In addition, the path information acquisition unit 114 acquires path information so that the initialization is successful for one of the multiple paths connecting to the device 200 to be initialized. In other words, when the initialization is successful for one of the multiple paths connecting to the device 200, the path information acquisition unit 114 acquires path information corresponding to the other devices 200 without acquiring other path information corresponding to the device 200 whose initialization was successful.

When there are multiple devices 200 with the same priority, the path information acquisition unit 114 may acquire path information corresponding to a device 200 selected from among the devices 200 with the same priority in any manner.

The path selection unit 115 selects a path for issuing an initialization I/O based on the path information acquired by the path information acquisition unit 114. For example, the path selection unit 115 selects a path indicated by a path ID included in the path information.

The initialization I/O issuing unit 116 issues an initialization I/O to the path selected by the path selection unit 115 after the path information acquisition unit 114 acquires the path information. The initialization I/O issuing unit 116 may have a known configuration.

The I/O result check unit 117 checks whether the initialization was successful or not, depending on the result of the initialization I/O issued by the initialization I/O issuing unit 116. The configuration of the I/O result check unit 117 may also be a known one.

The table update unit 118 updates the path management table 112 according to the result of the check by the I/O result check unit 117. For example, if the I/O result check unit 117 determines that the initialization was successful, the table update unit 118 changes the valid flag and the initialization flag in the path management table 112 corresponding to the path for which the initialization process was performed to on. On the other hand, if the I/O result check unit 117 determines that the initialization was unsuccessful, the table update unit 118 changes the valid flag in the path management table 112 corresponding to the path for which the initialization process was performed to off, and changes the initialization flag to on.

In addition, the table update unit 118 can change the valid flag and initialization flag in the path management table 112 to off when the system initializer 110 is started for the second or subsequent times.

The OS start process 120 starts the OS 130 after the system initializer 110 performs initialization processing on the device 200 to be initialized. As described above, the system initializer 110 performs initialization processing on the device 200 to be initialized so that initialization is successful for one of the multiple paths connecting to the device 200. Therefore, the OS start process 120 starts the OS 130 at the stage where initialization is successful for one of the multiple paths connecting to each device 200 to be initialized. In other words, the OS start process 120 starts the OS 130 at the stage where initialization is successful for some paths that satisfy predetermined conditions. The OS start process 120 may be a known process.

OS 130 performs initialization processing for paths that were not initialized by system initializer 110. Furthermore, when I/O is issued to a device 200 for which no paths have been initialized, OS 130 initializes the paths before issuing the I/O. Furthermore, OS 130 measures priority according to the access time and user when the I/O is issued.

Figure 5 shows an example of the configuration of OS 130. Referring to Figure 5, for example, OS 130 can have a path management table 131. In addition to general functions such as user jobs and I/O functions, OS 130 has, as its main processing units, a peripheral device initialization unit including a path information acquisition unit 132, a path selection unit 133, an initialization I/O issuance unit 134, and an I/O result check unit 135, and a path management table update unit including a validity flag change unit 136, an initialization flag change unit 137, a priority change unit 138, an access time change unit 139, and a notification unit 140. In this embodiment, the I/O function of OS 130 can have a function of calling the priority change unit 138 and the access time change unit 139 when I/O is issued, etc.

Path management table 131 is a table for managing path initialization processing. Updates to path management table 131 are reflected in path management table 112. In addition, the configuration of path management table 112 is reflected in path management table 131. Path management table 131 may be the same as path management table 112.

The path information acquisition unit 132 acquires path information including the path ID by referring to the path management table 131.

Here, the path information acquisition unit 132 acquires path information for paths for which the system initializer 110 did not perform initialization processing. Similarly to the path information acquisition unit 114, the path information acquisition unit 132 acquires path information for paths for which the system initializer 110 did not perform initialization processing using different criteria depending on whether a priority has been set. In other words, the path information acquisition unit 114 acquires path information selected using different criteria depending on whether a priority has not yet been acquired, such as when the system initializer 110 is started for the first time, and whether a priority has been acquired, such as when the system initializer 110 is started for the second or subsequent times.

For example, if the priority has not been acquired, the path information acquisition unit 132 acquires path information for paths for which the system initializer 110 has not performed initialization processing, in order from the top of the table, etc. As a result, the OS 130 sequentially initializes paths for which the system initializer 110 has not performed initialization processing.

Also, for example, when priority has been acquired, the path information acquisition unit 132 acquires path information in descending order of priority for paths on which the system initializer 110 has not performed initialization processing. As a result, the OS 130 performs initialization in descending order of priority for paths on which the system initializer 110 has not performed initialization processing.

For example, as described above, the path information acquisition unit 132 sequentially acquires path information for paths for which the system initializer 110 did not perform initialization processing.

When the priority is acquired, the device 200 whose priority is equal to or higher than the priority threshold becomes the device 200 to be initialized by the system initializer 110. Therefore, the system initializer 110 does not perform initialization processing on the device 200 whose priority is lower than the priority threshold. As a result, when an I/O is issued by the I/O function of the OS 130, initialization may not have been performed on all paths corresponding to the device 200 to which the I/O is issued. In this way, when an I/O is issued to a device 200 whose corresponding paths have not been initialized, the path information acquisition unit 132 can acquire any path information corresponding to the device 200. This allows the OS 130 to perform initialization processing on the path indicated by the path information acquired by the path information acquisition unit 132. In addition, after the initialization processing by the OS 130, an I/O can be issued by the I/O function.

The path selection unit 133, the initialization I/O issuing unit 134, and the I/O result checking unit 135 perform the same processing as the path selection unit 115, the initialization I/O issuing unit 116, and the I/O result checking unit 117. For example, the path selection unit 133 selects a path for which to issue an initialization I/O based on the path information acquired by the path information acquisition unit 132. The initialization I/O issuing unit 134 issues an initialization I/O to the path selected by the path selection unit 133 after the path information acquisition unit 132 acquires the path information. The I/O result checking unit 135 then checks whether the initialization was successful or not based on the result of the initialization I/O issued by the initialization I/O issuing unit 134.

The validity flag change unit 136 and the initialization flag change unit 137 perform the same processing as the table update unit 118. For example, if the I/O result check unit 135 determines that the initialization was successful, the validity flag change unit 136 changes the validity flag in the path management table 131 corresponding to the path on which the initialization process was performed to on. Also, the initialization flag change unit 137 changes the initialization flag corresponding to the path on which the initialization process was performed to on. On the other hand, if the I/O result check unit 135 determines that the initialization was unsuccessful, the validity flag change unit 136 changes the validity flag in the path management table 131 corresponding to the path on which the initialization process was performed to off. Also, the initialization flag change unit 137 changes the initialization flag corresponding to the path on which the initialization process was performed to on.

The priority change unit 138 changes the priority items contained in the path management table 131. For example, the priority change unit 138 adds a priority value depending on at least one of the access time when the I/O is issued and the user. The time and user settings and the value to be added may be set arbitrarily.

As an example, the priority change unit 138 adds 1 to the priority value if an I/O is issued before the OS 130 is started. Also, the priority change unit 138 adds 0 to the priority value if an I/O is issued after the OS 130 is started. In this way, the priority change unit 138 can add a different value depending on whether the light-emitting object of the I/O is before or after the OS 130 is started. Note that the priority change unit 138 may be configured to add the priority value in stages depending on the time that has elapsed since the system initializer 110 was started when the I/O was issued.

As another example, the priority change unit 138 adds a value according to the user of the I/O. For example, the priority change unit 138 changes the priority value according to the user, for example, if the user of the I/O is a subsystem, the priority value is increased by 2, if the user is a user, the priority value is increased by 1, if there is no user, the priority value is increased by 0, etc.

For example, as described above, the priority change unit 138 adds a priority value depending on the access time when the I/O is issued and the user.

The access time change unit 139 changes the access time item contained in the path management table 131. For example, when an I/O is issued by an I/O function of the OS 130, the access time change unit 139 writes the time when the I/O was issued (for example, the time elapsed since the system initializer 110 started operating) in the access time item.

The notification unit 140 can notify other functional units of the OS 130 that changes have been made to the path management table 131 by the validity flag change unit 136, the initialization flag change unit 137, the priority change unit 138, the access time change unit 139, etc. In other words, when a change has been made to the path management table 131, the notification unit 140 notifies other processing units, external devices, etc. that a change has been made to the path management table 131.

The above is an example of the configuration of the host device 100. Next, an example of the operation when performing path initialization processing will be described with reference to Figs. 6 to 9. First, an example of the operation when the system initializer 110 performs initialization processing will be described with reference to Figs. 6 and 7.

Figure 6 shows an example of the operation of the system initializer 110 when the priority has not been acquired. Referring to Figure 6, the system initializer 110 starts (step S110).

The device management table copy unit 113 generates the path management table 112 by copying the device management table 111 (step S102).

The path information acquisition unit 114 acquires path information including a path ID and the like by referring to the path management table 112. For example, the path information acquisition unit 114 acquires any path information corresponding to any device 200, such as the top of the table. The path selection unit 115 selects a path for which to issue an initialization I/O based on the path information acquired by the path information acquisition unit 114. The initialization I/O issuing unit 116 then issues an initialization I/O to the path selected by the path selection unit 115 after the path information acquisition unit 114 acquires the path information. In this manner, the path initialization process is performed (step S103).

The I/O result check unit 117 checks whether the initialization was successful or not, based on the result of the initialization I/O issued by the initialization I/O issuing unit 116 (step S104). If the initialization is unsuccessful (step S104, No), the table update unit 118 changes the valid flag corresponding to the path for which the initialization process was performed in the path management table 112 to OFF, and changes the initialization flag to ON. In addition, the path information acquisition unit 114 acquires any other path information corresponding to the same device 200 as the path for which the initialization process was performed (step S105), and returns to the processing of step S103.

On the other hand, if the initialization is successful (step S104, Yes), the table update unit 118 changes the valid flag and initialization flag in the path management table 112 corresponding to the path that has been initialized to on (step S106).

When the initialization process for initializing one of the multiple paths connected to all devices 200 to be initialized is completed (Yes in step S107), the system initializer 110 ends the process. Thereafter, the OS start process 120 starts the OS 130. On the other hand, if there are devices 200 remaining to be initialized (No in step S107), the path information acquisition unit 114 acquires any path information corresponding to the next device 200 (step S108) and returns to the process of step S103.

The above is an example of the operation of the system initializer 110 when the priority has not been acquired. Next, an example of the operation of the system initializer 110 when the priority has been acquired will be described with reference to FIG. 7.

Referring to Figure 7, the system initializer 110 is started (step S210).

The device management table copy unit 113 checks whether the device management table 111 has been updated (step S202). If the device management table 111 has been updated (step S202, Yes), the device management table copy unit 113 reflects the updated information in the path management table 112 (step S203).

The table update unit 118 turns off the valid flag and the initialization flag in the path management table 112 (step S204).

The path information acquisition unit 114 acquires path information including a path ID and the like based on the priority by referring to the path management table 112. For example, the path information acquisition unit 114 acquires any path information corresponding to the device 200 with the highest priority among the devices 200 whose priority is equal to or higher than the priority threshold (step S205). The path selection unit 115 selects a path for which to issue an initialization I/O based on the path information acquired by the path information acquisition unit 114. The initialization I/O issuing unit 116 then issues an initialization I/O to the path selected by the path selection unit 115 after the path information acquisition unit 114 acquires the path information. In this manner, the path initialization process is performed (step S206).

The I/O result check unit 117 checks whether the initialization was successful or not, based on the result of the initialization I/O issued by the initialization I/O issuing unit 116 (step S207). If the initialization is unsuccessful (step S207, No), the table update unit 118 changes the valid flag corresponding to the path for which the initialization process was performed in the path management table 112 to OFF, and changes the initialization flag to ON. In addition, the path information acquisition unit 114 acquires any other path information corresponding to the same device 200 as the path for which the initialization process was performed (step S208), and returns to the process of step S206.

On the other hand, if the initialization is successful (step S207, Yes), the table update unit 118 changes the valid flag and the initialization flag in the path management table 112 corresponding to the path that has been initialized to on (step S209).

When the initialization process for initializing one of the multiple paths connected to all devices 200 to be initialized is completed (Yes in step S210), the system initializer 110 ends the process. Thereafter, the OS start process 120 starts the OS 130. On the other hand, if there are devices 200 remaining to be initialized (No in step S210), the path information acquisition unit 114 acquires any path information corresponding to the device 200 with the next highest priority (step S211), and returns to the process of step S205.

The above is an example of the operation of the system initializer 110 when the priority has been acquired. Next, an example of the operation of the OS 130 when the priority has not been acquired will be described with reference to FIG. 8.

The path information acquisition unit 132 acquires path information including a path ID and the like by referring to the path management table 131. For example, the path information acquisition unit 132 acquires path information from the top of the table for paths that the system initializer 110 did not perform initialization processing on (step S301).

The path selection unit 133 selects a path to issue an initialization I/O to, based on the path information acquired by the path information acquisition unit 132. The initialization I/O issuance unit 134 then issues an initialization I/O to the path selected by the path selection unit 133 after the path information acquisition unit 132 acquires the path information. In this manner, the path initialization process is performed (step S302).

The I/O result check unit 135 checks whether the initialization was successful or not, depending on the result of the initialization I/O issued by the initialization I/O issuing unit 134 (step S303). If the initialization is unsuccessful (step S303, No), the valid flag change unit 136 changes the valid flag to off, and the initialization flag change unit 137 changes the initialization flag to on (step S304). On the other hand, if the initialization is successful (step S303, Yes), the valid flag change unit 136 changes the valid flag to on, and the initialization flag change unit 137 changes the initialization flag to on (step S305).

When the initialization process has been performed on all paths (step S306, Yes), OS 130 ends the path initialization process. On the other hand, when there are paths remaining that have not been initialized (step S306, No), path information acquisition unit 132 acquires the next path information (step S307) and returns to the process of step S302.

The above is an example of the operation of OS 130 when priority has not been acquired. Next, an example of the operation of OS 130 when priority has been acquired will be described with reference to FIG. 9.

The path information acquisition unit 132 acquires path information including a path ID and the like by referring to the path management table 131. For example, the path information acquisition unit 132 acquires path information in descending order of priority for paths that the system initializer 110 has not performed initialization processing on (step S401).

The path selection unit 133 selects a path to issue an initialization I/O based on the path information acquired by the path information acquisition unit 132. The initialization I/O issuance unit 134 then issues an initialization I/O to the path selected by the path selection unit 133 after the path information acquisition unit 132 acquires the path information. In this manner, the path initialization process is performed in order of priority (step S402).

The I/O result check unit 135 checks whether the initialization was successful or not, depending on the result of the initialization I/O issued by the initialization I/O issuing unit 134 (step S403). If the initialization is unsuccessful (step S403, No), the valid flag change unit 136 changes the valid flag to off, and the initialization flag change unit 137 changes the initialization flag to on (step S404). On the other hand, if the initialization is successful (step S403, Yes), the valid flag change unit 136 changes the valid flag to on, and the initialization flag change unit 137 changes the initialization flag to on (step S405).

When the initialization process has been performed on all paths (step S406, Yes), OS 130 ends the path initialization process. On the other hand, when there are paths remaining that have not been initialized (step S406, No), path information acquisition unit 132 acquires the next path information (step S407) and returns to the process of step S402.

The above is an example of the operation of OS130 when priority has been acquired.

Thus, the host device 100 has a system initializer 110 that has a path information acquisition unit 114, a path selection unit 115, and an initialization I/O issuing unit 116. With this configuration, the system initializer 110 can operate to initialize only some of the multiple paths that connect to the device 200 to be initialized. As a result, it becomes possible to start the OS 130 in a state where only some of the multiple paths that connect to the device 200 to be initialized have been initialized. This makes it possible to start the OS 130 quickly while ensuring reliability.

In addition, OS 130 has a configuration for initializing paths that were not initialized by system initializer 110. With this configuration, it becomes possible to initialize the remaining paths after OS 130 starts up.

In this embodiment, a case has been described in which processing based on priority is performed even when the device management table 111 has been updated. However, for example, if the device management table copy unit 113 determines that the device management table 111 has been updated, the processing using priority may not be performed. In other words, if the device management table 111 has been updated, the system initializer 110 may initialize all devices 200 connected to the host device 100. The system initializer 110 may determine the devices 200 to be initialized based on criteria other than those exemplified above, such as initializing devices 200 whose priorities are equal to or greater than a priority threshold and newly added devices 200.

Second Embodiment
Next, a second embodiment of the present disclosure will be described with reference to Fig. 10 and Fig. 11. In the second embodiment, an information processing device 300 connected to a plurality of devices via a plurality of paths will be described.

Fig. 10 shows an example of the hardware configuration of the information processing device 300. Referring to Fig. 10, the information processing device 300 has, as an example, the following hardware configuration.
・CPU (Central Processing Unit) 301 (arithmetic unit)
ROM (Read Only Memory) 302 (storage device)
RAM (Random Access Memory) 303 (storage device)
Program group 304 loaded into RAM 303
A storage device 305 for storing the programs 304
A drive device 306 that reads and writes data from and to a recording medium 310 outside the information processing device.
A communication interface 307 that connects to a communication network 311 outside the information processing device
Input/output interface 308 for inputting and outputting data
A bus 309 that connects each component

In addition, the information processing device 300 can realize the function of the initialization unit 321 shown in FIG. 11 by having the CPU 301 acquire and execute the group of programs 304. The group of programs 304 is stored in advance in the storage device 305 or ROM 302, for example, and is loaded and executed by the CPU 301 into the RAM 303, etc., as necessary. The group of programs 304 may be supplied to the CPU 301 via the communication network 311, or may be stored in advance on the recording medium 310, and the drive device 306 may read out the programs and supply them to the CPU 301.

Note that FIG. 10 shows an example of the hardware configuration of the information processing device 300. The hardware configuration of the information processing device 300 is not limited to the above-described case. For example, the information processing device 300 may be configured with only a part of the above-described configuration, such as not having the drive device 306.

The initialization unit 321 initializes only some of the paths among the multiple paths that connect to the device to be initialized.

In this way, the information processing device 300 has an initialization unit 321. With this configuration, the initialization unit 321 can initialize only some of the multiple paths that connect to the device to be initialized. As a result, it becomes possible to start the OS quickly while ensuring reliability.

The information processing device 300 described above can be realized by incorporating a specific program into the information processing device 300. Specifically, the program, which is another aspect of the present invention, is a program for realizing an initialization unit in the information processing device 300, which is connected to each of a plurality of devices via a plurality of paths, that initializes only some of the paths that connect to the device to be initialized.

The initialization method realized by the information processing device 300 described above is a method in which, when the information processing device 300, which is connected to each of multiple devices via multiple paths, successfully initializes one of the multiple paths connecting to the device, it does not initialize the other paths connecting to the device, but initializes the paths connecting to the other devices.

Even if the invention is a program (or recording medium) or an initialization method having the above-mentioned configuration, it has the same action and effect as the above-mentioned information processing device 300, and therefore can achieve the above-mentioned object of the present invention.

<Additional Notes>
A part or all of the above-described embodiment can be described as follows: An information processing device and the like according to the present invention will be outlined below. However, the present invention is not limited to the following configuration.

(Appendix 1)
An information processing device connected to a plurality of devices via a plurality of paths,
An information processing device comprising an initialization unit that initializes only some of a plurality of paths connected to a device to be initialized.
(Appendix 2)
2. The information processing device according to claim 1,
When initialization of one path among a plurality of paths connected to the device is successful, the initialization unit does not initialize the other paths connected to the device.
(Appendix 3)
10. The information processing device according to claim 1,
When initialization of one of a plurality of paths connecting to a device is successful, the initialization unit does not initialize other paths connecting to the device, but initializes paths connecting to other devices.
(Appendix 4)
An information processing device according to any one of claims 1 to 3,
The initialization unit selects a device to be initialized according to a priority level obtained in advance.
(Appendix 5)
The information processing device according to claim 4,
The information processing device, wherein the priority is acquired based on at least one of a time when the device is accessed and a user at the time of accessing the device.
(Appendix 6)
The information processing device according to claim 4 or 5,
The initialization unit selects a device to be initialized based on different criteria depending on whether the priority has been acquired.
(Appendix 7)
An information processing device according to any one of Supplementary Note 1 to Supplementary Note 6,
The information processing device, wherein the initialization unit manages the initialization by using a path management table generated based on a device management table for managing devices.
(Appendix 8)
An information processing device according to any one of claims 1 to 7,
An information processing apparatus comprising an OS that initializes paths that have not been initialized by the initialization unit.
(Appendix 9)
An information processing device connected to each of a plurality of devices via a plurality of paths,
An initialization method in which, when initialization of one path among a plurality of paths connecting to a device is successful, initialization is not performed on the other paths connecting to the device, but initialization is performed on paths connecting to other devices.
(Appendix 10)
An information processing device connected to each of a plurality of devices via a plurality of paths,
A program for implementing an initialization unit that initializes only some of a plurality of paths connected to a device to be initialized.

The programs described in the above embodiments and appendices may be stored in a storage device or a computer-readable recording medium. For example, the recording medium may be a portable medium such as a flexible disk, an optical disk, a magneto-optical disk, or a semiconductor memory.

The present invention has been described above with reference to the above-mentioned embodiments, but the present invention is not limited to the above-mentioned embodiments. Various modifications that can be understood by a person skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

100 Host device 110 System initializer 111 Device management table 112 Path management table 113 Device management table copy unit 114 Path information acquisition unit 115 Path selection unit 116 Initialization I/O issuing unit 117 I/O result check unit 118 Table update unit 120 OS start process 130 OS
131 Path management table 132 Path information acquisition unit 133 Path selection unit 134 Initialization I/O issuing unit 135 I/O result check unit 136 Validity flag change unit 137 Initialization flag change unit 138 Priority change unit 139 Access time change unit 140 Notification unit 200 Device 300 Information processing device 301 CPU
302 ROM
303 RAM
304 Program group 305 Storage device 306 Drive device 307 Communication interface 308 Input/output interface 309 Bus 310 Recording medium 311 Communication network 321 Initialization unit

Claims (9)

An information processing device connected to a plurality of devices via a plurality of paths,
An initialization unit is provided for initializing only a part of a plurality of paths connected to a device to be initialized,
When initialization of one of a plurality of paths connecting to a device is successful, the initialization unit does not initialize other paths connecting to the device, but initializes paths connecting to other devices. 2. The information processing device according to claim 1,
The initialization unit selects a device to be initialized according to a priority level obtained in advance. 3. The information processing device according to claim 2,
The information processing device, wherein the priority is acquired based on at least one of a time when the device is accessed and a user at the time of accessing the device. 3. The information processing device according to claim 2 ,
The initialization unit selects a device to be initialized based on different criteria depending on whether the priority has been acquired. The information processing device according to any one of claims 1 to 4,
The information processing device, wherein the initialization unit manages the initialization by using a path management table generated based on a device management table for managing devices. The information processing device according to any one of claims 1 to 5,
An information processing apparatus comprising an OS that initializes paths that have not been initialized by the initialization unit. An information processing device connected to each of a plurality of devices via a plurality of paths,
Initialize only some of the paths among the multiple paths connected to the device to be initialized,
In the initialization , if initialization of one of a plurality of paths connecting to the device is successful, the initialization method does not initialize the other paths connecting to the device, but initializes paths connecting to other devices. An information processing device connected to each of a plurality of devices via a plurality of paths,
An initialization unit is provided for initializing only a portion of a plurality of paths connected to a device to be initialized;
The initialization unit is a program that, when initialization of one of a plurality of paths connecting to a device is successful, initializes paths connecting to other devices without initializing other paths connecting to the device. An information processing device connected to a plurality of devices via a plurality of paths,
An initialization unit is provided for initializing only a part of a plurality of paths connected to a device to be initialized,
An information processing apparatus comprising an OS that initializes paths that have not been initialized by the initialization unit.

Images