Device driver file loading method, device driver file sharing system, device, medium, and product

Abstract

The present application relates to the technical field of computers, and discloses a device driver file loading method, a device driver file sharing system, a device, a medium, and a product. The device driver file sharing system comprises a plurality of hosts, a compute express link switch, a compute express link memory expansion card, and a plurality of compute express link memories. The device driver file loading method comprises: when a target host performs a device driver file loading operation, the target host determining, from among a plurality of compute express link memories, a target compute express link memory storing a device driver file; reading the device driver file from the target compute express link memory by means of a compute express link switch and a compute express link memory expansion card; and loading the device driver file, and notifying a following host to perform the device driver file loading operation. The present application achieves sharing of the device driver file among the plurality of hosts and improves the utilization rate of storage resources.

Description

Device driver file loading method, sharing system, and device, medium and product

[0001] Cross-reference to Related Applications

[0002] The present application claims priority to the Chinese patent application No. 202411002872.1, filed on July 25, 2024, and entitled "Device driver file loading method, sharing system, and device, medium and product", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0003] The present application relates to the technical field of computer, more particularly, to a device driver file loading method, sharing system, and device, medium and product. BACKGROUND

[0004] A device driver file is a file used to initialize a device so that the device enters a normal working mode, which is generally loaded by a BIOS (Basic Input / Output System) in the startup phase or by an operating system in the system startup phase. With the development of server technology, multi-host systems are increasingly widely used. In a multi-host system, each host needs to initialize the devices on the local host, which requires loading the device driver files. Currently, these driver files are mostly stored in binary form on the storage medium of the local host. Since the device driver files are universal, if each host stores a copy, it will cause a waste of storage resources, especially when the number of hosts is large, the waste of storage resources is more.

[0005] Therefore, how to realize the sharing of device driver files among multiple hosts is a technical problem to be solved by those skilled in the art. SUMMARY

[0006] The present application aims to provide a device driver file loading method, sharing system, and device, medium and product, which realizes the sharing of device driver files among multiple hosts.

[0007] To achieve the above-mentioned purpose, the present application provides a device driver file loading method applied to a device driver file sharing system. The device driver file sharing system includes a plurality of hosts, a computing fast link switch connected with the plurality of hosts, a computing fast link memory expansion card connected with the computing fast link switch, and a plurality of computing fast link memories connected with the computing fast link memory expansion card.

[0008] The method comprises:

[0009] When the target host executes the device driver loading operation, the target host determines a target compute rapid link memory storing the device driver among the plurality of compute rapid link memories;

[0010] The target host reads the device driver from the target compute rapid link memory through the compute rapid link switch and the compute rapid link memory expansion card;

[0011] The target host loads the device driver and informs a next host of the target host to execute the device driver loading operation.

[0012] In some embodiments of the present application, before the target host determines the target compute rapid link memory storing the device driver among the plurality of compute rapid link memories, the target host further comprises:

[0013] determining whether there is a device requiring loading of the device driver in the target host;

[0014] If there is, the target host executes the step of determining the target compute rapid link memory storing the device driver among the plurality of compute rapid link memories.

[0015] In some embodiments of the present application, after the target host determines whether there is a device requiring loading of the device driver in the target host, the target host further comprises:

[0016] If there is not, the target host executes the step of informing a next host of the target host to execute the device driver loading operation.

[0017] In some embodiments of the present application, before the target host executes the device driver loading operation, the target host further comprises:

[0018] The target host obtains the device driver and stores the device driver in the target compute rapid link memory.

[0019] In some embodiments of the present application, the target host obtains the device driver, comprising:

[0020] The target host obtains the device driver from a basic input output system flash memory of the target host.

[0021] In some embodiments of the present application, the target host obtains the device driver, comprising:

[0022] The target host obtains the device driver from a flash memory of the compute rapid link memory expansion card.

[0023] In some embodiments of the present application, after the target host loads the device driver, the target host further comprises:

[0024] determining whether the device driver is loaded successfully;

[0025] If the loading is successful, the other host device driver file is informed as an available file.

[0026] In some embodiments of the present application, after determining whether the device driver file is loaded successfully, the method further comprises:

[0027] If the loading fails, the step of loading the device driver file is re-entered.

[0028] In some embodiments of the present application, the target host determines a target compute express link memory in which the device driver file is stored from a plurality of compute express link memories, comprising:

[0029] The target host determines a target compute express link memory in which the available device driver file is stored from a plurality of compute express link memories.

[0030] In some embodiments of the present application, the target host reads the device driver file from the target compute express link memory through the compute express link switch and the compute express link memory expansion card, comprising:

[0031] The target host reads the device driver file from the target compute express link memory through the compute express link switch and the compute express link memory expansion card by using a basic input / output system of the target host.

[0032] To achieve the above object, the present application provides a device driver file sharing system, comprising a plurality of hosts, a compute express link switch connected with the plurality of hosts, a compute express link memory expansion card connected with the compute express link switch, and a plurality of compute express link memories connected with the compute express link memory expansion card.

[0033] The host is configured to determine a target compute express link memory in which a device driver file is stored from a plurality of compute express link memories, read the device driver file from the target compute express link memory through the compute express link switch and the compute express link memory expansion card, and load the device driver file.

[0034] In some embodiments of the present application, the host is further configured to obtain the device driver file and store the device driver file in the target compute express link memory.

[0035] To achieve the above object, the present application provides an electronic device, comprising:

[0036] A memory configured to store a computer program.

[0037] A processor configured to execute the computer program to implement the steps of the device driver file loading method.

[0038] To achieve the above object, the present application provides a non-volatile readable storage medium, the non-volatile readable storage medium stores a computer program, and the computer program is executed by a processor to implement the steps of the device driver file loading method.

[0039] To achieve the above object, the present application provides a computer program product, the computer program product comprises a computer program, and the computer program is executed by a processor to implement the steps of the device driver file loading method.

[0040] It can be known from the above scheme that the device driver file loading method provided by the present application is applied to a device driver file sharing system, the device driver file sharing system comprises a plurality of hosts, a compute express link switch connected with the plurality of hosts, a compute express link memory expansion card connected with the compute express link switch, and a plurality of compute express link memories connected with the compute express link memory expansion card; the method comprises the following steps: when a target host performs a device driver file loading operation, the target host determines a target compute express link memory storing the device driver file from the plurality of compute express link memories; the target host reads the device driver file from the target compute express link memory through the compute express link switch and the compute express link memory expansion card; the target host loads the device driver file and notifies a next host of the target host to perform the device driver file loading operation.

[0041] The device driver file loading method provided by the present application stores the device driver file into the compute express link (CXL) memory, changes the storage position of the device driver file in the multi-host system in the related art, and further changes the access mode of the device driver file in the multi-host. After the device driver file is stored into the target compute express link memory, all the hosts can access the target compute express link memory and use the device driver file, thereby realizing the sharing of the device driver file among the multi-hosts and improving the utilization rate of the storage resource. The present application also discloses a device driver file sharing system, an electronic device, a non-volatile readable storage medium and a computer program product, which can also achieve the above technical effects.

[0042] It should be understood that the above general description and the following detailed description are only exemplary and cannot limit the present application. BRIEF DESCRIPTION OF DRAWINGS

[0043] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the accompanying drawings needed to be used in the embodiments or prior art description will be briefly introduced as follows. Obviously, the accompanying drawings in the following description only represent some embodiments of the present application, and all other drawings obtained by those of ordinary skill in the art based on the accompanying drawings without any creative effort fall within the protection scope of the present application. In addition, in the embodiments of the present application, "first", "second", etc. are used to distinguish similar objects, and do not necessarily indicate a specific order or sequence.

[0044] FIG. 1 is a system for sharing memory and I / O services between nodes in the related art;

[0045] FIG. 2 is a structural diagram of a device driver file sharing system according to an exemplary embodiment;

[0046] FIG. 3 is a flowchart of a device driver file loading method according to an exemplary embodiment;

[0047] FIG. 4 is a flowchart of another device driver file loading method according to an exemplary embodiment;

[0048] FIG. 5 is a structural diagram of a device driver file loading apparatus according to an exemplary embodiment;

[0049] FIG. 6 is a structural diagram of an electronic device according to an exemplary embodiment. DETAILED DESCRIPTION

[0050] The technical solutions in the embodiments of the present application will be described clearly and completely in combination with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without any creative effort fall within the protection scope of the present application. In addition, in the embodiments of the present application, "first", "second", etc. are used to distinguish similar objects, and do not necessarily indicate a specific order or sequence.

[0051] Device driver file is a file used to initialize a device so that the device enters normal working mode, which is generally loaded by BIOS in the boot stage or by the operating system in the system boot stage. With the development of server technology, multi-host systems are increasingly widely used. In a multi-host system, each host needs to initialize the device on the local host, which requires loading the device driver file. Currently, these driver files are mostly stored in binary form on the storage medium of the local host. Since the device driver files are universal, if each host stores a copy, it will cause waste of storage resources, especially when the number of hosts is large, the waste of storage resources is more.

[0052] Referring to FIG. 1, which is a system for sharing memory and I / O services between nodes in the related art, a shared memory controller is used to service load and store operations received from multiple independent nodes via a data link to provide access to shared memory resources. Each of the multiple independent nodes is allowed to access a respective portion of the shared memory resources. Interconnect protocol data and memory access protocol data are sent over the data link, and a translation between the interconnect protocol data and the memory access protocol data can be defined and identified.

[0053] The above solution is to share resources among multiple hosts through a newly defined shared memory controller and a shared memory link protocol running thereon. The transmission of data needs to follow this specific hardware architecture and protocol data format, and this hardware architecture and link protocol are not widely used. It is difficult to promote the way of sharing resources among multiple hosts through a shared memory controller.

[0054] Therefore, in this application, the device driver file is stored in the compute express link memory, which changes the storage location of the device driver file in the related art under the multi-host system, and further changes the way of accessing the device driver file by the multi-host. After the device driver file is stored in the target compute express link memory, all hosts can access the target compute express link memory and use the device driver file, which realizes the sharing of the device driver file among multiple hosts and improves the utilization of storage resources.

[0055] The embodiment provides a device driver file sharing system, as shown in FIG. 2, which includes a plurality of hosts, a compute express link switch connected with the plurality of hosts, a compute express link memory expansion card connected with the compute express link switch, and a plurality of compute express link memories connected with the compute express link memory expansion card.

[0056] The host is configured to determine a target CXL memory in which the device driver file is stored from a plurality of CXL memories, access the target CXL memory through the CXL switch and the CXL memory expansion card, and load the device driver file.

[0057] In the embodiment, the device driver file sharing system includes a plurality of hosts, i.e., host 1 to host N, each of which has its own BIOS Flash, BMC (Baseboard Management Controller), and BMC Flash. The CXL switch can set a connection relationship between an upstream host and a downstream CXL memory and control a certain host to access a certain CXL memory (CXL memory). The CXL memory pool includes a CXL memory expansion card (CXL memory expansion card) and CXL memories. The CXL memory expansion card includes a CXL memory expansion controller and a CXL Flash. Each host can access the CXL memory expansion card and the underlying CXL memories through the CXL switch.

[0058] In a specific implementation, the host determines a target CXL memory in which the device driver file is stored from a plurality of CXL memories, accesses the target CXL memory through the CXL switch and the CXL memory expansion card, acquires the device driver file stored in the target CXL memory, and loads the device driver file.

[0059] In some embodiments of the present application, the host is further configured to acquire the device driver file and store the device driver file in the target CXL memory. In a specific implementation, one of the plurality of hosts acquires the device driver file from an external storage medium by the BIOS and stores the device driver file in the target CXL memory for access by all hosts in the device driver file sharing system. The external storage medium includes, but is not limited to, the BIOS Flash of the host and the CXL Flash in the CXL memory expansion card.

[0060] It can be seen that the embodiment stores the device driver file into the computing express link memory, changes the storage location of the device driver file in the multi-host system in the prior art, and further changes the way of accessing the device driver file in the multi-host. After the device driver file is stored into the target computing express link memory, all the hosts can access the target computing express link memory and use the device driver file, so that the device driver file is shared among the multi-hosts, and the utilization of the storage resource is improved. In addition, when the device driver file needs to be updated, the device driver file in the BIOS Flash or the CXL memory expansion card Flash of one host is replaced with a new file, so that the new device driver file is stored into the device driver file area of the target CXL memory during the booting of the host. Therefore, the other hosts obtain the updated device driver file, and the updating efficiency of the device driver file in the multi-host is improved.

[0061] The embodiment of the application discloses a device driver file loading method, and realizes the sharing of the device driver file among the multi-hosts.

[0062] Referring to FIG. 3, a flowchart of a device driver file loading method according to an exemplary embodiment is shown, as shown in FIG. 3, which includes the following steps.

[0063] S101: When a target host performs a device driver file loading operation, the target host determines a target computing express link memory for storing the device driver file in a plurality of computing express link memories.

[0064] The embodiment is applied to the device driver file sharing system, and the embodiment describes the process of loading the device driver file by one host in the device driver file sharing system, that is, the target host.

[0065] In the specific implementation, when the target host performs the device driver file loading operation, the target host determines the target computing express link memory for storing the device driver file in the plurality of computing express link memories.

[0066] In some embodiments of the application, before the target host determines the target computing express link memory for storing the device driver file in the plurality of computing express link memories, the method further includes: judging whether there is a device that needs to load the device driver file in the target host; if yes, performing the step of determining the target computing express link memory for storing the device driver file in the plurality of computing express link memories; and if no, performing the step of notifying the next host of the target host to perform the device driver file loading operation.

[0067] In a specific implementation, during a booting stage of the target host, a BIOS of the target host receives a setting of a user, i.e., a requirement of loading of the device driver file. When the target host performs the loading operation of the device driver file, it is determined according to the setting of the user whether the target host needs to load the device driver file, i.e., whether there is a device requiring loading of the device driver file. If the device driver file needs to be loaded, i.e., if there is a device requiring loading of the device driver file, a target compute express link memory in which the device driver file is stored is determined in the plurality of compute express link memories. If the device driver file does not need to be loaded, i.e., if there is no device requiring loading of the device driver file, a next host of the target host is directly notified to perform the loading operation of the device driver file.

[0068] S102: The target host reads the device driver file from the target compute express link memory through the compute express link switch and the compute express link memory expansion card.

[0069] In a specific implementation, the target host reads the device driver file from the target compute express link memory through a basic input output system of the target host.

[0070] S103: The target host loads the device driver file and notifies a next host of the target host to perform the loading operation of the device driver file.

[0071] In a specific implementation, after the target host reads the device driver file from the target compute express link memory, the target host notifies the next host to perform the loading operation of the device driver file after the device driver file is loaded successfully.

[0072] The device driver file loading method provided by the embodiment of the present application stores the device driver file into the compute express link memory, changes the storage position of the device driver file in the multi-host system in the related art, and further changes the access manner of the device driver file in the multi-host system. After the device driver file is stored into the target compute express link memory, all the hosts can access the target compute express link memory and use the device driver file, so that the device driver file is shared among the hosts, and the utilization rate of the storage resource is improved.

[0073] The embodiment of the present application discloses a device driver file loading method, and further describes and optimizes the technical solution compared with the previous embodiment. Specifically,

[0074] Referring to FIG. 4, a flowchart of another device driver file loading method according to an example embodiment is shown, as shown in FIG. 4, including:

[0075] S201: A target host obtains a device driver file and stores the device driver file into a target compute express link memory.

[0076] In the embodiment, the target host obtains the device driver file from the external storage medium by BIOS, stores the device driver file in the target compute quick link memory, so as to be accessed by all hosts in the device driver file sharing system.

[0077] It should be noted that the specific external storage medium is not limited here. As a feasible implementation manner, the target host obtains the device driver file from the basic input output system flash memory of itself. As another feasible implementation manner, the target host obtains the device driver file from the flash memory of the compute quick link memory expansion card. Of course, the target host can also obtain the device driver file from other external storage media.

[0078] S202: When the target host performs the device driver file loading operation, the target compute quick link memory storing the device driver file is determined in the plurality of compute quick link memories;

[0079] S203: The device driver file is read from the target compute quick link memory by the compute quick link switch and the compute quick link memory expansion card;

[0080] S204: The device driver file is loaded, and the next host is informed to perform the device driver file loading operation.

[0081] In some embodiments of the application, after the target host loads the device driver file, the method further includes: judging whether the device driver file is loaded successfully; if loaded successfully, informing other hosts that the device driver file is an available file; and if loaded unsuccessfully, re-entering the step of loading the device driver file.

[0082] In the specific implementation, after the target host loads the device driver file, whether the loading is successful is judged. If the loading is successful, other hosts are informed that the device driver file stored in the target compute quick link memory is an available file. When the other hosts perform the device driver file loading operation, the target compute quick link memory storing the available device driver file is determined in the plurality of compute quick link memories, and then the available device driver file is obtained therefrom for loading. That is, the target host determines the target compute quick link memory storing the device driver file in the plurality of compute quick link memories, including: the target host determines the target compute quick link memory storing the available device driver file in the plurality of compute quick link memories.

[0083] If the loading fails, reloading is performed for multiple attempts. If the loading still fails after multiple attempts, the device driver file may be damaged in the process of storing the device driver file in the target computing express link memory of the target host, in which case the target host re-executes the step of storing the device driver file in the target computing express link memory, or the device driver file obtained by the target host has a problem, in which case other hosts can be selected to perform the steps of obtaining the device driver file and storing the device driver file in the target computing express link memory.

[0084] It can be seen that the device driver file is stored in the computing express link memory in the embodiment, the storage location of the device driver file in the multi-host system is changed in the related art, and thus the way in which the multi-host accesses the device driver file is changed. After the device driver file is stored in the target computing express link memory, all the hosts can access the target computing express link memory and use the device driver file, the device driver file is shared among the multi-hosts, and the utilization rate of the storage resource is improved. In addition, when the device driver file needs to be updated, the device driver file in the BIOS Flash or the CXL memory expansion card Flash of the target host is replaced with a new file, so that the new device driver file is stored in the device driver file region of the target CXL memory during the startup of the target host. Therefore, the other hosts obtain the updated device driver file, and the updating efficiency of the device driver file of the multi-host is improved.

[0085] An application embodiment provided in the application is introduced below, including the following steps.

[0086] Step 1: The first host reads the device driver file from the external storage medium by the BIOS during the startup stage, and places the file on the specific CXL memory in the CXL memory pool. The external storage medium can be the BIOS Flash of the first host, or the Flash on the CXL memory expansion card.

[0087] Step 2: The nth host receives the user setting by the BIOS during the startup stage, and obtains the requirement for the device driver file. If the device needs to be loaded with the driver, step 3 is entered, otherwise step 6 is entered.

[0088] Step 3: The nth host reads the specific CXL memory in the CXL memory pool by the BIOS during the startup stage, obtains the device driver file, and performs device initialization. If the initialization is successful, step 4 is entered, otherwise step 5 is entered.

[0089] Step 4: The nth host completes the initialization of the device, and notifies other hosts that the device driver file is available.

[0090] Step 5: The nth host reloads the device driver file and informs other hosts that the device driver file is available.

[0091] Step 6: n = n + 1, re-enter step 2, that is, the n+1th host starts the device driver loading process.

[0092] The following describes a device driver file loading apparatus provided by an embodiment of the present application. The device driver file loading apparatus described below can be referred to the device driver file loading method described above.

[0093] Referring to FIG. 5, a structural diagram of a device driver file loading apparatus according to an exemplary embodiment is shown, as shown in FIG. 5, comprising:

[0094] The determining module 100 is configured to determine a target compute express link memory storing the device driver file in the plurality of compute express link memories when the target host performs the device driver file loading operation.

[0095] The reading module 200 is configured to read the device driver file from the target compute express link memory through the compute express link switch and the compute express link memory expansion card.

[0096] The loading module 300 is configured to load the device driver file and inform the next host of the target host to perform the device driver file loading operation.

[0097] The device driver file loading apparatus provided by the embodiment of the present application stores the device driver file into the compute express link memory, changes the storage location of the device driver file in the multi-host system in the related art, and further changes the way of accessing the device driver file by the multi-host. After the device driver file is stored into the target compute express link memory, all hosts can access the target compute express link memory and use the device driver file, which realizes the sharing of the device driver file among the multi-hosts and improves the utilization of the storage resource.

[0098] On the basis of the above embodiment, in some embodiments of the present application, further comprising:

[0099] The first judging module is configured to judge whether there is a device requiring loading of the device driver file in the target host. If yes, the working process of the determining module 100 is started. If no, the next host of the target host is informed to perform the device driver file loading operation.

[0100] On the basis of the above embodiment, in some embodiments of the present application, further comprising:

[0101] The storage module is configured to acquire the device driver file and store the device driver file in the target compute express link memory.

[0102] In some embodiments of the present application, on the basis of the above-mentioned embodiments, the storage module is specifically configured to obtain the device driver file from the basic input output system flash memory of the target host.

[0103] In some embodiments of the present application, on the basis of the above-mentioned embodiments, the storage module is specifically configured to obtain the device driver file from the flash memory of the compute express link memory expansion card.

[0104] In some embodiments of the present application, on the basis of the above-mentioned embodiments, the method further comprises:

[0105] The second determining module is configured to determine whether the device driver file is loaded successfully; if the device driver file is loaded successfully, the other host is informed that the device driver file is an available file; and if the device driver file fails to be loaded, the working process of the loading module 300 is restarted.

[0106] In some embodiments of the present application, on the basis of the above-mentioned embodiments, the determining module 100 is specifically configured to determine, in the plurality of compute express link memories, a target compute express link memory in which the device driver file is stored.

[0107] In some embodiments of the present application, on the basis of the above-mentioned embodiments, the determining module 100 is specifically configured to read, by the target host, the device driver file from the target compute express link memory through the basic input output system of the target host, the compute express link switch and the compute express link memory expansion card.

[0108] As to the apparatus in the above-mentioned embodiments, the specific manners in which various modules perform operations have been described in detail in the embodiments of the method, and will not be described here in detail.

[0109] Based on the hardware implementation of the above-mentioned program modules, and in order to implement the method of the embodiments of the present application, the embodiments of the present application further provide an electronic device. FIG. 6 is a structural diagram of an electronic device according to an exemplary embodiment. As shown in FIG. 6, the electronic device comprises:

[0110] The communication interface 1 is capable of information interaction with other devices such as network devices and the like;

[0111] The processor 2 is connected with the communication interface 1 to realize information interaction with other devices, and is used to run a computer program to execute the device driver file loading method provided in one or more of the above technical solutions. The computer program is stored on the memory 3.

[0112] Of course, in a practical implementation, the various components of the electronic device are coupled together by a bus system 4. As will be appreciated, the bus system 4 is used to enable the components to communicate with each other. The bus system 4 includes, among other things, a data bus, a power bus, a control bus, and a state signal bus. However, for the sake of clarity, the various buses are collectively indicated as the bus system 4 in Figure 6.

[0113] The memory 3 in the embodiments of the present application is used to store various types of data to support the operation of the electronic device. Examples of such data include any computer programs used in the operation of the electronic device.

[0114] It can be understood that the memory 3 can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a ferromagnetic random access memory (FRAM), a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM). The magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM) used as an external cache. By way of example but not limitation, many forms of RAM can be used, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), sync link dynamic random access memory (SLDRAM), and direct rambus random access memory (DRRAM).The memory 3 described in the embodiments of the present application is intended to include, but not limited to, these and any other suitable types of memory.

[0115] The method disclosed in the embodiments of the present application can be applied to or implemented by the processor 2. The processor 2 can be an integrated circuit chip with processing capability. In the implementation process, the steps of the above method can be completed by the integrated logic circuit or the instruction of the software form in the processor 2. The processor 2 described above can be a general processor, a DSP, or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The processor 2 can implement or execute the disclosed methods, steps and logic block diagrams in the embodiments of the present application. The general processor can be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiments of the present application, the hardware code processor can be directly embodied to execute the completion, or the combination of hardware and software modules in the code processor can be executed to complete. The software module can be located in the storage medium, which is located in the memory 3. The processor 2 reads the program in the memory 3 and combines the hardware to complete the steps of the above method.

[0116] The processor 2 executes the program to implement the corresponding flow in each method of the embodiments of the present application. For brevity, it will not be repeated here.

[0117] In the exemplary embodiments, the embodiments of the present application also provide a non-volatile readable storage medium, which stores a computer program. The computer program can be executed by the processor 2 to complete the above method steps.

[0118] In the exemplary embodiments, the embodiments of the present application also provide a computer program product, which includes a computer program. The computer program is executed by the processor 2 to complete the above method steps.

[0119] Those skilled in the art can understand that all or part of the steps of the above method embodiments can be completed by the related hardware of the computer program instruction. The above computer program can be stored in a non-volatile readable storage medium. When the computer program is executed, the execution includes the steps of the above method embodiments. Or, when the above integrated units of the present application are realized in the form of software function modules and sold or used as independent products, they can also be stored in a non-volatile readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application can be embodied in the form of software products, which are stored in a non-volatile readable storage medium, including a plurality of instructions for making an electronic device (which can be a personal computer, a server, a network device, etc.) execute all or part of the embodiments of the present application.

[0120] The above merely provides the specific implementation of the present application, but the protection scope of the present application is not limited to this. Any person skilled in the art can easily think of the changes or replacements within the technical range disclosed by the present application, and all the changes and replacements should be covered within the protection scope of the present application.

Claims

1. A device driver file loading method, characterized by, The application is applied to a device driver file sharing system, which comprises a plurality of hosts, a computing fast link switch connected with the plurality of hosts, a computing fast link memory expansion card connected with the computing fast link switch, and a plurality of computing fast link memories connected with the computing fast link memory expansion card. The method comprises: When a target host performs a device driver file loading operation, the target host determines a target computing fast link memory storing a device driver file in the plurality of computing fast link memories; The target host reads the device driver file from the target computing fast link memory through the computing fast link switch and the computing fast link memory expansion card; The target host loads the device driver file and informs a next host of the target host to perform a device driver file loading operation.

2. The device driver file loading method of claim 1, wherein, Before the target host determines the target computing fast link memory storing the device driver file in the plurality of computing fast link memories, the method further comprises: determining whether there is a device requiring a device driver file loading operation in the target host; if yes, performing the step of determining the target computing fast link memory storing the device driver file in the plurality of computing fast link memories.

3. The device driver file loading method of claim 2, wherein, The step of determining whether there is a device requiring a device driver file loading operation in the target host comprises: the target host receiving a loading demand for the device driver file through a basic input / output system of the target host; determining whether there is a device requiring a device driver file loading operation in the target host according to the loading demand for the device driver file.

4. The device driver file loading method of claim 2, wherein, After determining whether there is a device requiring a device driver file loading operation in the target host, the method further comprises: if no, performing the step of informing the next host of the target host to perform a device driver file loading operation.

5. The device driver file loading method of claim 1, wherein, Before the target host performs the device driver file loading operation, the method further comprises: the target host obtaining a device driver file and storing the device driver file in the target computing fast link memory.

6. The device driver file loading method of claim 5, wherein, The step of the target host obtaining the device driver file comprises: the target host obtaining the device driver file from a basic input / output system flash memory of the target host.

7. The device driver file loading method of claim 5, wherein, The step of the target host obtaining the device driver file comprises: the target host obtaining the device driver file from a flash memory of the computing fast link memory expansion card.

8. The device driver file loading method of claim 1, wherein After the target host loads the device driver file, the method further comprises: determining whether the device driver file is loaded successfully; if yes, informing other hosts that the device driver file is an available file.

9. The device driver file loading method of claim 8, wherein, After determining whether the device driver file is loaded successfully, the method further comprises: if no, re-entering the step of loading the device driver file.

10. The device driver file loading method of claim 8, wherein, The step of the target host determining the target computing fast link memory storing the device driver file in the plurality of computing fast link memories comprises: the target host determining the target computing fast link memory storing an available device driver file in the plurality of computing fast link memories.

11. The device driver file loading method of claim 1, wherein, The target host reads a device driver file from the target compute rapid link memory through the compute rapid link switch and the compute rapid link memory expansion card, comprising: The target host reads a device driver file from the target compute rapid link memory through the compute rapid link switch and the compute rapid link memory expansion card by using its basic input output system.

12. The device driver file loading method of claim 1, wherein, The device driver file is configured as a file for initializing a device to make the device enter a normal working mode.

13. A device driver file sharing system, characterized by, The system comprises a plurality of hosts, a compute rapid link switch connected with the plurality of hosts, a compute rapid link memory expansion card connected with the compute rapid link switch, and a plurality of compute rapid link memories connected with the compute rapid link memory expansion card. The host is configured to determine a target compute rapid link memory storing a device driver file from the plurality of compute rapid link memories, read a device driver file from the target compute rapid link memory through the compute rapid link switch and the compute rapid link memory expansion card, and load the device driver file.

14. The device driver file sharing system of claim 13, wherein, The host accesses the compute rapid link memory expansion card and the compute rapid link memory through the compute rapid link switch.

15. The device driver file sharing system of claim 13, wherein, The host is further configured to obtain a device driver file and store the device driver file in the target compute rapid link memory.

16. The device driver file sharing system of claim 15, wherein, The obtaining of the device driver file and the storing of the device driver file in the target compute rapid link memory comprise: The obtaining of the device driver file and the storing of the device driver file in the target compute rapid link memory comprise:

17. The device driver file sharing system of claim 16, wherein, The obtaining of the device driver file and the storing of the device driver file in the target compute rapid link memory comprise:

18. An electronic device, comprising: The external storage medium at least comprises a basic input output system flash memory of the host itself and a flash memory in the compute rapid link memory expansion card. Comprise: A memory configured to store a computer program; 19. A non-volatile readable storage medium, characterized by A processor configured to implement the steps of the device driver file loading method according to any one of claims 1 to 12 when executing the computer program.

20. A computer program product, characterised in that, The non-volatile readable storage medium stores a computer program, and the computer program is executed to implement the steps of the device driver file loading method according to any one of claims 1 to 12. The computer program product comprises a computer program, and the computer program is executed to implement the steps of the device driver file loading method according to any one of claims 1 to 12.

Images