CN114625481A - Data processing method and device, readable medium and electronic equipment - Google Patents

Abstract

The present disclosure relates to a data processing method, apparatus, readable medium, and electronic device. The method includes: receiving a data request message triggered by a user through a virtual machine, where the data request message is used to request processing on a host machine running the virtual machine. target data; according to the data request message, determine the shared data information corresponding to the target data, the shared data information includes a shared queue, and the shared queue is used for direct data interaction between the virtual machine and the host; according to the data request The message and the shared queue process the target data through the kernel of the host. That is to say, the virtual machine of the present disclosure and the host machine can directly perform data interaction by sharing data information, without the need for transit through the Virtiofs Daemon (daemon process) of the host machine, and the kernel of the host machine can directly obtain the data processing request sent by the virtual machine. , in this way, additional system call overhead can be avoided, thereby improving the efficiency of virtual machine data processing.

Description

Data processing method, apparatus, readable medium and electronic device

technical field

The present disclosure relates to the field of computer technology, and in particular, to a data processing method, apparatus, readable medium, and electronic device.

Background technique

With the rise of cloud-native concepts, containers are increasingly used in cloud environments. The image directory corresponding to the container is usually stored in the host. When the security container accesses the corresponding image file, it needs to be implemented through the virtual machine-host shared directory technology, such as the Virtiofs technology.

However, the file access request in the Virtiofs technology needs to be transferred through the user mode Virtiofs Daemon (daemon process), which will bring additional system call overhead, resulting in low efficiency of virtual machine data processing.

SUMMARY OF THE INVENTION

This section is provided to introduce in a simplified form concepts that are described in detail in the detailed description that follows. This section is not intended to identify key features or essential features of the claimed technical solution, nor is it intended to limit the scope of the claimed technical solution.

In a first aspect, the present disclosure provides a data processing method, the method comprising:

receiving a data request message triggered by a user through a virtual machine, where the data request message is used to request to process target data on a host machine running the virtual machine;

determining shared data information corresponding to the target data according to the data request message, where the shared data information includes a shared queue, and the shared queue is used for direct data interaction between the virtual machine and the host;

The target data is processed through the kernel of the host according to the data request message and the shared queue.

In a second aspect, the present disclosure provides a data processing device, the device comprising:

a data request message receiving module, configured to receive a data request message triggered by a user through a virtual machine, where the data request message is used to request to process target data on the host machine running the virtual machine;

A shared data information determination module, configured to determine the shared data information corresponding to the target data according to the data request message, where the shared data information includes a shared queue, and the shared queue is used for the virtual machine and the host machine Direct data exchange between them;

A data processing module, configured to process the target data through the kernel of the host according to the data request message and the shared queue.

In a third aspect, the present disclosure provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processing apparatus, implements the steps of the method described in the first aspect of the present disclosure.

In a fourth aspect, the present disclosure provides an electronic device, comprising:

a storage device having at least one computer program stored thereon;

At least one processing device is configured to execute the at least one computer program in the storage device to implement the steps of the method in the first aspect of the present disclosure.

Through the above technical solution, a data request message triggered by a user through a virtual machine is received, and the data request message is used to request to process target data on the host machine running the virtual machine; according to the data request message, the target is determined Shared data information corresponding to the data, the shared data information includes a shared queue, and the shared queue is used for direct data interaction between the virtual machine and the host; according to the data request message and the shared queue, The target data is processed by the kernel of the host. That is to say, the virtual machine of the present disclosure and the host machine can directly perform data interaction by sharing data information, without the need for transit through the Virtiofs Daemon (daemon process) of the host machine, and the kernel of the host machine can directly obtain the data processing request sent by the virtual machine. , in this way, additional system call overhead can be avoided, thereby improving the efficiency of virtual machine data processing.

Other features and advantages of the present disclosure will be described in detail in the detailed description that follows.

Description of drawings

The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent when taken in conjunction with the accompanying drawings and with reference to the following detailed description. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that the originals and elements are not necessarily drawn to scale. In the attached image:

FIG. 1 is a schematic diagram of file access according to an exemplary embodiment of the present disclosure;

FIG. 2 is a flowchart of a data processing method according to an exemplary embodiment of the present disclosure;

3 is a flowchart of another data processing method according to an exemplary embodiment of the present disclosure;

4 is a schematic diagram of a shared mapping space according to an exemplary embodiment of the present disclosure;

FIG. 5 is a schematic diagram of data processing according to an exemplary embodiment of the present disclosure;

6 is a block diagram of a data processing apparatus according to an exemplary embodiment of the present disclosure;

FIG. 7 is a block diagram of a second data processing apparatus according to an exemplary embodiment of the present disclosure;

8 is a block diagram of a third data processing apparatus according to an exemplary embodiment of the present disclosure;

9 is a block diagram of a fourth data processing apparatus according to an exemplary embodiment of the present disclosure;

10 is a block diagram of a fifth data processing apparatus according to an exemplary embodiment of the present disclosure;

11 is a block diagram of a sixth data processing apparatus according to an exemplary embodiment of the present disclosure;

Fig. 12 is a block diagram of an electronic device according to an exemplary embodiment of the present disclosure.

Detailed ways

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for the purpose of A more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes, and are not intended to limit the protection scope of the present disclosure.

It should be understood that the various steps described in the method embodiments of the present disclosure may be performed in different orders and/or in parallel. Furthermore, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this regard.

As used herein, the term "including" and variations thereof are open-ended inclusions, ie, "including but not limited to". The term "based on" is "based at least in part on." The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions of other terms will be given in the description below.

It should be noted that concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or interdependence.

It should be noted that the modifications of "a" and "a plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless the context clearly indicates otherwise, they should be understood as "one or a plurality of". multiple".

The names of messages or information exchanged between multiple devices in the embodiments of the present disclosure are only for illustrative purposes, and are not intended to limit the scope of these messages or information.

First, the application scenarios of the present disclosure will be described. FIG. 1 is a schematic diagram of a file access according to an exemplary embodiment of the present disclosure. As shown in FIG. 1, the Virtiofs technology uses the FUSE module of the virtual machine kernel to intercept the file access request, and forwards the file access request to the sink through the Virtio mechanism The Virtiofs Daemon (daemon process) of the host, and then the Virtiofs Daemon (daemon process) operates the corresponding files on the host, so that the virtual machine can access the local files of the host. However, the file access request in the Virtiofs technology needs to be transferred through the user mode Virtiofs Daemon (daemon process), which will bring additional system call overhead, resulting in low efficiency of virtual machine data processing.

In order to solve the above-mentioned problems, the present disclosure provides a data processing method, device, readable medium and electronic device. The virtual machine and the host machine can directly perform data interaction by sharing data information without going through the Virtiofs Daemon (daemon process) of the host machine. ) for transit, the kernel of the host machine can directly obtain the data processing request sent by the virtual machine, so that additional system call overhead can be avoided, thereby improving the efficiency of data processing of the virtual machine.

The present disclosure will be described below with reference to specific embodiments.

FIG. 2 is a flowchart of a data processing method according to an exemplary embodiment of the present disclosure. As shown in FIG. 2 , the method may include:

S201. Receive a data request message triggered by a user through a virtual machine.

The data request message may be used to request to process target data on the host running the virtual machine, and the data request message may include a data identifier of the target data. For example, the target data may be a target file, the data request message may be a request to access a target file on the host, and the data request message may include a file identifier of the target file. In this embodiment, the target data is used as the file type for description.

In this step, if the user triggers an access operation to the target data on the host running the virtual machine during the operation of the virtual machine software, the data can be generated according to the data identifier of the target data and the type of the access operation request message.

S202. Determine shared data information corresponding to the target data according to the data request message.

The shared data information may include a shared queue, and the shared queue may be used for direct data interaction between the virtual machine and the host. The shared data information may be stored in a shared mapping space, and both the virtual machine and the host can access the shared mapping space.

In this step, after receiving the data request message, the shared data information corresponding to the target data may be determined from the shared mapping space according to the data request message.

S203. Process the target data through the kernel of the host according to the data request message and the shared queue.

Wherein, the shared queue may include a queue to be processed, and the shared data information further includes an address mapping table.

In this step, after determining the shared queue corresponding to the target data, the data request message can be sent to the pending queue in the shared queue and notified to the host, and the kernel of the host can retrieve the data from the pending queue. Extract the data request message, and process the target data according to the data request message.

In a possible implementation manner, before processing the target data through the kernel of the host machine according to the data request message and the shared queue, the address map corresponding to the physical address of the virtual machine may be determined according to the address mapping table. The virtual address of the host; the address mapping table may include the corresponding relationship between the physical address of the virtual machine and the virtual address of the host; according to the virtual address, the data request message and the shared queue, the kernel of the host is processed the target data.

For example, after determining the virtual address of the host machine corresponding to the physical address of the virtual machine, the data request message can be sent to the pending queue and notified to the host machine, and the kernel of the host machine can retrieve the data from the pending process. The data request message is extracted from the queue, and the target data is processed according to the virtual address and the data request message.

Using the above method, the virtual machine and the host can exchange data through shared data information, without the need to transfer through the host's Virtiofs Daemon (daemon process), and the host's kernel can directly obtain the data processing request sent by the virtual machine. In this way, you can Avoid extra system call overhead, thereby improving the efficiency of virtual machine data processing.

FIG. 3 is a flowchart of another data processing method according to an exemplary embodiment of the present disclosure. As shown in FIG. 3 , the method may include:

S301. Receive a data request message triggered by a user through a virtual machine.

The data request message may be used to request to process target data on the host running the virtual machine, and the data request message may include a data identifier of the target data. For example, the target data may be a target file, the data request message may be a request to access a target file on the host, and the data request message may include a file identifier of the target file. In this embodiment, the target data is used as the file type for description.

S302. Determine whether there is a shared queue corresponding to the target data in the shared mapping space, and if it is determined that there is no shared queue corresponding to the target data in the shared mapping space, perform steps S303 to S306, and after determining the shared mapping If there is a shared queue corresponding to the target data in the space, steps S307 to S314 are executed.

The shared data information may include an address mapping table and a shared queue, the shared queue may be used for data interaction between the virtual machine and the host, and the shared queue may include a pending queue and a completion queue. The shared data information may be stored in the shared mapping space, and both the virtual machine and the host can access the shared mapping space. For example, the shared mapping space may be a BAR (Base Address Register, base address register) in a PCI (Peripheral Component Interconnect, peripheral component interconnect standard) device corresponding to Virtiofs of the virtual machine. The shared mapping space may include two areas, one area is used to store the address mapping table, the other area may include a plurality of mapping block areas, the mapping block area is used to store the mapping information of the opened file, and the mapping information may include Pending queue, completion queue and notification area, different files correspond to different mapped block areas.

It should be noted that, during the startup process of the virtual machine, a corresponding address mapping table can be created for the virtual machine through VMM (Virtual MachineMonitor, virtual machine monitor), and a corresponding EPT (Extended Page Tables, extended page table) mapping can be established, and bind the address mapping table with the area for storing the address mapping table in the shared mapping space.

FIG. 4 is a schematic diagram of a shared mapping space according to an exemplary embodiment of the present disclosure. As shown in FIG. 4 , the size of the shared mapping space is 1GB, the size of the space occupied by the address mapping table is 1MB, and the address The mapping table may include multiple entries, and each entry includes three 64-bit fields: the physical address of the virtual machine, the virtual address of the host, and the mapping length. The space occupied by each mapping block area is 128KB, of which the space occupied by the pending queue is 64KB, and the space occupied by the completion queue is 8KB. The maximum depth of the pending queue and the completion queue can be is 1024, the size of the space occupied by the notification area is 4KB, the remaining space in the mapping block area can be used as a padding area, and the padding area is used for data alignment processing.

In this step, after receiving the data processing request message triggered by the user, the Virtiofs module of the virtual machine kernel can determine whether there is a mapping block area corresponding to the target data in the shared mapping space, and then determine whether the shared mapping space exists in the shared mapping space. When there is a mapping block area corresponding to the target data, it means that there is a shared queue corresponding to the target data in the shared mapping space, and when it is determined that there is no mapping block area corresponding to the target data in the shared mapping space, it means that the There is no shared queue corresponding to the target data in the shared mapping space.

S303. Determine a mapping block area corresponding to the target data from the shared mapping space.

In this step, if it is determined that the shared queue corresponding to the target data does not exist in the shared mapping space, it means that there is no mapping block area corresponding to the target data in the shared mapping space. In this case, the virtual machine The Virtiofs module of the kernel can send a mapping information creation request message to the Virtiofs Daemon (daemon process) through the preset FUSE command. After receiving the mapping information creation request message, the Virtiofs Daemon (daemon process) can send the mapping information to the VMM. A creation request message, after receiving the mapping information creation request message, the VMM can use any space mapping block region in the shared mapping space as a mapping block region corresponding to the target data. For example, the mapping block area in the shared mapping space may be traversed, and the first free mapping block area that is traversed may be used as the mapping block area corresponding to the target data.

S304, initialize the mapping block area.

In this step, after determining the mapping block area corresponding to the target data, the VMM may perform initialization processing on the mapping block area to allocate a corresponding space for the mapping block area.

S305. Create a shared queue corresponding to the target data in the mapping block area.

In this step, after the VMM initializes the mapping block area, the pending queue and the completion queue may be initialized through the io_uring_setup() interface, and a corresponding EPT mapping is established to bind the shared queue to the mapping block area.

Further, after the shared queue corresponding to the target data is created, the shared data information corresponding to the target data and the mapping block area corresponding to the shared data information can be obtained, then, the data identifier corresponding to the target data can be determined, and the The corresponding relationship between the data identifier and the mapping block area is sent to the Virtiofs module of the virtual machine kernel.

S306. Add the target data and the shared queue corresponding to the target data to a preset queue association relationship.

The preset queue association relationship may include correspondence between different data and shared queues.

In this step, after the shared queue corresponding to the target data is created in the mapping block area, the target data and the shared queue corresponding to the target data can be added to the preset queue association relationship. In addition, after the target data is closed , the target data in the preset queue association relationship and the shared queue corresponding to the target data can be deleted.

It should be noted that, for step S302, it is also possible to determine whether there is a shared queue corresponding to the target data in the shared mapping space through the preset queue association relationship. For example, determining the preset queue association relationship includes the target data. In the case of determining that there is a shared queue corresponding to the target data in the shared mapping space, and determining that the preset queue association relationship does not contain the target data, determine that the shared mapping space does not exist in the shared mapping space corresponding to the target data. Shared queue.

S307. Determine shared data information corresponding to the target data according to the data request message.

In this step, when it is determined that there is a shared queue corresponding to the target data in the shared mapping space, the data identifier in the data request message can be determined, according to the correspondence between the pre-established data identifier and the mapping block area The target mapping block area corresponding to the data identifier is determined, and the shared data information stored in the target mapping block area is the shared data information corresponding to the target data.

S308. Determine the virtual address of the host machine corresponding to the physical address of the virtual machine according to the address mapping table.

In this step, after determining the shared data information corresponding to the target data, the virtual address of the host machine corresponding to the physical address of the virtual machine can be determined according to the address mapping table in the shared data information, so as to use the target The physical address of the virtual machine corresponding to the data memory of the data is modified to the virtual address of the host machine.

S309. Determine a shared data request message corresponding to the data request message according to the preset data format.

The preset data format may be a data format that can be processed by the host kernel.

In this step, after determining the shared data information corresponding to the target data, the corresponding information can be extracted from the data request message according to the preset data format to obtain the shared data request message. Exemplarily, the preset data format may be a data structure corresponding to the shared data request message, extracting the element value corresponding to each element in the data structure from the data request message, and filling the data structure with the element value, The shared data request message corresponding to the data request message can be obtained.

S310. Send the shared data request message to the pending queue.

S311. Extract the shared data request message from the queue to be processed through the host.

The mapping block area corresponding to the target data may include a notification area, and the notification area may not establish a corresponding EPT mapping.

In this step, after the shared data request message is sent to the pending queue, a data processing request message may be sent to the host through the notification area, and after the host receives the data processing request message, the data processing request message is sent from the host. The shared data request message is extracted from the pending queue. For example, the notification area can be used to implement the semantics of the io_uring_enter() system call IORING_ENTER_SQ_WAKEUP. When the virtual machine performs an MMIO (Memory-mapped I/O, memory-mapped I/O) write operation to the notification area, You can exit to the KVM (Kernel-based Virtual Machine, kernel-based virtual machine) module, and perform the actual operation corresponding to io_uring_enter() through the KVM module to wake up the sq process on the host to process the data processing request in the pending queue information. In this way, in the non-polling mode (for example, the interrupt mode), the data processing request message can be sent to the host through the io_uring_enter() interface.

It should be noted that when the VMM calls io_uring_enter(), it needs to set the IORING_SETUP_SQPOLL flag at the same time to create a corresponding kernel thread to asynchronously process the shared data request message. In addition, the VMM can call the io_uring_register() interface to perform the IORING_REGISTER_EVENTFD operation, and register the eventfd corresponding to the Virtiofs interrupt of the virtual machine to iouring as a notification method for completing the queue.

S312. Process the target data through the kernel of the host according to the virtual address and the shared data request message.

S313: After processing the target data through the kernel of the host, send the processing result to the completion queue.

In this step, after the kernel of the host machine has processed the target data, it can send the processing result to the completion queue, and notify the Virtiofs module of the virtual machine by means of interrupt injection.

S314. Extract the processing result corresponding to the target data from the completion queue through the virtual machine.

In this step, after receiving the data processing completion notification, the Virtiofs module of the virtual machine can extract the processing result corresponding to the target data from the completion queue.

It should be noted that after the host has processed the target data, if it is determined to cancel the access operation corresponding to the target data, the Virtiofs of the virtual machine kernel can request the Virtiofs Daemon (daemon process) to delete the target data through the corresponding FUSE command. The binding between the mapping block regions corresponding to the target data, cancel all EPT mappings corresponding to the target data, release the address space corresponding to the target data, and delete the file description corresponding to the target data.

FIG. 5 is a schematic diagram of data processing according to an exemplary embodiment of the present disclosure. As shown in FIG. 5 , thick lines represent data interaction during data processing, and thin lines represent control interaction during data processing. The shared data information is stored in the shared mapping space, and the virtual machine can send a request to the virtual machine monitor through the Virtiofs Daemon (daemon process) to create the shared data information in the shared mapping space and create the corresponding EPT mapping, so that The virtual machine can directly send a data processing request to the host kernel through the shared mapping space, and after the host processes the data processing request, the processing result can be sent to the virtual machine through the shared mapping space.

Using the above method, by mapping the address mapping table, pending queue and completion queue on the host in the virtual machine kernel, the data request message of the virtual machine can be directly submitted to the kernel of the host by iouring. The host's Virtiofs Daemon (daemon process) performs the transfer, and the host's kernel can directly obtain the data processing request sent by the virtual machine. In this way, additional system call overhead can be avoided, thereby improving the efficiency of virtual machine data processing.

FIG. 6 is a block diagram of a data processing apparatus according to an exemplary embodiment of the present disclosure. As shown in FIG. 6 , the apparatus may include:

The data request message receiving module 601 is used for receiving a data request message triggered by a user through a virtual machine, and the data request message is used for requesting to process target data on the host machine running the virtual machine;

The shared data information determination module 602 is configured to determine the shared data information corresponding to the target data according to the data request message, the shared data information includes a shared queue, and the shared queue is used for direct communication between the virtual machine and the kernel of the host machine. data interaction;

The data processing module 603 is configured to process the target data through the kernel of the host according to the data request message and the shared queue.

Optionally, the shared data information further includes an address mapping table. FIG. 7 is a block diagram of a second data processing apparatus according to an exemplary embodiment of the present disclosure. As shown in FIG. 7 , the apparatus further includes:

The virtual address determination module 604 is configured to determine the virtual address of the host machine corresponding to the physical address of the virtual machine according to the address mapping table; the address mapping table includes the difference between the physical address of the virtual machine and the virtual address of the host machine. Correspondence;

The data processing module 603 is also used for:

The target data is processed by the kernel of the host according to the virtual address, the data request message and the shared queue.

Optionally, the shared data information is stored in a shared mapping space, and both the virtual machine and the host can access the shared mapping space; FIG. 8 shows a third data processing apparatus according to an exemplary embodiment of the present disclosure. The block diagram, as shown in Figure 8, the device also includes:

A shared queue determination module 605, configured to determine whether there is a shared queue corresponding to the target data in the shared mapping space;

The shared data information determining module 602 is further configured to:

When it is determined that there is a shared queue corresponding to the target data in the shared mapping space, the shared data information corresponding to the target data is determined according to the data request message.

Optionally, the shared mapping space includes multiple mapping block regions. FIG. 9 is a block diagram of a fourth data processing apparatus according to an exemplary embodiment of the present disclosure. As shown in FIG. 9 , the apparatus further includes:

The mapping block region determining module 606 is used to determine the mapping block region corresponding to the target data from the shared mapping space when it is determined that the shared queue corresponding to the target data does not exist in the shared mapping space;

an initialization module 607, for initializing the mapping block area;

A shared queue creation module 608, configured to create a shared queue corresponding to the target data in the mapping block area.

Optionally, FIG. 10 is a block diagram of a fifth data processing apparatus according to an exemplary embodiment of the present disclosure. As shown in FIG. 10 , the apparatus further includes:

The adding module 609 is configured to add the target data and the shared queue corresponding to the target data to a preset queue association relationship, where the preset queue association relationship includes correspondence between different data and shared queues.

Optionally, the shared queue includes a queue to be processed; the data processing module 604 is further configured to: determine a shared data request message corresponding to the data request message according to a preset data format;

send the shared data request message to the pending queue;

Extract the shared data request message from the pending queue through the host;

According to the virtual address and the shared data request message, the target data is processed through the kernel of the host.

Optionally, the shared data information further includes a completion queue. FIG. 11 is a block diagram of a sixth data processing apparatus according to an exemplary embodiment of the present disclosure. As shown in FIG. 11 , the apparatus further includes:

The result sending module 610 is used to send the processing result to the completion queue after processing the target data through the kernel of the host;

The result extraction module 611 is configured to extract the processing result corresponding to the target data from the completion queue through the virtual machine.

Optionally, the mapping block area includes a notification area; the apparatus further includes:

a notification module, configured to send a data processing request message to the host through the notification area;

The data processing module 604 is also used for:

After the host computer receives the data processing request message, it extracts the shared data request message from the pending queue.

Through the above device, the virtual machine and the host machine can exchange data by sharing data information, and there is no need to transfer through the Virtiofs Daemon (daemon process) of the host machine. The kernel of the host machine can directly obtain the data processing request sent by the virtual machine. In this way, it is possible to Avoid extra system call overhead, thereby improving the efficiency of virtual machine data processing.

Regarding the apparatus in the above-mentioned embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be described in detail here.

Referring next to FIG. 12 , it shows a schematic structural diagram of an electronic device 1200 suitable for implementing an embodiment of the present disclosure. Terminal devices in the embodiments of the present disclosure may include, but are not limited to, such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablets), PMPs (portable multimedia players), vehicle-mounted terminals (eg, mobile terminals such as in-vehicle navigation terminals), etc., and stationary terminals such as digital TVs, desktop computers, and the like. The electronic device shown in FIG. 12 is only an example, and should not impose any limitation on the function and scope of use of the embodiments of the present disclosure.

As shown in FIG. 12, an electronic device 1200 may include a processing device (eg, a central processing unit, a graphics processor, etc.) 1201 that may be loaded into random access according to a program stored in a read only memory (ROM) 1202 or from a storage device 1208 Various appropriate actions and processes are executed by the programs in the memory (RAM) 1203 . In the RAM 1203, various programs and data necessary for the operation of the electronic device 1200 are also stored. The processing device 1201 , the ROM 1202 , and the RAM 1203 are connected to each other through a bus 1204 . An input/output (I/O) interface 1205 is also connected to bus 1204 .

Typically, the following devices may be connected to the I/O interface 1205: input devices 1206 including, for example, a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; including, for example, a liquid crystal display (LCD), speakers, vibration An output device 1207 of a computer, etc.; a storage device 1208 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1209. Communication means 1209 may allow electronic device 1200 to communicate wirelessly or by wire with other devices to exchange data. Although FIG. 12 shows an electronic device 1200 having various means, it should be understood that not all of the illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.

In particular, according to embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a non-transitory computer readable medium, the computer program containing program code for performing the method illustrated in the flowchart. In such an embodiment, the computer program may be downloaded and installed from the network via the communication device 1209 , or from the storage device 1208 , or from the ROM 1202 . When the computer program is executed by the processing apparatus 1201, the above-mentioned functions defined in the methods of the embodiments of the present disclosure are executed.

It should be noted that the computer-readable medium mentioned above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the above two. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or a combination of any of the above. More specific examples of computer readable storage media may include, but are not limited to, electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable Programmable read only memory (EPROM or flash memory), optical fiber, portable compact disk read only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above. In this disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In the present disclosure, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with computer-readable program code embodied thereon. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device . Program code embodied on a computer readable medium may be transmitted using any suitable medium including, but not limited to, electrical wire, optical fiber cable, RF (radio frequency), etc., or any suitable combination of the foregoing.

In some embodiments, the server can communicate using any currently known or future developed network protocol, such as HTTP (HyperText Transfer Protocol), and can communicate with digital data in any form or medium (eg, , communication network) interconnection. Examples of communication networks include local area networks ("LAN"), wide area networks ("WAN"), the Internet (eg, the Internet), and peer-to-peer networks (eg, ad hoc peer-to-peer networks), as well as any currently known or future development network of.

The above-mentioned computer-readable medium may be included in the above-mentioned electronic device; or may exist alone without being assembled into the electronic device.

The above-mentioned computer-readable medium carries one or more programs, and when the above-mentioned one or more programs are executed by the electronic device, the electronic device is made to: receive a data request message triggered by the user through the virtual machine, and the data request message is used for request processing of target data on the host running the virtual machine; according to the data request message, determine shared data information corresponding to the target data, where the shared data information includes a shared queue, and the shared queue is used for the Data interaction is directly performed between the virtual machine and the host; the target data is processed through the kernel of the host according to the data request message and the shared queue.

Computer program code for performing operations of the present disclosure may be written in one or more programming languages, including but not limited to object-oriented programming languages—such as Java, Smalltalk, C++, and This includes conventional procedural programming languages - such as the "C" language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer, or entirely on the remote computer or server. Where a remote computer is involved, the remote computer may be connected to the user's computer through any kind of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (eg, using an Internet service provider to via Internet connection).

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code that contains one or more logical functions for implementing the specified functions executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It is also noted that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented in dedicated hardware-based systems that perform the specified functions or operations , or can be implemented in a combination of dedicated hardware and computer instructions.

The modules involved in the embodiments of the present disclosure may be implemented in software or hardware. Wherein, the name of the module does not constitute a limitation of the module itself under certain circumstances. For example, the data request message receiving module can also be described as "receiving a data request message triggered by a user through a virtual machine, and the data request message is A module for requesting processing of target data on a host machine running the virtual machine".

The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), Systems on Chips (SOCs), Complex Programmable Logical Devices (CPLDs) and more.

In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in connection with the instruction execution system, apparatus or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media would include one or more wire-based electrical connections, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), fiber optics, compact disk read only memory (CD-ROM), optical storage, magnetic storage, or any suitable combination of the foregoing.

According to one or more embodiments of the present disclosure, Example 1 provides a data processing method, the method comprising: receiving a data request message triggered by a user through a virtual machine, where the data request message is used to request processing to run the virtual machine target data on the host of the host computer; according to the data request message, determine the shared data information corresponding to the target data, the shared data information includes a shared queue, and the shared queue is used for the virtual machine and the host Data interaction is directly performed between hosts; the target data is processed through the kernel of the host according to the data request message and the shared queue.

According to one or more embodiments of the present disclosure, Example 2 provides the method of Example 1, the shared data information further includes an address mapping table, and in the data request message and the shared queue, through the sink Before the kernel of the host processes the target data, the method further includes:

Determine the virtual address of the host machine corresponding to the physical address of the virtual machine according to the address mapping table; the address mapping table includes the correspondence between the physical address of the virtual machine and the virtual address of the host machine ;

The processing of the target data through the kernel of the host computer according to the data request message and the shared queue includes:

The target data is processed by the kernel of the host according to the virtual address, the data request message and the shared queue.

According to one or more embodiments of the present disclosure, Example 3 provides the method of Example 2, the shared data information is stored in a shared mapping space, and both the virtual machine and the host machine can access the shared mapping space; Before determining the shared data information corresponding to the target data according to the data request message, the method further includes: determining whether there is a shared queue corresponding to the target data in the shared mapping space; The data request message, and determining the shared data information corresponding to the target data includes: in the case where it is determined that a shared queue corresponding to the target data exists in the shared mapping space, determining the target data according to the data request message corresponding to the shared data information.

According to one or more embodiments of the present disclosure, Example 4 provides the method of Example 3, the shared mapping space includes a plurality of mapping block regions, the method further comprising: determining that the shared mapping space does not exist in the shared mapping space In the case of a shared queue corresponding to target data, determine a map block area corresponding to the target data from the shared map space; initialize the map block area; create a shared queue corresponding to the target data in the map block area .

According to one or more embodiments of the present disclosure, Example 5 provides the method of Example 4, the method further comprising: adding the target data and a shared queue corresponding to the target data to a preset queue association relationship, the The preset queue association relationship includes the corresponding relationship between different data and shared queues.

According to one or more embodiments of the present disclosure, Example 6 provides the method of Example 4, the shared queue includes a queue to be processed; The processing of the target data by the kernel of the host computer includes: determining a shared data request message corresponding to the data request message according to a preset data format; sending the shared data request message to the queue to be processed; The host extracts the shared data request message from the queue to be processed; and processes the target data through the kernel of the host machine according to the virtual address and the shared data request message.

According to one or more embodiments of the present disclosure, Example 7 provides the method of Example 6, the shared data information further includes a completion queue, and the method further includes: after processing the target data through the kernel of the host machine, Send the processing result to the completion queue; and extract the processing result corresponding to the target data from the completion queue through the virtual machine.

According to one or more embodiments of the present disclosure, Example 8 provides the method of Example 6, wherein the map block area includes a notification area; in the process of extracting the shared data request from the pending queue by the host The method further includes: sending a data processing request message to the host through the notification area; extracting the shared data request message from the queue to be processed through the host includes: in the host After receiving the data processing request message, the host machine extracts the shared data request message from the queue to be processed.

According to one or more embodiments of the present disclosure, Example 9 provides a data processing apparatus, the apparatus includes: a data request message receiving module, configured to receive a data request message triggered by a user through a virtual machine, the data request message used for requesting to process target data on the host machine running the virtual machine; a shared data information determination module, configured to determine shared data information corresponding to the target data according to the data request message, where the shared data information includes shared data Queue, the shared queue is used for direct data interaction between the virtual machine and the kernel of the host; the data processing module is used to request the message and the shared queue according to the data, through the host's The kernel processes the target data.

According to one or more embodiments of the present disclosure, Example 10 provides the apparatus of Example 9, the shared data information further includes an address mapping table, and the apparatus further includes: a virtual address determination module configured to, according to the address mapping table , determine the virtual address of the host machine corresponding to the physical address of the virtual machine; the address mapping table includes the correspondence between the physical address of the virtual machine and the virtual address of the host machine; the data processing module , and is further used for: processing the target data through the kernel of the host according to the virtual address, the data request message and the shared queue.

According to one or more embodiments of the present disclosure, Example 11 provides the apparatus of Example 10, the shared data information is stored in a shared mapping space, and both the virtual machine and the host machine can access the shared mapping space; The apparatus further includes: a shared queue determination module, configured to determine whether a shared queue corresponding to the target data exists in the shared mapping space; the shared data information determination module is further configured to: determine whether the shared mapping space exists in the shared mapping space. In the case that the shared queue corresponding to the target data exists in the data, the shared data information corresponding to the target data is determined according to the data request message.

According to one or more embodiments of the present disclosure, Example 12 provides the apparatus of Example 11, the shared mapping space includes a plurality of mapping block regions, and the apparatus further includes: a mapping block region determining module for determining the In the case where the shared queue corresponding to the target data does not exist in the shared mapping space, the mapping block area corresponding to the target data is determined from the shared mapping space; an initialization module is used to initialize the mapping block area; the shared queue A creating module is configured to create a shared queue corresponding to the target data in the mapping block area.

According to one or more embodiments of the present disclosure, Example 13 provides the apparatus of Example 12, the apparatus further comprising: an adding module configured to add the target data and the shared queue corresponding to the target data to a preset queue An association relationship, the preset queue association relationship includes a corresponding relationship between different data and shared queues.

According to one or more embodiments of the present disclosure, Example 14 provides the apparatus of Example 12, the shared queue includes a queue to be processed; the data processing module is further configured to: determine the data request according to a preset data format the shared data request message corresponding to the message; send the shared data request message to the pending queue; extract the shared data request message from the pending queue through the host; The shared data request message is processed, and the target data is processed through the kernel of the host.

According to one or more embodiments of the present disclosure, Example 15 provides the apparatus of Example 14, the shared data information further includes a completion queue, the apparatus further includes: a result sending module for processing through the kernel of the host machine After the target data is obtained, the processing result is sent to the completion queue; a result extraction module is configured to extract the processing result corresponding to the target data from the completion queue through the virtual machine.

According to one or more embodiments of the present disclosure, Example 16 provides the apparatus of Example 14, the map block area includes a notification area; the apparatus further includes: a notification module configured to notify the host through the notification area Sending a data processing request message; the data processing module is further configured to: after the host computer receives the data processing request message, extract the shared data request message from the queue to be processed.

According to one or more embodiments of the present disclosure, Example 17 provides a computer-readable medium having stored thereon a computer program that, when executed by a processing apparatus, implements the steps of the method described in any one of Examples 1-8 .

According to one or more embodiments of the present disclosure, Example 18 provides an electronic device, comprising: a storage device on which a computer program is stored; and a processing device for executing the computer program in the storage device, to Implement the steps of the method of any of Examples 1-8.

The above description is merely a preferred embodiment of the present disclosure and an illustration of the technical principles employed. Those skilled in the art should understand that the scope of the disclosure involved in the present disclosure is not limited to the technical solutions formed by the specific combination of the above-mentioned technical features, and should also cover, without departing from the above-mentioned disclosed concept, the technical solutions formed by the above-mentioned technical features or Other technical solutions formed by any combination of its equivalent features. For example, a technical solution is formed by replacing the above features with the technical features disclosed in the present disclosure (but not limited to) with similar functions.

Additionally, although operations are depicted in a particular order, this should not be construed as requiring that the operations be performed in the particular order shown or in a sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, although the above discussion contains several implementation-specific details, these should not be construed as limitations on the scope of the present disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

Although the subject matter has been described in language specific to structural features and/or logical acts of method, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are merely example forms of implementing the claims. Regarding the apparatus in the above-mentioned embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be described in detail here.

Claims (11)

1. a data processing method, is characterized in that, described method comprises: receiving a data request message triggered by a user through a virtual machine, where the data request message is used to request to process target data on a host machine running the virtual machine; determining shared data information corresponding to the target data according to the data request message, where the shared data information includes a shared queue, and the shared queue is used for direct data interaction between the virtual machine and the host; The target data is processed through the kernel of the host according to the data request message and the shared queue. 2. The method according to claim 1, wherein the shared data information further comprises an address mapping table, and in the described data request message and the shared queue, processed by the kernel of the host machine. Before describing the target data, the method further includes: According to the address mapping table, the virtual address of the host machine corresponding to the physical address of the virtual machine is determined; the address mapping table includes the relationship between the physical address of the virtual machine and the virtual address of the host machine Correspondence; The processing of the target data through the kernel of the host computer according to the data request message and the shared queue includes: The target data is processed by the kernel of the host according to the virtual address, the data request message and the shared queue. 3. The method according to claim 2, wherein the shared data information is stored in a shared mapping space, and both the virtual machine and the host machine can access the shared mapping space; The data request message, before determining the shared data information corresponding to the target data, the method further includes: determining whether there is a shared queue corresponding to the target data in the shared mapping space; The determining, according to the data request message, the shared data information corresponding to the target data includes: When it is determined that there is a shared queue corresponding to the target data in the shared mapping space, the shared data information corresponding to the target data is determined according to the data request message. 4. The method according to claim 3, wherein the shared mapping space comprises a plurality of mapping block regions, and the method further comprises: In the case of determining that the shared queue corresponding to the target data does not exist in the shared mapping space, determine a mapping block area corresponding to the target data from the shared mapping space; initialize the map block area; A shared queue corresponding to the target data is created in the mapping block area. 5. The method according to claim 4, wherein the method further comprises: The target data and the shared queue corresponding to the target data are added to a preset queue association relationship, where the preset queue association relationship includes correspondence between different data and shared queues. 6. The method according to claim 4, wherein the shared queue comprises a queue to be processed; the virtual address, the data request message and the shared queue are processed through the kernel of the host machine Processing the target data includes: determining a shared data request message corresponding to the data request message according to a preset data format; sending the shared data request message to the pending queue; Extracting the shared data request message from the queue to be processed by the host; The target data is processed by the kernel of the host according to the virtual address and the shared data request message. 7. The method according to claim 6, wherein the shared data information further comprises a completion queue, the method further comprising: After the target data is processed by the kernel of the host, the processing result is sent to the completion queue; The processing result corresponding to the target data is extracted from the completion queue by the virtual machine. 8 . The method according to claim 6 , wherein the mapping block area includes a notification area; before extracting the shared data request message from the queue to be processed by the host, the Methods also include: Send a data processing request message to the host through the notification area; The extracting the shared data request message from the to-be-processed queue by the host includes: After the host computer receives the data processing request message, it extracts the shared data request message from the queue to be processed. 9. A data processing device, characterized in that the device comprises: a data request message receiving module, configured to receive a data request message triggered by a user through a virtual machine, where the data request message is used to request to process target data on the host machine running the virtual machine; A shared data information determination module, configured to determine the shared data information corresponding to the target data according to the data request message, where the shared data information includes a shared queue, and the shared queue is used for the virtual machine and the host machine Direct data interaction between the kernels; A data processing module, configured to process the target data through the kernel of the host according to the data request message and the shared queue. 10. A computer-readable medium on which a computer program is stored, characterized in that, when the program is executed by a processing device, the steps of the method according to any one of claims 1-8 are implemented. 11. An electronic device, characterized in that, comprising: a storage device having at least one computer program stored thereon; At least one processing device for executing the at least one computer program in the storage device to implement the steps of the method of any one of claims 1-8.

Images