CN116450221A

CN116450221A - CPU-driven calling method, device and equipment

Info

Publication number: CN116450221A
Application number: CN202310290259.3A
Authority: CN
Inventors: 张亮; 孙鑫; 彭飞; 郭凯
Original assignee: Longxin Zhongke Hefei Technology Co ltd
Current assignee: Longxin Zhongke Hefei Technology Co ltd
Priority date: 2023-03-21
Filing date: 2023-03-21
Publication date: 2023-07-18

Abstract

The method, the device and the equipment for calling the CPU driver are applied to first electronic equipment, and the method comprises the following steps: receiving an access request sent by second electronic equipment; based on the access request, determining the physical machine with the driving information as the target equipment in the physical machines contained in the cluster, and sending the access request to the target equipment; the driving information in the target equipment is used for being sent to the second electronic equipment; the cluster comprises a plurality of physical machines, wherein the central processor architecture supported by at least one physical machine is different from the central processor architecture supported by the other physical machines; the physical machine is configured with a container including drive information corresponding to a central processing unit architecture supported by the physical machine. The method avoids the complex process of screening and searching the driving information to be called in the disclosed massive information by the user, and improves the efficiency of calling the driving information by the second electronic equipment.

Description

CPU-driven calling method, device and equipment

Technical Field

The present disclosure relates to the field of electronic technologies, and in particular, to a method, an apparatus, and a device for calling a central processing unit driver.

Background

Currently, different architectures of different cpus correspond to different driving information. In the electronic device, driving information corresponding to the architecture of the central processing unit is required to be installed, so that the central processing unit in the electronic device can control external devices (for example, a sound box, a printer and the like connected with the electronic device) of the electronic device based on the driving information.

Therefore, how to acquire the required driving information by the electronic device is an urgent problem to be solved.

Disclosure of Invention

The method, the device, the equipment and the device for calling the CPU driver are used for calling the driving information by the electronic equipment.

In a first aspect, the present application provides a method for invoking a cpu driver, applied to a first electronic device, where the method includes:

receiving an access request sent by second electronic equipment, wherein the access request is used for indicating a request for acquiring driving information;

based on the access request, determining the physical machine with the driving information as a target device in the physical machines contained in the cluster, and sending the access request to the target device; the driving information in the target device is used for being sent to the second electronic device; the cluster includes a plurality of physical machines and, the central processor architecture supported by at least one physical machine in the plurality of physical machines is different from the central processor architecture supported by the rest physical machines; the physical machine is provided with a container comprising driving information corresponding to a central processing unit architecture supported by the physical machine.

In some embodiments, the first electronic device has a plurality of first interfaces, where the first interfaces corresponding to the physical machines with different driving information are different, and the first interfaces corresponding to the physical machines with the same driving information are the same; the access request is specifically used for indicating that the physical machine corresponding to the first interface is requested to have driving information;

receiving an access request sent by a second electronic device, including:

based on the first interface, receiving an access request sent by the second electronic equipment;

based on the access request, determining the physical machine with the driving information as a target device in the physical machines contained in the cluster, and sending the access request to the target device, wherein the method comprises the following steps:

based on the first interface, determining a physical machine corresponding to the first interface as a target device in physical machines contained in a cluster; and sending the access request to the target device.

In some embodiments, the container in the physical machine has tag information for indicating a type of central processor architecture to which the driving information stored in the container corresponds; the first interface has an interface name;

Based on the first interface, determining the physical machine corresponding to the first interface as the target device in the physical machines contained in the cluster, including:

based on the first interface, determining a physical machine corresponding to the first interface according to label information of each container in the cluster, interface names of the first interface and a preset corresponding relation, and determining the physical machine corresponding to the first interface as target equipment, wherein the preset corresponding relation is used for indicating the corresponding relation between the interface names of the first interface and the label information.

In some embodiments, the first interface corresponds to a plurality of physical machines;

based on the first interface, determining a physical machine corresponding to the first interface as an alternative device in physical machines contained in the cluster;

based on the first interface, acquiring the occupation amount of the network traffic of the alternative device and the number of the access requests currently received by the first interface, and determining the target device corresponding to the access requests at the alternative device according to the occupation amount of the network traffic of the alternative device and the number of the access requests currently received by the first interface.

In some embodiments, the first electronic device has a second interface that is a performance layer transition interface; transmitting the access request to the target device, comprising:

transmitting address information of the target device and the access request to a second interface in the first electronic device based on the first interface;

and carrying out format conversion processing on the access request based on the second interface, and sending the access request after format conversion to the target equipment based on the address information of the target equipment.

In some embodiments, the driving information deployed in the container of the target device is a driving instruction set obtained by analyzing driving information corresponding to a central processor architecture supported by the target device.

In some embodiments, the method further comprises:

and if the newly-added physical machine exists in the cluster, a container is arranged in the newly-added physical machine, wherein the container comprises driving information corresponding to a central processing unit architecture supported by the physical machine, and the newly-added physical machine is used for receiving an access request sent by the first electronic device and sending the driving information in the container to a second electronic device corresponding to the access request when the first electronic device determines that the newly-added physical machine is a target device.

In a second aspect, the present application provides a central processing unit driven calling device, applied to a first electronic device, where the device includes:

the receiving unit is used for receiving an access request sent by the second electronic equipment, wherein the access request is used for indicating a request for acquiring driving information;

a determining unit configured to determine, based on the access request, a physical machine having the driving information as a target device among physical machines included in the cluster;

a sending unit, configured to send the access request to the target device; the driving information in the target device is used for being sent to the second electronic device; the cluster comprises a plurality of physical machines, wherein the central processor architecture supported by at least one physical machine is different from the central processor architecture supported by the other physical machines; the physical machine is provided with a container comprising driving information corresponding to a central processing unit architecture supported by the physical machine.

In some embodiments, the first electronic device has a plurality of first interfaces, where the first interfaces corresponding to the physical machines with different driving information are different, and the first interfaces corresponding to the physical machines with the same driving information are the same; the access request is specifically used for indicating that the physical machine corresponding to the first interface is requested to have driving information; the receiving unit is specifically configured to:

the determining unit is specifically configured to:

based on the first interface, determining a physical machine corresponding to the first interface as a target device in physical machines contained in a cluster;

and the sending unit is specifically used for sending the access request to the target equipment based on the first interface.

In some embodiments, the container in the physical machine has tag information for indicating a type of central processor architecture to which the driving information stored in the container corresponds; the first interface has an interface name; the determining unit is specifically configured to:

In some embodiments, the first interface corresponds to a plurality of physical machines; a determining unit including

The first determining module is used for determining a physical machine corresponding to the first interface as an alternative device in the physical machines contained in the cluster based on the first interface;

the second determining module is configured to obtain, based on the first interface, a occupation amount of network traffic of the candidate device and a number of access requests currently received by the first interface, and determine, at the candidate device, a target device corresponding to the access request according to the occupation amount of network traffic of the candidate device and the number of access requests currently received by the first interface.

In some embodiments, the first electronic device has a second interface that is a performance layer transition interface; a transmitting unit comprising:

the sending module is used for sending the address information of the target equipment and the access request to a second interface in the first electronic equipment based on the first interface;

and the conversion module is used for carrying out format conversion processing on the access request based on the second interface and sending the access request after format conversion to the target equipment based on the address information of the target equipment.

In some embodiments, the apparatus further comprises:

the deployment unit is configured to, if it is determined that a newly-added physical machine exists in the cluster, deploy a container in the newly-added physical machine, where the container includes driving information corresponding to a central processor architecture supported by the physical machine, and when the newly-added physical machine is determined to be a target device by the first electronic device, receive an access request sent by the first electronic device, and send the driving information in the container to a second electronic device corresponding to the access request.

In a third aspect, the present application provides an electronic device, comprising: a memory, a processor;

a memory; a memory for storing the processor-executable instructions;

wherein the processor is configured to perform the method according to any of the first aspects according to the executable instructions.

In a fourth aspect, the present application provides a computer-readable storage medium having stored therein computer-executable instructions for performing the method of any of the first aspects when executed by a processor.

In a fifth aspect, the present application provides a computer program product comprising a computer program which, when executed by a processor, implements the method of any one of the first aspects.

The method, the device and the equipment for calling the CPU driver are applied to first electronic equipment, and the method comprises the following steps: receiving an access request sent by second electronic equipment, wherein the access request is used for indicating a request for acquiring driving information; based on the access request, determining the physical machine with the driving information as a target device in the physical machines contained in the cluster, and sending the access request to the target device; the driving information in the target device is used for being sent to the second electronic device; the cluster comprises a plurality of physical machines, wherein the central processor architecture supported by at least one physical machine is different from the central processor architecture supported by the other physical machines; the physical machine is provided with a container comprising driving information corresponding to a central processing unit architecture supported by the physical machine. According to the method, a plurality of physical machines can be deployed in the cluster, different driving information can be set among different physical machines, when the second electronic device needs to call the driving information, the first electronic device can find the physical machine with the driving information indicated by the access request in the cluster by sending the access request to the first electronic device, and the determined physical machine (namely, the target device) sends the driving information to the second electronic device. By the method, each second electronic device supporting different CPU architectures can call the driving information required by each second electronic device in a mode of accessing the first electronic device, so that a complex process of screening and searching the driving information required to be called in the disclosed massive information by a user is avoided, and the efficiency of calling the driving information by the second electronic device is improved.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.

Fig. 1 is a schematic flow chart of a central processing unit driven calling method according to an embodiment of the present application;

FIG. 2 is a flow chart of a second CPU driven calling method provided in the present application;

FIG. 3 is a schematic diagram of a cluster architecture according to an embodiment of the present disclosure;

fig. 4 is a schematic structural diagram of a central processing unit driven calling device according to an embodiment of the present application;

FIG. 5 is a schematic diagram of a CPU driven calling device according to an embodiment of the present disclosure;

fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Specific embodiments thereof have been shown by way of example in the drawings and will herein be described in more detail. These drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with aspects of the present application.

Currently, with the continuous development of electronic technology, the types of central processor architectures are increasing, such as RSIC-V architecture, ARM architecture, X86 architecture, and Loongarch architecture. Because different central processing unit architectures correspond to different driving information, the electronic equipment needs to be provided with the driving information corresponding to the central processing unit architecture arranged inside the electronic equipment, and the peripheral connected with the electronic equipment can be controlled, wherein the central processing unit can convert an instruction which needs to be issued to the peripheral into an instruction which can be recognized by the peripheral based on the driving information, or can convert an instruction returned by the peripheral into an instruction which can be recognized by the central processing unit based on the driving information. In practical applications, the above-mentioned driving information may be understood as a binary driver. For example, when the electronic device needs to connect to the printing device, the central processor in the electronic device needs to configure the binary driver of the printing device, and the configured binary driver needs to correspond to the central processor architecture. Then, the central processing unit can convert the information such as the data to be printed or the printing control instruction and the like into the data or the instruction which can be identified by the printing equipment based on the configured binary driver, so that the central processing unit can control the printing equipment. Therefore, how to implement installation calls to the central processor driver is an urgent issue to be resolved.

In the related technology, a user can search related driving information on the internet to call the driving information, but because of more information on the internet, the user cannot accurately screen the driving information really needed in the driving information, and the driving information call fails.

The method, the device and the equipment for calling the CPU driver are used for solving the technical problems.

Technical term interpretation:

the container is a mirrored runtime instance. Just as a virtual machine is launched from a virtual machine template, a user may launch one or more containers from a single image as well. The greatest distinction between a virtual machine and a container is that the container is faster and lighter-the container will share the operating system/kernel of the host it is hosting (e.g., one physical machine in this embodiment can be considered as the host here) than the virtual machine runs on top of the complete operating system.

A pod is a logical packaging entity that executes containers on a cluster. Each pod can be thought of as a transparent package providing a slot for containers, and a pod can contain a set of one or more containers with shared storage/network resources. In practice, a cluster may run a set of related or unrelated pods, i.e., a cluster may contain many related or unrelated pods, and they are grouped in logical boundaries called namespaces.

A Node is a Node that exists between a pod and a cluster, which is essentially a machine hosting the pod, each Node having some necessary services, whether physical or virtual, to run the pod.

Service is a policy in a cluster to access pod. The pod in the Kubernetes cluster has a life cycle and is not revivable. Each pod has its own IP address, and the destruction and creation of the pod creates an innovative IP address. Service is used to uniformly manage and track the changes of these pod, even if the pod changes, the call to the foreground is not perceived, and the foreground does not need any modification. Service takes over the functions of Service discovery, load balancing, etc.

The following describes the technical solutions of the present application and how the technical solutions of the present application solve the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.

Fig. 1 is a schematic flow chart of a method for calling a central processing unit, which is provided in an embodiment of the present application, where the method provided in the embodiment is applied to a first electronic device, and includes the following steps:

S101, receiving an access request sent by the second electronic equipment, wherein the access request is used for indicating a request for acquiring driving information.

The method for calling the central processing unit driver provided in the present embodiment may be applied to the first electronic device, for example. The second electronic device is a device that needs to invoke the driving information. When the second electronic device needs to call the driving information corresponding to the central processor architecture in the second electronic device, at this time, the second electronic device may send an access request for requesting to acquire the driving information corresponding to the central processor architecture in the second electronic device to the first electronic device.

In one example, when the second electronic device sends the access request, the name of the required driving information may be directly carried in the access request, so that the first electronic device may determine the driving information required by the second electronic device based on the name in the access request; alternatively, the second electronic device may carry the type of central processor architecture supported by the second electronic device in the access request so that the first electronic device may determine the driving information it needs based on the central processor architecture supported by the second electronic device.

S102, determining a physical machine with driving information as a target device in physical machines contained in the cluster based on the access request, and sending the access request to the target device; the driving information in the target equipment is used for being sent to the second electronic equipment; the cluster comprises a plurality of physical machines, wherein the central processor architecture supported by at least one physical machine is different from the central processor architecture supported by the other physical machines; the physical machine is configured with a container including drive information corresponding to a central processing unit architecture supported by the physical machine.

For example, in the cluster in this embodiment, a plurality of physical machines are included, where each physical machine may be provided with a container, and drive information corresponding to a central processor architecture supported by the physical machine (the drive information is also referred to as a binary drive in practical application) is stored in the container. And, there is at least one physical machine in the cluster different from the CPU architecture supported by the remaining physical machines. For example, in practical applications, the cluster in this embodiment may be a Kubernetes cluster. Kubernetes (often abbreviated as K8 s) is an open source system for automatically deploying, expanding, and managing "containerized" applications. 4 physical machines can be arranged in the cluster, wherein the central processor architecture supported by one physical machine is architecture A, and the central processor architectures supported by the other three physical machines can be architecture B. Further, the physical machine supporting the architecture a may be provided with the drive information a corresponding to the architecture a, and the physical machine supporting the architecture B may be provided with the drive information B corresponding to the architecture B. In the same physical machine, one or more containers storing the same drive information may be provided. When a plurality of containers are provided, the resource access rate of the physical machine, that is, the number of access requests that the physical machine can receive at the same time, can be increased. It should be noted that, in this embodiment, the type of the cluster is not limited, and the Kubernetes cluster in the above example may be used or may be the rest of clusters.

In one example, when the first electronic device determines the target device in the cluster, at this time, the type of the driving information included in each physical machine may be determined first, the determined driving information is compared with the type of the driving information indicated in the received access request, and the physical machine where the driving information with the consistent first comparison result is located is taken as the target device.

In this embodiment, after the first electronic device receives the access request sent by the second electronic device, the first electronic device determines, from among the multiple physical machines in the cluster, the physical machine having the driving information indicated by the access request as the target device, and then sends the received access request to the target electronic device, so that the target device sends the driving information in the target device to the second electronic device, so that the second electronic device can call the driving information required by the second electronic device.

It should be understood that in this embodiment, a plurality of physical machines may be deployed in a cluster, and in a plurality of physical machines (i.e., a plurality of hardware devices, for example, a plurality of computer devices, a plurality of server devices), at least one physical machine includes drive information different from drive information included in the other physical machines. When the second electronic device needs to call the driving information, the first electronic device can find the physical machine with the driving information indicated by the access request in the cluster by sending the access request to the first electronic device, and then send the driving information to the second electronic device through the determined physical machine (namely, the target device). By the method, each second electronic device supporting various CPU architectures can call the driving information required by each second electronic device in a mode of accessing the first electronic device, so that a complex process of screening and searching the driving information required to be called in the disclosed massive information by a user is avoided, and the efficiency of calling the driving information by the second electronic device is improved.

Fig. 2 is a flow chart of a second method for invoking a cpu driver according to the present application, where in this embodiment, a first electronic device has a plurality of first interfaces, where the first interfaces corresponding to physical machines with different driving information are different, and the first interfaces corresponding to physical machines with the same driving information are the same; the access request is specifically used for indicating that the physical machine corresponding to the first interface is requested to have driving information. As shown in fig. 2, the method comprises the steps of:

s201, based on the first interface, an access request sent by the second electronic device is received.

Illustratively, in this embodiment, a plurality of first interfaces may be provided at the first electronic device. Wherein the number of first interfaces corresponds to the number of kinds of drive information contained in the cluster. When the first interface is set in the first electronic device, a plurality of physical machines with the same driving information may be correspondingly set with one first interface, and types of driving information included in the physical machines corresponding to different first interfaces are different. Each first interface may be configured to receive an access request for requesting drive information contained in its corresponding physical machine.

For example, fig. 3 is a schematic diagram of a cluster architecture according to an embodiment of the present application. As shown in fig. 3, a Kubernetes cluster is illustrated as an example in this example. The cluster comprises 4 physical machines, wherein the driving information contained in the physical machine 1 and the driving information contained in the physical machine 3 are both driving information A; the driving information contained in the physical machine 2 and the driving information contained in the physical machine 4 are both driving information B, and each physical machine in the figure can be regarded as a Node working Node in a Kubernetes cluster; the containers contained in each physical machine can be seen as pod in the Kubernetes cluster. At this time, when the first interfaces are set, two first interfaces, namely, a first interface 1 and a first interface 2 in the figure, may be set, where the first interface 1 corresponds to the physical machine 1 and the physical machine 3, and the first interface 2 corresponds to the physical machine 2 and the physical machine 4. When the driving information required to be called by the second electronic device is the driving information B, the second electronic device can send an access request to the first interface 2; when the second electronic device needs to request the acquired driving information to be the driving information 1, the second electronic device may send the access request to the first interface 1 at this time. In practical applications, the first interface in the first electronic device may be regarded as Service in the Kubernetes cluster, and the implementation principle may be described by referring to the principles in the related art, which is not described herein again.

That is, in this embodiment, by setting a plurality of first interfaces in the first electronic device, each first interface is responsible for receiving an access request for obtaining the driving information included in the physical machine corresponding to the first interface, and when the second electronic device needs to call the driving information, only the first interface corresponding to the driving information in the first electronic device needs to be called.

S202, determining a physical machine corresponding to a first interface as target equipment in physical machines contained in a cluster based on the first interface; the driving information in the target equipment is used for being sent to the second electronic equipment; the cluster comprises a plurality of physical machines, wherein the central processor architecture supported by at least one physical machine is different from the central processor architecture supported by the other physical machines; the physical machine is configured with a container including drive information corresponding to a central processing unit architecture supported by the physical machine.

In this embodiment, after the first interface in the first electronic device receives the access request, the physical machine corresponding to the first interface in the cluster is taken as the target device.

In some embodiments, when the first interface determines the target device, the current target device may be determined by adopting a polling mode, or the target device may be selected by adopting a random selection mode.

It can be understood that in this embodiment, the same first interfaces may be correspondingly set for physical machines with the same driving information, and the driving information of the physical machines corresponding to different first interfaces is different, so that compared with a mode of correspondingly setting a first interface for each physical machine, the setting mode of the first interfaces provided in this embodiment can reduce the number of first interfaces exposed by the first electronic device outwards, and facilitate the second electronic device to call the first interfaces. In addition, because the driving information of different physical machines corresponding to different first interfaces is different, the setting mode of the first interfaces is adopted, in the first interface screening target equipment, screening is only needed in the physical machines corresponding to the first interfaces, and screening is not needed in all the physical machines in the cluster, so that the calling efficiency of the driving information is improved.

In one example, a container in a physical machine has tag information for indicating a type of central processor architecture to which drive information stored in the container corresponds; the first interface has an interface name; in performing step S202, this may be achieved by:

Based on the first interface, determining a physical machine corresponding to the first interface according to label information of each container in the cluster, interface names of the first interface and a preset corresponding relation, determining the physical machine corresponding to the first interface as target equipment, and the preset corresponding relation is used for indicating the corresponding relation between the interface names of the first interface and the label information.

In this embodiment, the containers included in the physical machine have tag information, and the tag information of each container may indicate a type of cpu architecture corresponding to the driving information stored in the container. For example, when the architecture type of the cpu corresponding to the driving information included in the container in the physical machine is architecture a, the tag information of the container may be set as the tag a. When the cpu architecture type corresponding to the driving information included in the container in the physical machine is architecture B, at this time, the tag information of the container may be set as tag B. The first interfaces also have respective interface names, and the interface names of the first interfaces and the corresponding tag information may be stored in the first electronic device in advance. When the first interface needs to determine the target device, at this time, the first interface may acquire tag information of containers included in each physical machine, determine a container having tag information corresponding to an interface name of the first interface therein, and determine the physical machine provided with the container as the target device.

In this embodiment, when determining the target device, the target device may be determined based on the tag information of the container included in the first interface and the physical machine, so that the driving information required by the second electronic device may be accurately found.

In one example, the first interface corresponds to a plurality of physical machines; the step S202 includes the steps of:

a first step of step S202: and determining the physical machine corresponding to the first interface as an alternative device in the physical machines contained in the cluster based on the first interface.

A second step of step S202: based on the first interface, the occupation amount of the network traffic of the alternative device and the number of the access requests currently received by the first interface are obtained, and the target device corresponding to the access requests is determined at the alternative device according to the occupation amount of the network traffic of the alternative device and the number of the access requests currently received by the first interface.

In this embodiment, when the first interface corresponds to a plurality of physical machines, all the physical machines corresponding to the first interface may be first determined as candidate devices when determining the target device. It is understood that the first interface may receive access requests sent from a plurality of second electronic devices simultaneously. After the first interface receives the access requests, the first interface may obtain the occupancy of network traffic for each of the candidate devices and determine the number of access requests currently received by the first interface. In one example, the occupancy of network traffic for the candidate device may be determined by logging the candidate device, and the occupancy of network traffic for the candidate device may be determined by screening the log for the number of access requests currently being processed by the candidate device.

And acquiring the occupation amount of the network traffic of each candidate device and the number of the currently received access requests at the first interface, and determining the target device corresponding to each access request. For example, a device with a higher network traffic occupancy among the plurality of candidate devices may be deleted, and then a final target device may be selected among the remaining candidate devices.

It can be understood that in this embodiment, when accessing the target device corresponding to the request, the occupation amount of the network traffic of each physical machine corresponding to the first interface may be obtained, and the target device corresponding to each access request received by the first interface may be determined based on the obtained occupation amount of the network traffic of each physical machine and the number of the access requests received in the current first interface, so as to avoid that when the occupation rate of the network traffic of the target device corresponding to the access request is higher, the target device cannot timely send the driving information to the second electronic device corresponding to the access request.

In one possible implementation manner, the first electronic device may determine an operation state of each physical machine in the cluster, where the operation state of the physical machine includes: normal working state, stop working state. Specifically, the first electronic device may determine the number of access requests received by each first interface once every predetermined period. And combining the maximum value of the network traffic occupation quantity supported by each physical machine to determine the working state of each physical machine in the cluster. For example, if the number of access requests acquired by the first interface 1 is smaller than the first preset value within a period of time, at this time, the working states of some physical machines in the plurality of physical machines corresponding to the first interface 1 may be set to a stop working state, so as to avoid the situation that the plurality of physical machines are simultaneously in a low network traffic occupation amount within a period of time, improve the network traffic occupation amount of each physical machine, and further avoid unnecessary resource consumption of the physical machines.

S203, the first electronic equipment is provided with a second interface, and the second interface is a representation layer state conversion interface; and transmitting the address information of the target device and the access request to a second interface in the first electronic device based on the first interface.

S204, performing format conversion processing on the access request based on the second interface, and sending the access request after format conversion to the target device based on the address information of the target device.

Illustratively, the present embodiment also has a second interface at the first electronic device due to a different second electronic device, wherein the second interface is a presentation state transition interface (Restful Application Program Interface). When the first interface receives the access request, the access request received by the first interface can be sent to a second interface in the first electronic device, constraint conditions of the access request are preset in the second interface, the constraint conditions are used for carrying out format conversion processing on the received access request, the access request after format conversion is sent to the target device, so that the target device in the cluster can accurately identify the received access request, and driving information stored in the target device can be sent to the second electronic device for sending the access request. In addition, when the first interface sends the access request to the second interface, the address information of the target device determined by the first interface is also sent to the second interface, so that after the second interface performs format conversion processing on the access request, the second interface can send the access request after the format conversion processing to the target device based on the address information of the target device. In this embodiment, the number of the second interfaces is not particularly limited, and one second interface may be provided, or a plurality of second interfaces may be provided.

In one possible implementation manner, the second interface in the first electronic device may also be used to receive the access request sent by the second electronic device, after format conversion of the access request, send the access request to the first interface that needs to be sent, and determine the target device by the first interface

It can be appreciated that in this embodiment, by setting the second interface, access requests from different second electronic devices may be converted into access requests in the same format, so that the target devices in the cluster may accurately send the driving information to the second electronic devices.

In some embodiments, based on any one of the foregoing embodiments, in this embodiment, the driving information deployed in the container of the target device is a driving instruction set obtained by analyzing driving information corresponding to a central processor architecture supported by the target device.

In this embodiment, in order to improve the efficiency of installing the driving information in the second electronic device, the driving information pre-stored in the container of the target device is a driving instruction set obtained by analyzing the driving information corresponding to the cpu architecture supported by the target device, that is, the driving instruction set is stored in the container in this embodiment. When the target device sends the driving information to the second electronic device, the target device can directly send the driving instruction set obtained after analysis to the second electronic device, and the second electronic device can directly install and process the driving instruction set after receiving the driving instruction set, so that the complicated step that the second electronic device needs to analyze the driving information is omitted.

In some embodiments, if it is determined that a newly added physical machine exists in the cluster on the basis of any one of the embodiments, a container is deployed in the newly added physical machine, where the container includes driving information corresponding to a central processing unit architecture supported by the physical machine, and the newly added physical machine is configured to receive, when the newly added physical machine is determined to be a target device by the first electronic device, an access request sent by the first electronic device, and send the driving information in the container to a second electronic device corresponding to the access request.

In this embodiment, the first electronic device may further monitor the physical machines included in the cluster in real time, and when the first electronic device determines that a new physical machine joins the cluster, the first electronic device may first determine a central processor architecture supported by the physical machine, and deploy a container to the newly joined physical machine based on the central processor architecture, and deploy driving information corresponding to the central processor architecture supported by the physical machine to the container.

In addition, in one possible implementation manner, when the architecture of the central processor supported by the newly added physical machine is different from the architecture of the central processor supported by any physical machine in the cluster, the first electronic device may set a first interface corresponding to the physical machine in the first electronic device, so that the subsequent second electronic device may acquire the driving information in the newly added physical machine by sending an access request to the newly added first interface.

In this embodiment, the same first interfaces are correspondingly set for physical machines with the same driving information, and the driving information of the physical machines corresponding to different first interfaces is different, so that compared with a mode of correspondingly setting one first interface for each physical machine, the setting mode of the first interfaces provided in this embodiment can reduce the number of the first interfaces exposed by the first electronic device outwards, and facilitate the second electronic device to call the first interfaces. In addition, because the driving information of different physical machines corresponding to different first interfaces is different, the setting mode of the first interfaces is adopted, in the first interface screening target equipment, screening is only needed in the physical machines corresponding to the first interfaces, and screening is not needed in all the physical machines in the cluster, so that the calling efficiency of the driving information is improved.

Fig. 4 is a schematic structural diagram of a central processing unit driven calling device according to an embodiment of the present application, where the calling device is applied to a first electronic device, and the calling device includes:

a receiving unit 41, configured to receive an access request sent by the second electronic device, where the access request is used to indicate a request to acquire driving information;

A determination unit 42 that determines, based on the access request, a physical machine having drive information among the physical machines included in the cluster as a target device;

a transmitting unit 43 for transmitting the access request to the target device; the driving information in the target equipment is used for being sent to the second electronic equipment; the cluster comprises a plurality of physical machines, wherein the central processor architecture supported by at least one physical machine is different from the central processor architecture supported by the other physical machines; the physical machine is configured with a container including drive information corresponding to a central processing unit architecture supported by the physical machine.

The device provided in this embodiment is configured to implement the technical scheme provided by the method, and the implementation principle and the technical effect are similar and are not repeated.

In some embodiments, the first electronic device has a plurality of first interfaces, where the first interfaces corresponding to the physical machines with different driving information are different, and the first interfaces corresponding to the physical machines with the same driving information are the same; the access request is specifically used for indicating that the request and the physical machine corresponding to the first interface have driving information; the receiving unit 41 is specifically configured to:

The determining unit 42 is specifically configured to:

based on the first interface, determining a physical machine corresponding to the first interface as target equipment in physical machines contained in the cluster;

the sending unit 43 is specifically configured to send the access request to the target device based on the first interface.

In some embodiments, the container in the physical machine has tag information for indicating a type of central processor architecture to which the driving information stored in the container corresponds; the first interface has an interface name; the determining unit 42 is specifically configured to:

FIG. 5 is a schematic structural diagram of a calling device driven by a central processing unit according to an embodiment of the present application, where on the basis of the structure shown in FIG. 4, a first interface corresponds to a plurality of physical machines; a determining unit 42 including

A first determining module 421, configured to determine, based on the first interface, a physical machine corresponding to the first interface as an alternative device in physical machines included in the cluster;

The second determining module 422 is configured to obtain, based on the first interface, a occupation amount of network traffic of the candidate device and a number of access requests currently received by the first interface, and determine, at the candidate device, a target device corresponding to the access request according to the occupation amount of network traffic of the candidate device and the number of access requests currently received by the first interface.

In some embodiments, the first electronic device has a second interface that is a presentation state transition interface; the transmission unit 43 includes:

a sending module 431, configured to send, based on the first interface, address information of the target device and an access request to a second interface in the first electronic device;

the conversion module 432 is configured to perform format conversion processing on the access request based on the second interface, and send the access request after format conversion to the target device based on the address information of the target device.

In some embodiments, the apparatus further comprises:

the deployment unit 44 is configured to, if it is determined that a newly added physical machine exists in the cluster, deploy a container in the newly added physical machine, where the container includes driving information corresponding to a central processor architecture supported by the physical machine, where the newly added physical machine is configured to, when determined as a target device by the first electronic device, receive an access request sent by the first electronic device, and send the driving information in the container to a second electronic device corresponding to the access request.

The application provides an electronic device, comprising: a memory, a processor;

a memory; a memory for storing processor-executable instructions;

the processor is used for executing the method according to the executable instructions.

Fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application, as shown in fig. 6,

an exemplary electronic device 600 is illustrated, and the exemplary electronic device 600 may perform some or all of the mechanisms and actions described above. Exemplary electronic device 600 may include, but is not limited to, one or more Central Processing Units (CPUs) 620, a system memory 630, and a system bus 621 that couples various system components including the system memory to processing unit 620. The system bus 621 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. The electronic device 600 may optionally include graphics hardware, including but not limited to a graphics hardware interface 660 and a display device 661, the display device 661 may include a display device capable of receiving touch-based user input, such as a touch-sensitive or multi-touch enabled display device. Depending on the particular physical implementation, one or more of the CPU 620, system memory 630, and other components of the electronic device 600 may be physically collocated, such as on a single chip. In this case, some or all of the system bus 621 may simply be silicon vias within a single chip structure, and its illustration in FIG. 6 may be symbolized for illustrative purposes only.

Electronic device 600 also typically includes computer readable media, which can include any available media that can be accessed by electronic device 600 and includes both volatile and nonvolatile media, and removable and non-removable media. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. Computer storage media includes media implemented in any method or technology for storage of content such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other storage technology, CD-ROM, digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or may be used to store the desired content, and any other medium that may be accessed by the electronic device 600. Computer storage media, however, does not include communication media. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any content delivery media. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer readable media.

The system memory 630 includes computer storage media in the form of volatile and/or nonvolatile memory such as Read Only Memory (ROM) 631 and Random Access Memory (RAM) 632. A basic input/output system 633 (BIOS), containing the basic routines that help to transfer content between elements within electronic device 600, such as during start-up, is typically stored in ROM 631. RAM 632 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 620. By way of example, and not limitation, fig. 6 illustrates operating system 634, other program modules 635, and program data 636.

The electronic device 600 may also include other removable/non-removable volatile/nonvolatile computer storage media. By way of example only, FIG. 6 illustrates a hard disk drive 641 that reads from or writes to non-removable, nonvolatile magnetic media. Other removable/non-removable, volatile/nonvolatile computer storage media that can be used with the exemplary electronic device include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM, and the other computer storage media defined and described above. The hard disk drive 641 is typically connected to the system bus 621 through a nonvolatile memory interface such as interface 640.

The drives and their associated computer storage media discussed above and illustrated in fig. 6, provide storage of computer readable instructions, data structures, program modules and other data for the electronic device 600. In FIG. 6, for example, hard disk drive 641 is illustrated as storing operating system 644, other program modules 645, and program data 646. Note that these components can either be the same as or different from operating system 634, other program modules 635, and program data 636. Operating system 644, other program modules 645, and program data 646 are given different numbers here to illustrate that, at a minimum, they are different copies.

The electronic device 600 may operate in a networked environment using logical connections to one or more remote computers. Electronic device 600 is shown connected to general network connection 651 (to network 670) through network interface or adapter 650, which network interface or adapter 650 in turn is connected to system bus 621. In a networked environment, program modules depicted relative to the electronic device 600, or portions or peripherals thereof, may be stored in the memory of one or more other electronic devices that are communicatively coupled to the electronic device 600 through the universal network connection 661. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the electronic devices may be used.

Although described as a single physical device, the exemplary electronic device 600 may be a virtual electronic device, in which case the functionality of the physical components described above (such as the CPU 620, system memory 630, network interface 640, and other similar components) may be provided by computer-executable instructions. Such computer-executable instructions may be executed on a single physical electronic device or may be distributed across multiple physical electronic devices, including being distributed across multiple physical electronic devices in a dynamic manner, such that the particular physical electronic device hosting such computer-executable instructions may be dynamically varied over time as needed and availability. Where the exemplary electronic device 600 is a virtualized device, the underlying physical electronic device hosting such a virtualized electronic device may itself comprise physical components similar to those described above and operate in a similar manner. Further, virtual electronic devices may be utilized in multiple layers, with one virtual electronic device executing within the fabric of another virtual electronic device. Thus, as utilized herein, the term "electronic device" refers to a physical electronic device or virtualized computing environment, including virtual electronic devices, in which computer-executable instructions can be executed in a manner consistent with the manner in which the instructions are executed by the physical electronic device. Similarly, as utilized herein, terms referring to physical components of an electronic device refer to those physical components or virtualizations thereof that perform the same or equivalent functions. Further, the logic instructions in the memory 630 may be implemented in the form of software functional units and stored in a computer-readable storage medium when sold or used as a stand-alone product.

The memory 630 is a computer readable storage medium, and may be used to store a software program, a computer executable program, and program instructions/modules corresponding to the methods in the embodiments of the present application. The CPU620 executes the functional applications and data processing by running the software programs, instructions and modules stored in the memory 630, i.e., implements the methods in the method embodiments described above.

Memory 630 may include a storage program area that may store an operating system, at least one application program required for functionality, and a storage data area; the storage data area may store data created according to the use of the terminal device, etc. In addition, the memory 630 may include high-speed random access memory, and may also include nonvolatile memory.

The present application provides a computer-readable storage medium having stored therein computer-executable instructions that, when executed by a processor, perform the method of any one of the above.

The present application provides a computer program product comprising a computer program which, when executed by a processor, implements the method of any one of the claims.

In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described by differences from other embodiments, and identical and similar parts between the embodiments are all enough to be referred to each other.

It will be apparent to those skilled in the art that embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the invention may take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

Embodiments of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations 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 terminal device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal device, 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.

While the preferred embodiments of the present invention have been described, those skilled in the art, once informed of the basic inventive concepts, additional variations and modifications may be made to these embodiments. It is therefore intended that the following claims be interpreted as including the preferred embodiment and all such alterations and modifications as fall within the scope of the embodiments of the invention.

Finally, it is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or terminal device comprising the element.

The foregoing describes in detail a method, apparatus and device for invoking a cpu driver according to the present invention, and specific examples are applied to illustrate the principles and embodiments of the present invention, where the foregoing examples are only for helping to understand the method and core idea of the present invention; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in accordance with the ideas of the present invention, the present description should not be construed as limiting the present invention in view of the above.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It is to be understood that the present application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims

1. A method of central processing unit driven invocation, characterized by being applied to a first electronic device, the method comprising:

based on the access request, determining the physical machine with the driving information as a target device in the physical machines contained in the cluster, and sending the access request to the target device; the driving information in the target device is used for being sent to the second electronic device; the cluster comprises a plurality of physical machines, wherein the central processor architecture supported by at least one physical machine is different from the central processor architecture supported by the other physical machines; the physical machine is provided with a container comprising driving information corresponding to a central processing unit architecture supported by the physical machine.

2. The method of claim 1, wherein the first electronic device has a plurality of first interfaces, wherein the first interfaces corresponding to physical machines having different driving information are different, and the first interfaces corresponding to physical machines having the same driving information are the same; the access request is specifically used for indicating that the physical machine corresponding to the first interface is requested to have driving information;

the receiving the access request sent by the second electronic device includes:

the determining, based on the access request, that the physical machine with the driving information is a target device in the physical machines included in the cluster, and sending the access request to the target device, includes:

3. The method of claim 2, wherein a container in the physical machine has tag information for indicating a type of central processor architecture to which the driving information stored in the container corresponds; the first interface has an interface name;

The determining, based on the first interface, the physical machine corresponding to the first interface as the target device in the physical machines included in the cluster includes:

4. The method of claim 2, wherein the first interface corresponds to a plurality of physical machines;

5. The method of claim 2, wherein the first electronic device has a second interface that is a presentation state transition interface; the sending the access request to the target device includes:

6. The method of claim 1, wherein the driving information deployed in the container of the target device is a driving instruction set obtained by analyzing driving information corresponding to a central processor architecture supported by the target device.

7. The method according to any one of claims 1-6, further comprising:

8. A central processing unit driven recall device for use with a first electronic device, the device comprising:

9. An electronic device, comprising: a processor, and a memory communicatively coupled to the processor;

the memory stores computer-executable instructions;

the processor executes computer-executable instructions stored in the memory to implement the method of any one of claims 1-7.

10. A computer readable storage medium, having stored thereon a computer program, the computer program being executed by a processor to implement the method of any of claims 1-7.

11. A computer program product comprising a computer program which, when executed by a processor, implements the method of any of claims 1-7.