CN118054998B

CN118054998B - Driver for kernel network driver and driver upgrading method

Info

Publication number: CN118054998B
Application number: CN202410444142.0A
Authority: CN
Inventors: 陈森法
Original assignee: Zhuhai Xingyun Zhilian Technology Co Ltd
Current assignee: Zhuhai Xingyun Zhilian Technology Co Ltd
Priority date: 2024-04-15
Filing date: 2024-04-15
Publication date: 2024-06-18
Anticipated expiration: 2044-04-15
Also published as: CN118054998A

Abstract

The application relates to the technical field of computers and provides a driver for kernel network driving and a driving upgrading method. The driver includes: the parent driver is used for managing the network interfaces and the child devices and also used for providing a parent network device operation interface and a parent Ethernet operation interface; a first sub-driver and a second sub-driver, the first sub-driver binding the sub-devices and providing a sub-network device operation interface and a sub-ethernet operation interface. The parent driver causes the parent network device operational interface and the parent ethernet operational interface to be respectively shorted to the corresponding child network device operational interface and child ethernet operational interface when the first child driver has been loaded, and the parent driver takes over the network interface through the parent network device operational interface and the parent ethernet operational interface when the first child driver has been unloaded. Therefore, the reconstruction of the network interface and the sub-equipment is avoided, and the driving hot upgrading is realized.

Description

Driver for kernel network driver and driver upgrading method

Technical Field

The present application relates to the field of computer technologies, and in particular, to a driver for kernel network driving and a driving upgrade method.

Background

With the development of technologies such as cloud computing and data centers, hardware such as a data processing unit (Data Processing Unit, DPU) and a Network interface card (Network INTERFACE CARD, NIC) has been widely deployed. The hardware manufacturer may release a matching kernel network driver to provide network capabilities, and may also support custom customization and error correction, thus upgrading the kernel network driver as may be required. In the prior art, upgrading a kernel network driver requires unloading the driver, deleting a kernel network interface provided by the driver, installing the driver, creating the kernel network interface, and performing network address allocation again to recover network functions. Because the upgrade time of the kernel network driver may be long, the cloud manufacturer needs to find available server resources in advance for service migration, but the service migration operation is complex and error-prone, and needs to occupy a large amount of additional server resources.

Therefore, the application provides a driver for kernel network driving and a driving upgrading method for solving the technical problems in the prior art.

Disclosure of Invention

In a first aspect, the present application provides a driver for a kernel network driver. The driver includes: a parent driver, wherein the parent driver is used for managing a plurality of network interfaces and a plurality of child devices corresponding to the network interfaces one by one, the parent driver is also used for providing a parent network device operation interface and a parent ethernet operation interface corresponding to the network interfaces one by one, the network interfaces comprise a first network interface and a second network interface, the child devices comprise a first child device and a second child device, the first network interface corresponds to the first child device, and the second network interface corresponds to the second child device; a first child driver binding the first child device and providing a child network device operation interface and a child ethernet operation interface corresponding to the first network interface, and a second child driver binding the second child device and providing a child network device operation interface and a child ethernet operation interface corresponding to the second network interface, wherein when the first child driver has been loaded, the parent driver causes a parent network device operation interface and a parent ethernet operation interface corresponding to the first network interface to be respectively shorted to a child network device operation interface and a child ethernet operation interface corresponding to the first network interface, and when the first child driver has been unloaded, the parent driver takes over the first network interface through a parent network device operation interface and a parent ethernet operation interface corresponding to the first network interface.

According to the application, the reconstruction of the network interfaces and the sub-devices is avoided, the abnormal interface states are avoided, the number of the devices is saved, the loss of the kernel network interfaces is saved, the kernel network driver is updated according to the custom-made needs and the service development needs, the realization of the hot upgrade of the driver is facilitated, the network is not interrupted during the upgrade of the driver, the service migration is not needed, the redundant server resources are not needed, and the number of the network interfaces is conveniently expanded and the service is conveniently expanded.

In a possible implementation manner of the first aspect of the present application, when the second child driver has been loaded, the parent driver causes the parent network device operation interface and the parent ethernet operation interface corresponding to the second network interface to be respectively shorted to the child network device operation interface and the child ethernet operation interface corresponding to the second network interface, and when the second child driver has been unloaded, the parent driver takes over the second network interface through the parent network device operation interface and the parent ethernet operation interface corresponding to the second network interface.

In a possible implementation manner of the first aspect of the present application, the first sub-driver is unloaded and reloaded to complete the upgrade of the first sub-driver, and the second sub-driver is unloaded and reloaded to complete the upgrade of the second sub-driver.

In a possible implementation manner of the first aspect of the present application, when the first sub-driver has been loaded, link traffic passing through the first network interface is processed by the first sub-device driven by the first sub-driver, and when the second sub-driver has been loaded, link traffic passing through the second network interface is processed by the second sub-device driven by the second sub-driver.

In a possible implementation manner of the first aspect of the present application, the first network interface and the second network interface form a same network aggregation interface, when the first child driver has been offloaded, the parent driver closes a link through the first network interface and switches link traffic through the first network interface to a link through the second network interface, so that link traffic through the first network interface is handled by the second child device driven by the second child driver, and when the second child driver has been offloaded, the parent driver closes a link through the second network interface and switches link traffic through the second network interface to a link through the first network interface, so that link traffic through the second network interface is handled by the first child device driven by the first child driver.

In a possible implementation manner of the first aspect of the present application, when the first child driver has been unloaded and loaded again, the first child driver matches the first child device and issues an upgrade end notification of the first child driver, the parent driver opens a link through the first network interface and resumes processing of the first child device driven by the first child driver through the first network interface, and when the second child driver has been unloaded and loaded again, the second child driver matches the second child device and issues an upgrade end notification of the second child driver, the parent driver opens a link through the second network interface and resumes processing of the second child device driven by the second child driver through the second network interface.

In a possible implementation manner of the first aspect of the present application, the upgrade end notification of the first sub-driver and the upgrade end notification of the second sub-driver are received by the user through a user kernel access interface or a character device kernel access interface.

In a possible implementation manner of the first aspect of the present application, the first sub-driver and the second sub-driver are alternately upgraded, and the first sub-driver and the second sub-driver are not unloaded simultaneously, and the first network interface is maintained during the first sub-driver upgrade, and the second network interface is maintained during the second sub-driver upgrade.

In a possible implementation manner of the first aspect of the present application, the first child driver is connected to a child device bound to the first child driver in the plurality of child devices through a virtual bus, the second child driver is connected to a child device bound to the second child driver in the plurality of child devices through the virtual bus, and the parent driver is connected to a physical bus.

In a possible implementation manner of the first aspect of the present application, the plurality of network interfaces further includes a third network interface, the plurality of child devices further includes a third child device, the third network interface corresponds to the third child device, the first child driver binds the third child device and provides a child network device operation interface and a child ethernet operation interface corresponding to the third network interface, when the first child driver has been loaded, the parent driver causes a parent network device operation interface and a parent ethernet operation interface corresponding to the third network interface to be respectively shorted to a child network device operation interface and a child ethernet operation interface corresponding to the third network interface, and when the first child driver has been unloaded, the parent driver takes over the third network interface through a parent network device operation interface and a parent ethernet operation interface corresponding to the third network interface, and when the first child driver has been loaded, link traffic passing through the third network interface is processed through the third child driver of the third child driver.

In a possible implementation manner of the first aspect of the present application, the first network interface, the second network interface and the third network interface form the same network aggregation interface, when the first child driver has been offloaded, the parent driver closes a link through the third network interface and switches link traffic through the third network interface to a link through the second network interface, so that link traffic through the third network interface is handled by the second child device driven by the second child driver, and when the first child driver has been offloaded and loaded again, the first child driver matches the third child device, the parent driver opens a link through the third network interface and resumes link traffic through the third network interface to be handled by the third child device driven by the first child driver, and the third network interface is maintained during the upgrade of the first child driver.

In a possible implementation manner of the first aspect of the present application, the plurality of network interfaces further includes a third network interface and a fourth network interface, the plurality of child devices further includes a third child device and a fourth child device, the third network interface corresponds to the third child device, the fourth network interface corresponds to the fourth child device, the first child driver binds the third child device and provides a child network device operation interface and a child ethernet operation interface corresponding to the third network interface, the second child driver binds the fourth child device and provides a child network device operation interface and a child ethernet operation interface corresponding to the fourth network interface, when the first child driver has been loaded, the parent driver causes a parent network device operation interface and a parent ethernet operation interface corresponding to the third network interface to be respectively shorted to the child network device operation interface and the child ethernet operation interface corresponding to the third network interface, and when the first child driver has been unloaded, the parent device operation interface and the fourth device operation interface are respectively, and the parent driver takes over the parent operation interface and the fourth operation interface through the parent device operation interface and the parent device operation interface when the first child driver has been unloaded.

In a possible implementation manner of the first aspect of the present application, when the first sub-driver has been loaded, link traffic passing through the third network interface is processed by the third sub-device driven by the first sub-driver, and when the second sub-driver has been loaded, link traffic passing through the fourth network interface is processed by the fourth sub-device driven by the second sub-driver.

In a possible implementation manner of the first aspect of the present application, the first network interface and the second network interface form a first network aggregation interface, when the first child driver has been offloaded, the parent driver closes a link through the first network interface and switches link traffic through the first network interface to a link through the second network interface, so that link traffic through the first network interface is handled by the second child device driven by the second child driver, and when the second child driver has been offloaded, the parent driver closes a link through the second network interface and switches link traffic through the second network interface to a link through the first network interface, so that link traffic through the second network interface is handled by the first child device driven by the first child driver.

In a possible implementation manner of the first aspect of the present application, the third network interface and the fourth network interface form a second network aggregation interface, when the first child driver has been offloaded, the parent driver closes a link through the third network interface and switches link traffic through the third network interface to a link through the fourth network interface, so that link traffic through the third network interface is handled by the fourth child device driven by the second child driver, and when the second child driver has been offloaded, the parent driver closes a link through the fourth network interface and switches link traffic through the fourth network interface to a link through the third network interface, so that link traffic through the fourth network interface is handled by the third child device driven by the first child driver.

In a possible implementation manner of the first aspect of the present application, the first sub-driver and the second sub-driver are alternately upgraded, and the first sub-driver and the second sub-driver are not unloaded simultaneously, and the first network interface and the third network interface are maintained during the first sub-driver upgrade, and the second network interface and the fourth network interface are maintained during the second sub-driver upgrade.

In a possible implementation manner of the first aspect of the present application, the plurality of network interfaces includes an even number of network interfaces, the plurality of sub-devices includes an even number of sub-devices, the first sub-driver binds the odd number of sub-devices in the plurality of sub-devices and provides a sub-network device operation interface and a sub-ethernet operation interface corresponding to a network interface corresponding to the sub-device bound by the first sub-driver, and the second sub-driver binds the even number of sub-devices in the plurality of sub-devices and provides a sub-network device operation interface and a sub-ethernet operation interface corresponding to a network interface corresponding to the sub-device bound by the second sub-driver.

In a possible implementation manner of the first aspect of the present application, each two network interfaces in the plurality of network interfaces form a same network aggregation interface, and member ports in the same network aggregation interface correspond to the first sub-driver and the second sub-driver respectively.

In a possible implementation manner of the first aspect of the present application, the traffic passing through the same network aggregation interface selects a member port in the same network aggregation interface through hashing.

In a second aspect, the embodiment of the application further provides a driving upgrading method for the kernel network driving. The driver includes a parent driver, a first child driver, and a second child driver. The drive upgrading method comprises the following steps: loading the first sub-driver after unloading to finish upgrading of the first sub-driver; and loading the second sub-driver after unloading to finish the upgrading of the second sub-driver. Wherein the first sub-drive and the second sub-drive are alternately upgraded, and the first sub-drive and the second sub-drive are not unloaded simultaneously. The parent driver is used for managing a plurality of network interfaces and a plurality of pieces of child equipment corresponding to the network interfaces one by one, the parent driver is also used for providing a parent network equipment operation interface and a parent Ethernet operation interface corresponding to the network interfaces one by one, the network interfaces comprise a first network interface and a second network interface, the child equipment comprises a first child equipment and a second child equipment, the first network interface corresponds to the first child equipment, and the second network interface corresponds to the second child equipment. The first sub-driver binds the first sub-device and provides a sub-network device operation interface and a sub-ethernet operation interface corresponding to the first network interface, and the second sub-driver binds the second sub-device and provides a sub-network device operation interface and a sub-ethernet operation interface corresponding to the second network interface. Wherein when the first child driver has been loaded, the parent driver causes a parent network device operation interface and a parent ethernet operation interface corresponding to the first network interface to be respectively shorted to a child network device operation interface and a child ethernet operation interface corresponding to the first network interface, and when the first child driver has been unloaded, the parent driver takes over the first network interface through the parent network device operation interface and the parent ethernet operation interface corresponding to the first network interface.

In a third aspect, embodiments of the present application further provide a computer device, the computer device including a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing a method according to any one of the implementations of any one of the above aspects when the computer program is executed.

In a fourth aspect, embodiments of the present application also provide a computer-readable storage medium storing computer instructions that, when run on a computer device, cause the computer device to perform a method according to any one of the implementations of any one of the above aspects.

In a fifth aspect, embodiments of the present application also provide a computer program product comprising instructions stored on a computer-readable storage medium, which when run on a computer device, cause the computer device to perform a method according to any one of the implementations of any one of the above aspects.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a schematic diagram of a driver for kernel network driving according to a first embodiment of the present application;

FIG. 2 is a schematic diagram of a driver for kernel network driver according to a second embodiment of the present application;

FIG. 3 is a schematic diagram of a driver for kernel network driver according to a third embodiment of the present application;

fig. 4 is a schematic flow chart of a method for upgrading a kernel network driver according to an embodiment of the present application;

Fig. 5 is a schematic structural diagram of a computing device according to an embodiment of the present application.

Detailed Description

Embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

It should be understood that in the description of the application, "at least one" means one or more than one, and "a plurality" means two or more than two. In addition, the words "first," "second," and the like, unless otherwise indicated, are used solely for the purposes of description and are not to be construed as indicating or implying a relative importance or order.

Fig. 1 is a schematic diagram of a driver for kernel network driving according to a first embodiment of the present application. As shown in fig. 1, the drivers for the kernel network driver include a parent driver 102, a first child driver 105, and a second child driver 106. The parent driver 102 is configured to manage a plurality of network interfaces (the network interface a110 and the network interface B120 are exemplarily shown in fig. 1) and a plurality of child devices (the child device a118 of the network interface a110 and the child device B128 of the network interface B120 are exemplarily shown in fig. 1) that are in one-to-one correspondence with the plurality of network interfaces. The parent driver 102 is further configured to provide a parent network device operation interface and a parent ethernet operation interface (a parent network device operation interface a111 and a parent ethernet operation interface a112 of the network interface a110, and a parent network device operation interface B121 and a parent ethernet operation interface B122 of the network interface B120 are exemplarily shown in fig. 1) that are in one-to-one correspondence with the plurality of network interfaces. The plurality of network interfaces includes a first network interface (network interface a 110) and a second network interface (network interface B120). The plurality of sub-devices includes a first sub-device (sub-device a118 of network interface a 110) and a second sub-device (sub-device B128 of network interface B120). The first network interface (network interface a 110) corresponds to the first sub-device (sub-device a118 of network interface a 110). The second network interface (network interface B120) corresponds to the second sub-device (sub-device B128 of network interface B120). Here, the parent network device operation interface a111 of the parent network device operation interface, such as the network interface a110, is used to implement a management basic function of the network interface, such as upstream and downstream traffic through the network interface, and the parent ethernet operation interface a112 of the parent network device operation interface, such as the network interface a110, is used to implement a management basic function of the ethernet port, such as messaging through the ethernet port. With continued reference to fig. 1, the first child driver 105 binds the first child device (child device a118 of network interface a 110) and provides a child network device operation interface and a child ethernet operation interface (child network device operation interface a113 and child ethernet operation interface a114 of network interface a 110) corresponding to the first network interface. The second sub-driver 106 binds the second sub-device (sub-device B128 of the network interface B120) and provides a sub-network device operation interface and a sub-ethernet operation interface (sub-network device operation interface B123 and sub-ethernet operation interface B124 of the network interface B120) corresponding to the second network interface. When the first child driver 105 has been loaded, the parent driver 102 causes the parent network device operation interface and the parent ethernet operation interface (the parent network device operation interface a111 and the parent ethernet operation interface a112 of the network interface a 110) corresponding to the first network interface to be respectively shorted to the child network device operation interface and the child ethernet operation interface (the child network device operation interface a113 and the child ethernet operation interface a114 of the network interface a 110) corresponding to the first network interface. And, when the first child driver 105 has been offloaded, the parent driver 102 takes over the first network interface (network interface a 110) through the parent network device operation interface and the parent ethernet operation interface (the parent network device operation interface a111 and the parent ethernet operation interface a112 of the network interface a 110) corresponding to the first network interface. Here, the sub-network device operation interface a113 of the sub-network device operation interface, such as the network interface a110, is used to implement a management basic function of the network interface, such as upstream and downstream traffic through the network interface, and the sub-ethernet operation interface a114 of the sub-ethernet operation interface, such as the network interface a110, is used to implement a management basic function of the ethernet interface, such as message transceiving through the ethernet interface.

A driver for a kernel network driver of the first embodiment shown in fig. 1 provides a two-tier driver structure including a parent driver 102 and also a first child driver 105 and a second child driver 106. The parent driver 102 provides a parent network device operation interface and a parent ethernet operation interface corresponding to the network interface one-to-one for each network interface, for example, the parent driver 102 provides a parent network device operation interface and a parent ethernet operation interface corresponding to a first network interface (network interface a 110) for the first network interface (the parent network device operation interface a111 and the parent ethernet operation interface a112 of the network interface a 110); the first sub-driver 105 binds the first sub-device (sub-device a118 of the network interface a 110) and provides a sub-network device operation interface and a sub-ethernet operation interface (sub-network device operation interface a113 and sub-ethernet operation interface a114 of the network interface a 110) corresponding to the first network interface. As such, when the first child driver 105 has been loaded, the parent driver 102 causes the parent network device operation interface and the parent ethernet operation interface (the parent network device operation interface a111 and the parent ethernet operation interface a112 of the network interface a 110) corresponding to the first network interface to be respectively shorted to the child network device operation interface and the child ethernet operation interface (the child network device operation interface a113 and the child ethernet operation interface a114 of the network interface a 110) corresponding to the first network interface, which means that traffic through the first network interface (the network interface a 110) is handled by the first child device (the child device a118 of the network interface a 110) driven by the first child driver 105. In other words, by directly shorting the parent network device operation interface a111 and the parent ethernet operation interface a112 of the network interface a110 to the child network device operation interface a113 and the child ethernet operation interface a114 of the corresponding network interface a110, this is equivalent to: the kernel network driver is provided by the parent driver 102, as seen for example from the physical bus 103, outside the driver, but essentially the first child device (child device a118 of the network interface a 110) to which the first child driver 105 is bound is driven by the first child driver 105 during the time that the first child driver 105 is loaded. When the first child drive 105 has been offloaded, for example, during an upgrade or error correction period of the first child drive 105, the parent drive 102 utilizes the parent network device operation interface and the parent ethernet operation interface (the parent network device operation interface a111 and the parent ethernet operation interface a112 of the network interface a 110) corresponding to the first network interface, so that the first network interface (the network interface a 110) can be taken over. This means that an upgrade or error correction of the first sub-driver 105 does not lead to a deletion of the first network interface (network interface a 110), i.e. the kernel network interface provided by the first sub-driver 105 does not need to be deleted, thus saving losses such as re-creation of the kernel network interface and re-network address allocation. Thus, when the first child drive 105 has been loaded, or when the first child drive 105 is unloaded, the parent drive 102 is responsible for maintaining and managing the first network interface (network interface a 110) and the first child device to which the first child drive 105 is bound (child device a118 of network interface a 110), which is equivalent to: the kernel network driver is provided by the parent driver 102, as seen from the outside of the driver, for example, from the physical bus 103, and the first child driver 105 provides kernel network driver functionality by directly shorting the parent network device operational interface a111 and the parent ethernet operational interface a112 of the network interface a110 to the child network device operational interface a113 and the child ethernet operational interface a114 of the corresponding network interface a110 only during the time that it has been loaded (which means that the first child driver 105 is not in a state where an upgrade, error correction or change configuration, etc. would cause it to be unloaded). Thus, on one hand, by using the two-layer drive structure including the parent drive 102 and the first child drive 105 and the second child drive 106, changes such as unloading, installation, updating, error correction, reconfiguration and the like of the first child drive 105 are realized, deletion of the child device bound by the first child drive 105 is not caused, and deletion of a network interface corresponding to the first child drive 105 is not caused, so that reconstruction of the network interface and the child device is avoided, abnormality of an interface state is avoided, loss of reallocating device numbers and re-creating a kernel network interface is also saved, and the kernel network drive is updated in favor of coping with customer customization needs and business development needs; on the other hand, the parent driver 102 is utilized to manage a plurality of network interfaces and a plurality of sub-devices corresponding to the plurality of network interfaces one by one, and the operation interface of the parent network device and the operation interface of the parent Ethernet provided by the parent driver 102 take over the first network interface when the first sub-driver 105 is upgraded, which means that the parent driver 102 can provide the state management basic functions of the network interfaces and the sub-devices, thereby being beneficial to realizing the hot upgrading of the driver, ensuring that the network is not interrupted and does not need service migration during the upgrading driving, and also not needing redundant server resources, and being convenient for expanding the number of the network interfaces and expanding the service. Further, the parent network device operation interface and the parent ethernet operation interface provided by the parent driver 102 are used to provide the network interface, the status management basic functions of the child devices, and to take over the first network interface when the first child driver 105 is unloaded, and when the first child driver 105 is loaded, the traffic through the first network interface (network interface a 110) is handled by the first child device (child device a118 of the network interface a 110) bound and driven by the first child driver 105. Thus, in contrast to migrating the entire traffic that would otherwise be provided by the first child drive 105 to additional server resources, a driver for a kernel network drive of the first embodiment shown in fig. 1 only needs to occupy limited resources so that the parent network device operational interface and the parent ethernet operational interface provided by the parent drive 102 take over the first network interface (network interface a 110) when the first child drive 105 is upgraded, which can ensure the stability of the network interface and the child device and the normal state of the entire interface by keeping the parent drive 102 un-upgraded, and keeping the network interface and the child device unchanged externally, the method is beneficial to realizing the upgrade of the kernel network drive under the condition of no external perception, thus reducing the overall complexity, reducing the error probability, simultaneously having the flexibility in the aspect of service expansion and the reliability in the aspect of service upgrade, and being beneficial to meeting the rapidly-increased, complex and changeable service demands of cloud computing, data centers and the like.

In summary, the driver for a kernel network driver according to the first embodiment shown in fig. 1 avoids rebuilding network interfaces and sub-devices, avoids abnormal interface states, and also saves the number of reallocated devices and the loss of recreating the kernel network interfaces, which is beneficial to upgrading the kernel network driver in response to customer customization needs and service development needs, and is beneficial to realizing hot upgrading of the driver, in which the network is not interrupted nor requires service migration during upgrading driving, and redundant server resources are not required, thereby facilitating the expansion of the number of network interfaces and the expansion of services.

In one possible implementation, when the second child driver 106 has been loaded, the parent driver 102 causes the parent network device operation interface and the parent ethernet operation interface (the parent network device operation interface B121 and the parent ethernet operation interface B122 of the network interface B120) corresponding to the second network interface to be respectively shorted to the child network device operation interface and the child ethernet operation interface (the child network device operation interface B123 and the child ethernet operation interface B124 of the network interface B120) corresponding to the second network interface, and when the second child driver 106 has been unloaded, the parent driver 102 takes over the second network interface (the network interface B120) through the parent network device operation interface and the parent ethernet operation interface (the parent network device operation interface B121 and the parent ethernet operation interface B122 of the network interface B120). Thus, on the one hand, by using the two-layer drive structure including the parent drive 102 and the first child drive 105 and the second child drive 106, changes such as unloading, installation, updating, error correction, reconfiguration and the like of the second child drive 106 are realized, deletion of the child device bound by the second child drive 106 is not caused, and deletion of the network interface corresponding to the second child drive 106 is not caused, so that reconstruction of the network interface and the child device is avoided, abnormality of the interface state is avoided, loss of reallocating device numbers and re-creating the kernel network interface is also saved, and the kernel network drive is updated in favor of coping with customer customization needs and business development needs; on the other hand, the parent driver 102 is utilized to manage a plurality of network interfaces and a plurality of sub-devices corresponding to the plurality of network interfaces one by one, and the operation interface of the parent network device and the operation interface of the parent Ethernet provided by the parent driver 102 take over the second network interface when the second sub-driver 106 is upgraded, which means that the parent driver can provide the state management basic functions of the network interfaces and the sub-devices, thereby being beneficial to realizing the hot upgrading of the driver, ensuring that the network is not interrupted and does not need service migration or redundant server resources during the upgrading driving, and being convenient for expanding the number of the network interfaces and expanding services.

In some embodiments, the first sub-driver 105 is unloaded and reloaded to complete the upgrade of the first sub-driver 105, and the second sub-driver 106 is unloaded and reloaded to complete the upgrade of the second sub-driver 106. Therefore, the method is favorable for realizing the hot upgrading of the drive, the network is not interrupted and the service migration is not required during the upgrading drive, and redundant server resources are not required, so that the method is convenient for expanding the number of network interfaces and expanding the service.

In some embodiments, link traffic through the first network interface (network interface a 110) is handled by the first sub-device (sub-device a118 of network interface a 110) driven by the first sub-driver 105 when the first sub-driver 105 has been loaded, and link traffic through the second network interface (network interface B120) is handled by the second sub-device (sub-device B128 of network interface B120) driven by the second sub-driver 106 when the second sub-driver 106 has been loaded. As such, when the first child driver 105 has been loaded, the parent driver 102 causes the parent network device operation interface and the parent ethernet operation interface (the parent network device operation interface a111 and the parent ethernet operation interface a112 of the network interface a 110) corresponding to the first network interface to be respectively shorted to the child network device operation interface and the child ethernet operation interface (the child network device operation interface a113 and the child ethernet operation interface a114 of the network interface a 110) corresponding to the first network interface, which means that traffic through the first network interface (the network interface a 110) is handled by the first child device (the child device a118 of the network interface a 110) driven by the first child driver 105. And, when the second child driver 106 has been loaded, the parent driver 102 causes the parent network device operation interface and the parent ethernet operation interface (the parent network device operation interface B121 and the parent ethernet operation interface B122 of the network interface B120) corresponding to the second network interface to be respectively shorted to the child network device operation interface and the child ethernet operation interface (the child network device operation interface B123 and the child ethernet operation interface B124 of the network interface B120) corresponding to the second network interface, which means that the traffic through the second network interface (the network interface B120) is handled by the second child device (the child device B128 of the network interface B120) driven by the second child driver 106. Therefore, only limited resources are occupied, so that the operation interface of the father network device and the operation interface of the father Ethernet provided by the father driver 102 can take over the corresponding network interfaces when the first child driver 105 or the second child driver 106 is upgraded, the stability of the network interfaces and the child devices and the normal state of the whole interfaces can be ensured by keeping the father driver 102 not to be upgraded, the network interfaces and the child devices are kept unchanged to the outside, the upgrading of the kernel network driver is finished under the condition that the outside is not perceived, the overall complexity is reduced, the error probability is reduced, and meanwhile, the flexibility in the aspect of service expansion and the reliability in the aspect of service upgrading are provided, and the requirements of rapidly-increased and complicated and changeable services such as cloud computing and data centers are met.

In some embodiments, the first network interface (network interface A110) and the second network interface (network interface B120) comprise the same network aggregation interface (network aggregation interface A190), when the first child drive 105 has been offloaded, the parent drive 102 closes the link through the first network interface (network interface A110) and switches link traffic through the first network interface (network interface A110) to the link through the second network interface (network interface B120), such that link traffic through the first network interface (network interface A110) is handled by a child device B128 of the second child device (network interface B120) driven by the second child drive 106, and, when the second child drive 106 has been offloaded, the parent drive 102 closes the link through the second network interface (network interface B120) and switches the link traffic through the second network interface (network interface B120) to the link through the first network interface (network interface a 110), so that the link traffic through the second network interface (network interface B120) is processed by the first child device (child device a118 of network interface a 110) driven by the first child drive 105. As such, with the link failover technique of the network aggregation interface, the first network interface (network interface a 110) may be taken over with the parent network device operational interface a111 and the parent ethernet operational interface a112 of the network interface a110 by alternately upgrading the first child drive 105 and the second child drive 106, for example, by offloading the first child drive 105, closing the link through the first network interface (network interface a 110) such that traffic is not being switched through the link of the first network interface (network interface a 110) but is being switched through to the link through the second network interface (network interface B120), and processing link traffic, e.g., messaging, by the second sub-device (sub-device B128 of network interface B120) driven by the second sub-driver 106, ensures that traffic is not interrupted during upgrades of the first sub-driver 105. Also, from the external, e.g. physical bus 103, during the up-scaling of the first sub-driver 105, the peer perceives a link failure, i.e. closes the link through said first network interface (network interface a 110) and switches to the link through said second network interface (network interface B120), so that after the upgrade of the first sub-driver 105 is completed, a match between the upgraded first sub-driver 105 and the first sub-device (sub-device a118 of network interface a 110) can be achieved, and then the provision of the core network driver by the sub-network device operation interface a113 and the sub-ethernet operation interface a114 of network interface a110 is resumed. Thus, the network interface and the sub-equipment are kept unchanged, the upgrading of the kernel network drive can be completed under the condition of no perception of the outside, the overall complexity is reduced, the error probability is reduced, the flexibility in the aspect of service expansion and the reliability in the aspect of service upgrading are simultaneously realized, and the requirements of rapidly-increased, complex and changeable services such as cloud computing, data centers and the like can be met.

In some embodiments, when the first child drive 105 has been unloaded and loaded, the first child drive 105 matches the first child device (child device a118 of network interface a 110) and issues an upgrade end notification for the first child drive 105, the parent drive 102 opens a link through the first network interface (network interface a 110) and resumes link traffic through the first network interface (network interface a 110) being processed by the first child device (child device a118 of network interface a 110) driven by the first child drive 105, and when the second child drive 106 has been unloaded and loaded, the second child drive 106 matches the second child device (child device B128 of network interface B120) and issues an upgrade end notification for the second child drive 106, the parent drive 102 opens a link through the second network interface (network interface B120) and resumes link traffic through the second network interface (network interface B120) being processed by the second child device (child device B128) of the second child drive 106. Thus, the network interface and the sub-equipment are kept unchanged, the upgrading of the kernel network drive can be completed under the condition of no perception of the outside, the overall complexity is reduced, the error probability is reduced, the flexibility in the aspect of service expansion and the reliability in the aspect of service upgrading are simultaneously realized, and the requirements of rapidly-increased, complex and changeable services such as cloud computing, data centers and the like can be met.

In some embodiments, the upgrade end notification of the first child drive 105 and the upgrade end notification of the second child drive 106 are received by the user through a user kernel access interface or a character device kernel access interface. Thus, the network interface and the sub-equipment are kept unchanged, the upgrading of the kernel network drive can be completed under the condition of no perception of the outside, the overall complexity is reduced, the error probability is reduced, the flexibility in the aspect of service expansion and the reliability in the aspect of service upgrading are simultaneously realized, and the requirements of rapidly-increased, complex and changeable services such as cloud computing, data centers and the like can be met.

In some embodiments, the first sub-drive 105 and the second sub-drive 106 are alternately upgraded, and the first sub-drive 105 and the second sub-drive 106 are not unloaded simultaneously, and the first network interface (network interface a 110) is maintained during the first sub-drive 105 upgrade, and the second network interface (network interface B120) is maintained during the second sub-drive 106 upgrade. In this way, by using the link failure switching technology of the network aggregation interface, the first child driver 105 and the second child driver 106 can be upgraded alternately, so that the stability of the network interface and the child device and the state of the whole interface can be ensured by keeping the parent driver 102 not to be upgraded, and the network interface and the child device are kept unchanged to the outside, thereby being beneficial to realizing the upgrade of the kernel network driver under the condition of no perception of the outside, reducing the overall complexity, reducing the error probability, simultaneously having the flexibility in the aspect of service expansion and the reliability in the aspect of service upgrade, and being beneficial to meeting the rapidly-increased and complicated and changeable service demands of cloud computing, data centers and the like.

In a possible implementation manner, the first child driver 105 is connected to a child device bound to the first child driver 105 in the plurality of child devices through a virtual bus 104, the second child driver 106 is connected to a child device bound to the second child driver in the plurality of child devices through the virtual bus 104, and the parent driver 102 is connected to the physical bus 103. Thus, the kernel network driver is provided by the father driver 102 from the external view of the physical bus 103, so that the kernel network driver is unchanged from the external view, the network interface and the child device are kept unchanged, the upgrading of the kernel network driver is finished under the condition of no external perception, the overall complexity is reduced, the error probability is reduced, the flexibility in the aspect of service expansion and the reliability in the aspect of service upgrading are provided, and the requirements of rapidly growing, complex and changeable services such as cloud computing and data centers are met.

Fig. 2 is a schematic diagram of a driver for kernel network driving according to a second embodiment of the present application. A driver for a kernel network driver according to the second embodiment shown in fig. 2 is the same as that of the first embodiment shown in fig. 1, and identical elements are denoted by identical reference numerals unless otherwise noted below, and the repeated elements may be described with reference to the above description about the specific embodiment shown in fig. 1, and will not be repeated here. Wherein, a driver for kernel network driving of the second embodiment shown in fig. 2 is different from the driver for kernel network driving of the first embodiment shown in fig. 1, the plurality of network interfaces further includes a third network interface (network interface C130), and the plurality of sub-devices further includes a third sub-device (sub-device C138 of network interface C130). The third network interface (network interface C130) corresponds to the third sub-device (sub-device C138 of network interface C130). The first sub-driver 105 binds the third sub-device (sub-device C138 of the network interface C130) and provides a sub-network device operation interface and a sub-ethernet operation interface (sub-network device operation interface C133 and sub-ethernet operation interface C134 of the network interface C130) corresponding to the third network interface. When the first child driver 105 has been loaded, the parent driver 102 causes the parent network device operation interface and the parent ethernet operation interface (the parent network device operation interface C131 and the parent ethernet operation interface C132 of the network interface C130) corresponding to the third network interface to be respectively shorted to the child network device operation interface and the child ethernet operation interface (the child network device operation interface C133 and the child ethernet operation interface C134 of the network interface C130) corresponding to the third network interface. And, when the first child driver 105 has been offloaded, the parent driver 102 takes over the third network interface (network interface C130) through the parent network device operation interface and the parent ethernet operation interface (the parent network device operation interface C131 and the parent ethernet operation interface C132 of the network interface C130) corresponding to the third network interface. And, when the first sub-driver 105 has been loaded, link traffic passing through the third network interface (network interface C130) is processed by the third sub-device (sub-device C138 of network interface C130) driven by the first sub-driver 105.

Referring to fig. 2, the parent driver 102 may provide a basic function of state management of network interfaces and child devices, which is advantageous for implementing a hot upgrade of the driver, where the network is not interrupted and no service migration is required during the upgrade of the driver, and no redundant server resources are required, so as to facilitate expanding the number of network interfaces and expanding the service, for example, the plurality of network interfaces further includes a third network interface (network interface C130) in fig. 2. Only limited resources are occupied, so that the operation interface of the parent network device and the operation interface of the parent Ethernet provided by the parent driver 102 take over the third network interface (network interface C130) when the first child driver 105 is upgraded, stability of the network interface and the child device and the state of the whole interface can be ensured by keeping the parent driver 102 not to be upgraded, the network interface and the child device are kept unchanged to the outside, and the upgrading of the kernel network driver is finished under the condition that the outside is not perceived, so that the overall complexity is reduced, the error probability is reduced, the flexibility in terms of service expansion and the reliability in terms of service upgrading are provided, and the requirements of rapidly-increased and complicated and changeable services such as cloud computing and data centers are met.

In one possible implementation, the first network interface (network interface a 110), the second network interface (network interface B120), and the third network interface (network interface C130) constitute the same network aggregation interface (network aggregation interface B191). When the first child drive 105 has been offloaded, the parent drive 102 closes the link through the third network interface (network interface C130) and switches the link traffic through the third network interface (network interface C130) to the link through the second network interface (network interface B120), such that the link traffic through the third network interface (network interface C130) is handled by the second child device (child device B128 of network interface B120) driven by the second child drive 106. And when the first child drive 105 has been unloaded and loaded again, the first child drive 105 matches the third child device (child device C138 of network interface C130), the parent drive 102 opens a link through the third network interface (network interface C130) and resumes link traffic through the third network interface (network interface C130) to be processed by the third child device (child device C138 of network interface C130) driven by the first child drive 105, and the third network interface (network interface C130) is maintained during the upgrade of the first child drive 105. In this way, by using the link failure switching technology of the network aggregation interface, the first sub-driver 105 and the second sub-driver 106 can be alternately upgraded to keep the network interface and the sub-device unchanged, which is favorable for realizing the upgrade of the kernel network driver under the condition of no external perception, thus reducing the overall complexity, reducing the error probability, simultaneously having the flexibility in terms of service expansion and the reliability in terms of service upgrade, and being favorable for meeting the rapidly-growing, complex and changeable service demands of cloud computing, data centers and the like.

Fig. 3 is a schematic diagram of a driver for kernel network driving according to a third embodiment of the present application. A driver for a kernel network driver of the third embodiment shown in fig. 3 is compared with a driver for a kernel network driver of the first embodiment shown in fig. 1, and the same elements are denoted by the same reference numerals unless otherwise noted below, and the repeated elements may be described with reference to the above description about the specific embodiment shown in fig. 1 and will not be repeated here. Wherein, a driver for kernel network driving of the third embodiment shown in fig. 3, unlike the driver shown in fig. 1, the plurality of network interfaces further includes a third network interface (network interface C130) and a fourth network interface (network interface D140), and the plurality of sub-devices further includes a third sub-device (sub-device C138 of network interface C130) and a fourth sub-device (sub-device D148 of network interface D140). The third network interface (network interface C130) corresponds to the third sub-device (sub-device C138 of network interface C130) and the fourth network interface (network interface D140) corresponds to the fourth sub-device (sub-device D148 of network interface D140). The first sub-driver 105 binds the third sub-device (sub-device C138 of the network interface C130) and provides a sub-network device operation interface and a sub-ethernet operation interface (sub-network device operation interface C133 and sub-ethernet operation interface C134 of the network interface C130) corresponding to the third network interface. The second sub-driver 106 binds the fourth sub-device (sub-device D148 of the network interface D140) and provides a sub-network device operation interface and a sub-ethernet operation interface (sub-network device operation interface D143 and sub-ethernet operation interface D144 of the network interface D140) corresponding to the fourth network interface.

With continued reference to fig. 3, when the first child driver 105 has been loaded, the parent driver 102 causes the parent network device operation interface and the parent ethernet operation interface (the parent network device operation interface C131 and the parent ethernet operation interface C132 of the network interface C130) corresponding to the third network interface to be respectively shorted to the child network device operation interface and the child ethernet operation interface (the child network device operation interface C133 and the child ethernet operation interface C134 of the network interface C130) corresponding to the third network interface. And, when the first child driver 105 has been offloaded, the parent driver 102 takes over the third network interface (network interface C130) through the parent network device operation interface and the parent ethernet operation interface (the parent network device operation interface C131 and the parent ethernet operation interface C132 of the network interface C130) corresponding to the third network interface. And, when the second child driver 106 has been loaded, the parent driver 102 causes the parent network device operation interface and the parent ethernet operation interface (the parent network device operation interface D141 and the parent ethernet operation interface D142 of the network interface D140) corresponding to the fourth network interface to be respectively shorted to the child network device operation interface and the child ethernet operation interface (the child network device operation interface D143 and the child ethernet operation interface D144 of the network interface D140) corresponding to the fourth network interface, and when the second child driver 106 has been unloaded, the parent driver 102 takes over the fourth network interface (the network interface D140) through the parent network device operation interface and the parent ethernet operation interface (the parent network device operation interface D141 and the parent ethernet operation interface D142 of the network interface D140). Thus, compared to the driver for kernel network driving of the first embodiment shown in fig. 1, the driver for kernel network driving of the third embodiment shown in fig. 3 adds two new network interfaces, namely, the third network interface (network interface C130) and the fourth network interface (network interface D140). And, by the first child driver 105 corresponding to the third network interface (network interface C130) and binding the corresponding third child device (child device C138 of network interface C130), and by the second child driver 106 corresponding to the fourth network interface (network interface D140) and binding the corresponding fourth child device (child device D148 of network interface D140), a two-tier driver structure including the parent driver 102 and also the first child driver 105 and the second child driver 106 can be fully utilized, increasing the number of supported network interfaces and increasing the number of corresponding child devices that need to be driven without increasing the number of child drivers. Moreover, the load of the kernel network drivers required to be supported by the first sub-driver 105 and the second sub-driver 106 can be dispersed, for example, the number of the sub-devices bound by the first sub-driver 105 and the second sub-driver 106 is kept consistent, which means that the link failure switching technology of the network aggregation interface is utilized, and the upgrade of the kernel network drivers corresponding to the whole network interface and the sub-devices can be realized by alternately upgrading the first sub-driver 105 and the second sub-driver 106, namely, operating two sub-drivers each time, on the premise of ensuring that the service is not interrupted, so that the whole complexity is reduced, the error probability is reduced, meanwhile, the system has flexibility in service expansion and reliability in service upgrading, and is beneficial to meeting the rapidly-growing, complex and changeable service demands of cloud computing, data centers and the like.

In one possible implementation, when the first sub-driver 105 has been loaded, link traffic through the third network interface (network interface C130) is processed by the third sub-device (sub-device C138 of network interface C130) driven by the first sub-driver 105, and when the second sub-driver 106 has been loaded, link traffic through the fourth network interface (network interface D140) is processed by the fourth sub-device (sub-device D148 of network interface D140) driven by the second sub-driver 106. Therefore, only limited resources are occupied, so that the operation interface of the father network device and the operation interface of the father Ethernet provided by the father driver 102 can take over the corresponding network interfaces when the first child driver 105 or the second child driver 106 is upgraded, the stability of the network interfaces and the child devices and the normal state of the whole interfaces can be ensured by keeping the father driver 102 not to be upgraded, the network interfaces and the child devices are kept unchanged to the outside, the upgrading of the kernel network driver is finished under the condition that the outside is not perceived, the overall complexity is reduced, the error probability is reduced, and meanwhile, the flexibility in the aspect of service expansion and the reliability in the aspect of service upgrading are provided, and the requirements of rapidly-increased and complicated and changeable services such as cloud computing and data centers are met.

In some embodiments, the first network interface (network interface a 110) and the second network interface (network interface B120) comprise a first network aggregation interface (network aggregation interface C192). When the first child drive 105 has been offloaded, the parent drive 102 closes the link through the first network interface (network interface a 110) and switches the link traffic through the first network interface (network interface a 110) to the link through the second network interface (network interface B120), such that the link traffic through the first network interface (network interface a 110) is handled by the second child device (child device B128 of network interface B120) driven by the second child drive 106. And, when the second child drive 106 has been offloaded, the parent drive 102 closes the link through the second network interface (network interface B120) and switches the link traffic through the second network interface (network interface B120) to the link through the first network interface (network interface a 110), so that the link traffic through the second network interface (network interface B120) is processed by the first child device (child device a118 of network interface a 110) driven by the first child drive 105. In this way, by using the link failure switching technology of the network aggregation interface, the first sub-driver 105 and the second sub-driver 106 can be alternately upgraded to keep the network interface and the sub-device unchanged, which is favorable for realizing the upgrade of the kernel network driver under the condition of no external perception, thus reducing the overall complexity, reducing the error probability, simultaneously having the flexibility in terms of service expansion and the reliability in terms of service upgrade, and being favorable for meeting the rapidly-growing, complex and changeable service demands of cloud computing, data centers and the like.

In some embodiments, the third network interface (network interface C130) and the fourth network interface (network interface D140) comprise a second network aggregation interface (network aggregation interface D193). When the first child drive 105 has been offloaded, the parent drive 102 closes the link through the third network interface (network interface C130) and switches the link traffic through the third network interface (network interface C130) to the link through the fourth network interface (network interface D140), such that the link traffic through the third network interface (network interface C130) is handled by the fourth child device (child device D148 of network interface D140) driven by the second child drive 106. And, when the second child drive 106 has been offloaded, the parent drive 102 closes the link through the fourth network interface (network interface D140) and switches the link traffic through the fourth network interface (network interface D140) to the link through the third network interface (network interface C130), so that the link traffic through the fourth network interface (network interface D140) is processed by the third child device (child device C138 of network interface C130) driven by the first child drive 105. In this way, by using the link failure switching technology of the network aggregation interface, the first sub-driver 105 and the second sub-driver 106 can be alternately upgraded to keep the network interface and the sub-device unchanged, which is favorable for realizing the upgrade of the kernel network driver under the condition of no external perception, thus reducing the overall complexity, reducing the error probability, simultaneously having the flexibility in terms of service expansion and the reliability in terms of service upgrade, and being favorable for meeting the rapidly-growing, complex and changeable service demands of cloud computing, data centers and the like. And, as shown in fig. 3, the first network interface (network interface a 110) and the second network interface (network interface B120) constitute a first network aggregation interface (network aggregation interface C192), and a hot upgrade, that is, a kernel network driver upgrade, is implemented between member ports in the first network aggregation interface (network aggregation interface C192) through link switching without interrupting traffic. In addition, the third network interface (network interface C130) and the fourth network interface (network interface D140) constitute a second network aggregation interface (network aggregation interface D193), and thermal upgrade, that is, core network driver upgrade, is achieved by link switching between member ports in the second network aggregation interface (network aggregation interface D193) without interrupting traffic. Further, by dispersing the load of the kernel network driver that the first sub-driver 105 and the second sub-driver 106 need to support, for example, keeping the number of sub-devices bound by the first sub-driver 105 and the second sub-driver 106 consistent, which means that by using the link failover technology of the network aggregation interface, the first sub-driver 105 and the second sub-driver 106 can be upgraded by alternately upgrading, that is, operating two sub-drivers each time, so that on the premise of ensuring that the service is not interrupted, the upgrading of the kernel network driver corresponding to the whole network interface and the sub-device is realized, thus reducing the overall complexity and the error probability, meanwhile, the system has flexibility in service expansion and reliability in service upgrading, and is beneficial to meeting the rapidly-growing, complex and changeable service demands of cloud computing, data centers and the like.

In some embodiments, the first sub-driver 105 and the second sub-driver 106 are alternately upgraded, and the first sub-driver 105 and the second sub-driver 106 are not simultaneously offloaded, and the first network interface (network interface a 110) and the third network interface (network interface C130) are maintained during the first sub-driver 105 upgrade, and the second network interface (network interface B120) and the fourth network interface (network interface D140) are maintained during the second sub-driver 106 upgrade. Therefore, on the premise of ensuring uninterrupted service, the upgrading of the core network drive corresponding to the integral network interface and the sub-equipment is realized, so that the integral complexity is reduced, the error probability is reduced, the flexibility in the aspect of service expansion and the reliability in the aspect of service upgrading are simultaneously realized, and the requirements of rapidly-increased, complex and changeable service such as cloud computing, data centers and the like are favorably met.

In some embodiments, the plurality of network interfaces includes an even number of network interfaces, the plurality of sub-devices includes an even number of sub-devices, the first sub-driver 105 binds the odd numbered sub-devices of the plurality of sub-devices and provides a sub-network device operation interface and a sub-ethernet operation interface corresponding to the network interface corresponding to the sub-device to which the first sub-driver 105 binds, and the second sub-driver 106 binds the even numbered sub-devices of the plurality of sub-devices and provides a sub-network device operation interface and a sub-ethernet operation interface corresponding to the network interface corresponding to the sub-device to which the second sub-driver 106 binds. In this way, by dispersing the load of the kernel network driver required to be supported by each of the first sub-driver 105 and the second sub-driver 106, the odd-numbered sub-devices are bound by the first sub-driver 105 and the even-numbered sub-devices are bound by the second sub-driver 106, and the even-numbered network interfaces and the even-numbered sub-devices mean that the number of the sub-devices bound by each of the first sub-driver 105 and the second sub-driver 106 can be kept consistent, so that the link failure switching technology of the network aggregation interface can be utilized, the first sub-driver 105 and the second sub-driver 106 can be alternately upgraded, that is, the upgrading of the kernel network driver corresponding to the whole network interface and the sub-device can be realized on the premise of ensuring that the service is not interrupted, so that the whole complexity is reduced, the error probability is reduced, the flexibility in the aspect of service expansion and the reliability in the aspect of service upgrading are simultaneously realized, and the service requirements of fast-growing, complexity and changeability in the aspect of cloud computing and data center are favorably met.

In some embodiments, each two network interfaces in the plurality of network interfaces form a same network aggregation interface, and member ports in the same network aggregation interface correspond to the first child driver 105 and the second child driver 106, respectively. Therefore, the number of the sub-devices bound by the first sub-driver 105 and the second sub-driver 106 is kept consistent by dispersing the load of the kernel network drivers required to be supported by the first sub-driver 105 and the second sub-driver 106, and thus, by using the link failure switching technology of the network aggregation interface, the upgrade of the first sub-driver 105 and the second sub-driver 106, namely, the upgrade of two sub-drivers operated in sequence each time, can be realized on the premise of ensuring uninterrupted service, the upgrade of the kernel network drivers corresponding to the whole network interface and the sub-devices is realized, the overall complexity is reduced, the error probability is reduced, and meanwhile, the flexibility in the aspect of service expansion and the reliability in the aspect of service upgrade are provided, and the fast-growing, complex and changeable service demands of cloud computing, data centers and the like are favorably met.

In some embodiments, traffic passing through the same network aggregation interface selects a member port in the same network aggregation interface through hashing. In this way, by using the link failure switching technology of the network aggregation interface, the upgrade of the core network driver corresponding to the whole network interface and the sub-device can be realized by alternately upgrading the first sub-driver 105 and the second sub-driver 106, namely, sequentially operating the upgrade of the two sub-drivers each time, on the premise of ensuring that the service is not interrupted, so that the whole complexity is reduced, the error probability is reduced, the flexibility in the aspect of service expansion and the reliability in the aspect of service upgrade are simultaneously provided, and the fast-growing and complex and changeable service demands of cloud computing, data centers and the like are favorably met.

Fig. 4 is a flow chart of a method for upgrading a kernel network driver according to an embodiment of the present application. The driver upgrade method for kernel network driver shown in fig. 4 is applied to a driver, and the driver includes a parent driver, a first child driver and a second child driver. The drive upgrade method includes the following steps.

Step S410: and loading the first sub-driver after unloading to finish the upgrading of the first sub-driver.

Step S420: and loading the second sub-driver after unloading to finish the upgrading of the second sub-driver.

Wherein the first sub-drive and the second sub-drive are alternately upgraded, and the first sub-drive and the second sub-drive are not unloaded simultaneously. The parent driver is used for managing a plurality of network interfaces and a plurality of pieces of sub-equipment corresponding to the network interfaces one by one, the parent driver is also used for providing a parent network equipment operation interface and a parent Ethernet operation interface corresponding to the network interfaces one by one, the network interfaces comprise a first network interface and a second network interface, the sub-equipment comprises a first sub-equipment and a second sub-equipment, the first network interface corresponds to the first sub-equipment, and the second network interface corresponds to the second sub-equipment. The first sub-driver binds the first sub-device and provides a sub-network device operation interface and a sub-ethernet operation interface corresponding to the first network interface, and the second sub-driver binds the second sub-device and provides a sub-network device operation interface and a sub-ethernet operation interface corresponding to the second network interface. The parent driver causes a parent network device operation interface and a parent ethernet operation interface corresponding to the first network interface to be respectively shorted to a child network device operation interface and a child ethernet operation interface corresponding to the first network interface when the first child driver has been loaded, and the parent driver takes over the first network interface through the parent network device operation interface and the parent ethernet operation interface corresponding to the first network interface when the first child driver has been unloaded.

The method for upgrading the kernel network driver shown in fig. 4 avoids the reconstruction of network interfaces and sub-devices, avoids the occurrence of abnormal interface states, saves the number of reallocated devices and the loss of recreated kernel network interfaces, is beneficial to upgrading the kernel network driver in response to the custom requirement and the service development requirement, is beneficial to realizing the hot upgrading of the driver, does not need service migration or redundant server resources during the upgrading of the driver, and is convenient to expand the number of the network interfaces and expand the service.

Fig. 5 is a schematic structural diagram of a computing device according to an embodiment of the present application, where the computing device 500 includes: one or more processors 510, a communication interface 520, and a memory 530. The processor 510, communication interface 520, and memory 530 are interconnected by a bus 540. Optionally, the computing device 500 may further include an input/output interface 550, where the input/output interface 550 is connected to an input/output device for receiving parameters set by a user, etc. The computing device 500 can be used to implement some or all of the functionality of the device embodiments or system embodiments described above in embodiments of the present application; the processor 510 can also be used to implement some or all of the operational steps of the method embodiments described above in connection with the embodiments of the present application. For example, specific implementations of the computing device 500 performing various operations may refer to specific details in the above-described embodiments, such as the processor 510 being configured to perform some or all of the steps of the above-described method embodiments or some or all of the operations of the above-described method embodiments. For another example, in an embodiment of the present application, the computing device 500 may be used to implement some or all of the functionality of one or more components of the apparatus embodiments described above, and the communication interface 520 may be used in particular for communication functions and the like necessary to implement the functionality of such apparatus, components, and the processor 510 may be used in particular for processing functions and the like necessary to implement the functionality of such apparatus, components.

It should be appreciated that the computing device 500 of fig. 5 may include one or more processors 510, and that the plurality of processors 510 may cooperatively provide processing power in a parallelized connection, a serialized connection, a serial-parallel connection, or any connection, or that the plurality of processors 510 may constitute a processor sequence or processor array, or that the plurality of processors 510 may be separated into primary and secondary processors, or that the plurality of processors 510 may have different architectures such as employing heterogeneous computing architectures. In addition, the computing device 500 shown in FIG. 5, the associated structural and functional descriptions are exemplary and not limiting. In some example embodiments, computing device 500 may include more or fewer components than shown in fig. 5, or combine certain components, or split certain components, or have a different arrangement of components.

Processor 510 may take a variety of specific implementations, for example, processor 510 may include one or more combinations of a central processing unit (central processing unit, CPU), a graphics processor (graphic processing unit, GPU), a neural network processor (neural-network processing unit, NPU), a tensor processor (tensor processing unit, TPU), or a data processor (data processing unit, DPU), and embodiments of the present application are not limited in this regard. Processor 510 may also be a single-core processor or a multi-core processor. Processor 510 may be a combination of a CPU and a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (programmable logic device, PLD), or a combination thereof. The PLD may be a complex programmable logic device (complex programmable logic device, CPLD), a field-programmable gate array (FPGA) GATE ARRAY, generic array logic (GENERIC ARRAY logic, GAL), or any combination thereof. Processor 510 may also be implemented solely with logic devices incorporating processing logic, such as an FPGA or Digital Signal Processor (DSP), etc. The communication interface 520 may be a wired interface, such as an ethernet interface, a local interconnect network (local interconnect network, LIN), etc., or a wireless interface, such as a cellular network interface or using a wireless lan interface, etc., for communicating with other modules or devices.

The memory 530 may be a nonvolatile memory such as a read-only memory (ROM), a Programmable ROM (PROM), an erasable programmable ROM (erasable PROM, EPROM), an electrically erasable programmable EPROM (EEPROM), or a flash memory. Memory 530 may also be volatile memory, which may be random access memory (random access memory, RAM) used as external cache. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate synchronous dynamic random access memory (double DATA RATE SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous link dynamic random access memory (SYNCHLINK DRAM, SLDRAM), and direct memory bus random access memory (direct rambus RAM, DR RAM). Memory 530 may also be used to store program code and data such that processor 510 invokes the program code stored in memory 530 to perform some or all of the operational steps of the method embodiments described above, or to perform corresponding functions in the apparatus embodiments described above. Moreover, computing device 500 may contain more or fewer components than shown in FIG. 5, or may have a different configuration of components.

Bus 540 may be a peripheral component interconnect express (PERIPHERAL COMPONENT INTERCONNECT EXPRESS, PCIe) bus, or an extended industry standard architecture (extended industry standard architecture, EISA) bus, a unified bus (unified bus, ubus or UB), a computer quick link (compute express link, CXL), a cache coherent interconnect protocol (cache coherent interconnect for accelerators, CCIX), or the like. The bus 540 may be classified into an address bus, a data bus, a control bus, and the like. The bus 540 may include a power bus, a control bus, a status signal bus, and the like in addition to a data bus. But is shown with only one bold line in fig. 5 for clarity of illustration, but does not represent only one bus or one type of bus.

The method and the device provided by the embodiment of the application are based on the same inventive concept, and because the principle of solving the problem by the method and the device is similar, the embodiment, the implementation, the example or the implementation of the method and the device can be mutually referred, and the repetition is not repeated. Embodiments of the present application also provide a system comprising a plurality of computing devices, each of which may be structured as described above. The functions or operations that may be implemented by the system may refer to specific implementation steps in the above method embodiments and/or specific functions described in the above apparatus embodiments, which are not described herein.

Embodiments of the present application also provide a computer-readable storage medium having stored therein computer instructions which, when executed on a computer device (e.g., one or more processors), implement the method steps of the method embodiments described above. The specific implementation of the processor of the computer readable storage medium in executing the above method steps may refer to specific operations described in the above method embodiments and/or specific functions described in the above apparatus embodiments, which are not described herein again.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. The application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Embodiments of the application may be implemented, in whole or in part, in software, hardware, firmware, or any other combination. When implemented in software, the above-described embodiments may be implemented in whole or in part in the form of a computer program product. The present application may take the form of a computer program product embodied on one or more computer-usable storage media having computer-usable program code embodied therein. The computer program product includes one or more computer instructions. When loaded or executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line), or wireless (e.g., infrared, wireless, microwave, etc.). Computer readable storage media can be any available media that can be accessed by a computer or data storage devices, such as servers, data centers, etc. that contain one or more collections of available media. Usable media may be magnetic media (e.g., floppy disks, hard disks, tape), optical media, or semiconductor media. The semiconductor medium may be a solid state disk, or may be a random access memory, flash memory, read only memory, erasable programmable read only memory, electrically erasable programmable read only memory, register, or any other form of suitable storage medium.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. Each flow and/or block of the flowchart and/or block diagrams, and combinations of flows and/or blocks in the flowchart and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks. These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks. These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to the related descriptions of other embodiments. It will be apparent to those skilled in the art that various modifications and variations can be made to the embodiments of the present application without departing from the spirit or scope of the embodiments of the application. The steps in the method of the embodiment of the application can be sequentially adjusted, combined or deleted according to actual needs; the modules in the system of the embodiment of the application can be divided, combined or deleted according to actual needs. The present application is also intended to include such modifications and alterations if they come within the scope of the claims and the equivalents thereof.

Claims

1. A driver for a kernel network driver, the driver comprising:

A parent driver, wherein the parent driver is used for managing a plurality of network interfaces and a plurality of child devices corresponding to the network interfaces one by one, the parent driver is also used for providing a parent network device operation interface and a parent ethernet operation interface corresponding to the network interfaces one by one, the network interfaces comprise a first network interface and a second network interface, the child devices comprise a first child device and a second child device, the first network interface corresponds to the first child device, and the second network interface corresponds to the second child device;

A first sub-driver binding the first sub-device and providing a sub-network device operation interface and a sub-ethernet operation interface corresponding to the first network interface, and a second sub-driver binding the second sub-device and providing a sub-network device operation interface and a sub-ethernet operation interface corresponding to the second network interface,

Wherein when the first child driver has been loaded, the parent driver causes a parent network device operation interface and a parent ethernet operation interface corresponding to the first network interface to be respectively shorted to a child network device operation interface and a child ethernet operation interface corresponding to the first network interface, and when the first child driver has been unloaded, the parent driver takes over the first network interface through the parent network device operation interface and the parent ethernet operation interface corresponding to the first network interface.

2. The driver of claim 1, wherein the parent driver causes a parent network device operational interface and a parent ethernet operational interface corresponding to the second network interface to be respectively shorted to a child network device operational interface and a child ethernet operational interface corresponding to the second network interface when the second child driver has been loaded, and wherein the parent driver takes over the second network interface through a parent network device operational interface and a parent ethernet operational interface corresponding to the second network interface when the second child driver has been unloaded.

3. The drive of claim 2, wherein the first sub-drive is unloaded and reloaded to complete the upgrade of the first sub-drive, and wherein the second sub-drive is unloaded and reloaded to complete the upgrade of the second sub-drive.

4. The driver of claim 2, wherein link traffic through the first network interface is handled by the first sub-device driven by the first sub-driver when the first sub-driver has been loaded, and wherein link traffic through the second network interface is handled by the second sub-device driven by the second sub-driver when the second sub-driver has been loaded.

5. The driver of claim 4, wherein the first network interface and the second network interface comprise the same network aggregation interface, wherein when the first child driver has been offloaded, the parent driver closes a link through the first network interface and switches link traffic through the first network interface to a link through the second network interface such that link traffic through the first network interface is handled by the second child device driven by the second child driver, and wherein when the second child driver has been offloaded, the parent driver closes a link through the second network interface and switches link traffic through the second network interface to a link through the first network interface such that link traffic through the second network interface is handled by the first child device driven by the first child driver.

6. The driver of claim 5, wherein when the first child driver has been unloaded and loaded, the first child driver matches the first child device and issues an upgrade end notification for the first child driver, the parent driver opens a link through the first network interface and resumes link traffic through the first network interface from being processed by the first child device driven by the first child driver, and when the second child driver has been unloaded and loaded, the second child driver matches the second child device and issues an upgrade end notification for the second child driver, the parent driver opens a link through the second network interface and resumes link traffic through the second network interface from being processed by the second child device driven by the second child driver.

7. The drive of claim 6, wherein the upgrade end notification of the first sub-drive and the upgrade end notification of the second sub-drive are received by a user through a user kernel access interface or a character device kernel access interface.

8. The drive of claim 5, wherein the first sub-drive and the second sub-drive are alternately upgraded and the first sub-drive and the second sub-drive are not offloaded simultaneously and the first network interface remains during the first sub-drive upgrade and the second network interface remains during the second sub-drive upgrade.

9. The driver of claim 1, wherein the first child driver is coupled to a child device of the plurality of child devices to which the first child driver is coupled via a virtual bus, wherein the second child driver is coupled to a child device of the plurality of child devices to which the second child driver is coupled via the virtual bus, and wherein the parent driver is coupled to a physical bus.

10. The driver of claim 1, wherein the plurality of network interfaces further comprises a third network interface, the plurality of child devices further comprises a third child device, the third network interface corresponds to the third child device, the first child driver binds the third child device and provides child network device operation interfaces and child ethernet operation interfaces corresponding to the third network interface, when the first child driver has been loaded, the parent driver causes parent network device operation interfaces and parent ethernet operation interfaces corresponding to the third network interface to be respectively shorted to child network device operation interfaces and child ethernet operation interfaces corresponding to the third network interface, and when the first child driver has been unloaded, the parent driver takes over the third network interface through parent network device operation interfaces and parent ethernet operation interfaces corresponding to the third network interface, and when the first child driver has been loaded, traffic through the link of the third network interface is handled by the third child driver of the first child driver.

11. The driver of claim 10, wherein the first network interface, the second network interface, and the third network interface comprise a same network aggregate interface, wherein when the first child driver has been offloaded, the parent driver closes a link through the third network interface and switches link traffic through the third network interface to a link through the second network interface such that link traffic through the third network interface is handled by the second child device driven by the second child driver, and wherein when the first child driver has been offloaded and loaded, the first child driver matches the third child device, wherein the parent driver opens a link through the third network interface and resumes link traffic through the third network interface to be handled by the third child device driven by the first child driver, and wherein the third network interface remains during the first child driver upgrade.

12. The driver of claim 1, wherein the plurality of network interfaces further comprises a third network interface and a fourth network interface, the plurality of child devices further comprising a third child device and a fourth child device, the third network interface corresponding to the third child device, the fourth network interface corresponding to the fourth child device, the first child driver binding the third child device and providing a child network device operation interface and a child ethernet operation interface corresponding to the third network interface, the second child driver binding the fourth child device and providing a child network device operation interface and a child ethernet operation interface corresponding to the fourth network interface, the parent driver causing a parent network device operation interface and a parent ethernet operation interface corresponding to the third network interface to be respectively shorted to the child network device operation interface and the child ethernet operation interface corresponding to the third network interface when the first child driver has been unloaded, the parent network device operation interface and the child ethernet operation interface corresponding to the third network interface being respectively taken over by the parent driver, the parent driver causing the parent network device operation interface and the parent device operation interface corresponding to be respectively shorted to the third network interface and the fourth network device operation interface when the first child driver has been unloaded, the parent driver being loaded with the parent device operation interface and the fourth network interface.

13. The driver of claim 12, wherein link traffic through the third network interface is handled by the third sub-device driven by the first sub-driver when the first sub-driver has been loaded, and wherein link traffic through the fourth network interface is handled by the fourth sub-device driven by the second sub-driver when the second sub-driver has been loaded.

14. The driver of claim 13, wherein the first network interface and the second network interface comprise a first network aggregation interface, wherein when the first child driver has been offloaded, the parent driver closes a link through the first network interface and switches link traffic through the first network interface to a link through the second network interface such that link traffic through the first network interface is handled by the second child device driven by the second child driver, and wherein when the second child driver has been offloaded, the parent driver closes a link through the second network interface and switches link traffic through the second network interface to a link through the first network interface such that link traffic through the second network interface is handled by the first child device driven by the first child driver.

15. The driver of claim 14, wherein the third network interface and the fourth network interface comprise a second network aggregation interface, wherein when the first child driver has been offloaded, the parent driver closes a link through the third network interface and switches link traffic through the third network interface to a link through the fourth network interface such that link traffic through the third network interface is handled by the fourth child device driven by the second child driver, and wherein when the second child driver has been offloaded, the parent driver closes a link through the fourth network interface and switches link traffic through the fourth network interface to a link through the third network interface such that link traffic through the fourth network interface is handled by the third child device driven by the first child driver.

16. The drive of claim 15, wherein the first sub-drive and the second sub-drive are alternately upgraded and the first sub-drive and the second sub-drive are not offloaded simultaneously and the first network interface and the third network interface remain during the first sub-drive upgrade and the second network interface and the fourth network interface remain during the second sub-drive upgrade.

17. The driver of claim 12, wherein the plurality of network interfaces includes an even number of network interfaces, the plurality of sub-devices includes an even number of sub-devices, the first sub-driver binds an odd numbered sub-device of the plurality of sub-devices and provides a sub-network device operation interface and a sub-ethernet operation interface corresponding to a network interface corresponding to a sub-device to which the first sub-driver binds, and the second sub-driver binds an even numbered sub-device of the plurality of sub-devices and provides a sub-network device operation interface and a sub-ethernet operation interface corresponding to a network interface corresponding to a sub-device to which the second sub-driver binds.

18. The driver of claim 17, wherein each two of the plurality of network interfaces comprise a same network aggregate interface, and wherein member ports in the same network aggregate interface correspond to the first sub-driver and the second sub-driver, respectively.

19. The driver of claim 18, wherein traffic passing through the same network aggregation interface selects a member port in the same network aggregation interface by hashing.

20. A driver upgrade method for a kernel network driver, wherein the driver includes a parent driver, a first child driver, and a second child driver, the driver upgrade method comprising:

Loading the first sub-driver after unloading to finish upgrading of the first sub-driver;

By unloading and reloading the second sub-driver to complete the upgrade of the second sub-driver,

Wherein the first sub-drive and the second sub-drive are alternately upgraded, and the first sub-drive and the second sub-drive are not unloaded simultaneously,

Wherein the parent driver is used for managing a plurality of network interfaces and a plurality of child devices corresponding to the network interfaces one by one, the parent driver is also used for providing a parent network device operation interface and a parent Ethernet operation interface corresponding to the network interfaces one by one, the network interfaces comprise a first network interface and a second network interface, the child devices comprise a first child device and a second child device, the first network interface corresponds to the first child device, the second network interface corresponds to the second child device,

Wherein the first sub-driver binds the first sub-device and provides a sub-network device operation interface and a sub-ethernet operation interface corresponding to the first network interface, the second sub-driver binds the second sub-device and provides a sub-network device operation interface and a sub-ethernet operation interface corresponding to the second network interface,