Server data carrying method and device

By deploying the request message queue on the server host and recording the request queue information on the data processing device, the problem of low processing efficiency of the data processing device is solved, and more efficient data handling and processing is achieved.

CN118939186APending Publication Date: 2024-11-12SHANDONG YUNHAI GUOCHUANG CLOUD COMPUTING EQUIP IND INNOVATION CENT CO LTD
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202410939287.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-12
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

In the prior art, the data processing device needs to frequently analyze the data processing requests when processing server data and acquire data from the server host storage area, resulting in low handling efficiency and low processing efficiency.

Method used

Deploy the request message queue on the server host and record the request queue information on the data processing device. By detecting the data processing request, the initial data is stored in the request message queue, and the request queue information of the data processing device is updated to directly transport it from the queue and process data.

Benefits of technology

It reduces the difficulty of data handling by data processing equipment, improves data handling speed and processing efficiency, and enables data processing equipment to obtain data to be processed simpler and faster.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118939186A_ABST
    Figure CN118939186A_ABST
Patent Text Reader

Abstract

The invention provides a server data carrying method and device, a request message queue is deployed on a server host, request queue information of the request message queue is recorded on data processing equipment, and the method comprises the following steps: detecting a data processing request generated on the server host; when it is detected that the target data processing request is generated on the server host, storing initial data requested to be processed by the target data processing request into a current initial request message queue; and according to the target request queue information, updating initial request queue information currently stored on the data processing equipment into reference request queue information, wherein the data processing equipment is used for carrying data from the request message queue according to the recorded request queue information and processing the data. According to the method and the device, the problem that the processing efficiency of the server data processing request under the participation of the data processing equipment is relatively low is solved, and the effect of improving the processing efficiency of the server data processing request under the participation of the data processing equipment is achieved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present application relate to the computer field, and in particular, to a method and device for transporting server data. Background Art

[0002] The data processing device carries out data processing by moving the data stored in the server host and then moves the processed data back to the server to help the server host process the data processing request to realize the data processing function. After receiving the data processing request, the current data processing device needs to parse the data processing request and obtain the required data from the data storage location of the server host corresponding to the data processing request. Such operation requires that each data processing operation corresponding to each data processing request needs to parse the data processing request to obtain the data storage location and obtain the corresponding data from the data processing location. However, the way in which the data processing device accesses the host storage area to obtain data is difficult to operate and the operation takes a long time, which leads to the poor efficiency of the data processing device in moving the data of the server host, and the low efficiency of the data processing device in processing the data processing request, that is, the processing efficiency of the server data processing request with the participation of the data processing device is low. Summary of the invention

[0003] The embodiments of the present application provide a method and device for transporting server data, so as to at least solve the problem of low processing efficiency of server data processing requests with the participation of data processing equipment in the related art.

[0004] According to an embodiment of the present application, a method for transporting server data is provided, which is applied to a server host, wherein the server host is configured to allow connection to a data processing device, the data processing device is used to process server data for the server host, a request message queue is deployed on the server host, and request queue information of the request message queue is recorded on the data processing device, the method comprising:

[0005] Detecting a data processing request generated on the server host;

[0006] When it is detected that a target data processing request is generated on the server host, the initial data requested to be processed by the target data processing request is stored in a current initial request message queue to obtain a target request message queue;

[0007] According to the target request queue information corresponding to the target request message queue, the initial request queue information currently stored on the data processing device is updated to the reference request queue information, wherein the data processing device is used to move data from the request message queue according to the recorded request queue information and process the moved data.

[0008] In an exemplary embodiment, storing the initial data requested to be processed by the target data processing request in the current initial request message queue to obtain the target request message queue includes:

[0009] Extracting a processing instruction and a data address from the target data processing request, wherein the processing instruction is an instruction requested by the target data processing request for the data processing device to execute, and the data address is a storage address of data requested by the target data processing request for the data processing device to execute the processing instruction;

[0010] Reading the data at the data address from the data storage space deployed on the server host to obtain data to be processed;

[0011] The processing instructions and the data to be processed are packaged according to a target data format to obtain the initial data; and the initial data is stored at the end of the initial request message queue to obtain the target request message queue.

[0012] In an exemplary embodiment, the request message queue includes a plurality of data units having an arrangement order, and the initial request message queue further records a request header identifier and a request tail identifier, wherein the request header identifier is used to indicate a first data unit storing data in the plurality of data units, and the request tail identifier is used to indicate an end data unit storing data in the plurality of data units;

[0013] The storing the initial data to the tail of the initial request message queue to obtain the target request message queue includes:

[0014] Query the current request tail identifier to obtain the current end data unit;

[0015] Storing the initial data in a data unit next to the current end data unit among the multiple data units;

[0016] Move the current request tail marker to the next data unit.

[0017] In an exemplary embodiment, the request queue information includes a queue head position and a queue tail position, wherein the queue head position is used to indicate the position of the queue head in the request message queue where the data processing device does not perform data transfer, and the queue tail position is used to indicate the position of the queue tail in the request message queue where the data processing device does not perform data transfer;

[0018] The updating of the initial request queue information currently stored on the data processing device to the reference request queue information according to the target request queue information corresponding to the target request message queue includes:

[0019] Obtaining the target queue tail position corresponding to the target request message queue as the target request queue information;

[0020] The initial queue tail position currently recorded on the data processing device is updated to the target queue tail position, wherein the initial request queue information includes the initial queue tail position, and the data processing device is used to transfer data from the recorded queue head position for processing when the queue head position and the queue tail position are different and update the queue head position after transferring the data.

[0021] In an exemplary embodiment, a head position register and a tail position register are deployed on the data processing device, the head position register is used to store the head position of the queue, the tail position register is used to store the tail position of the queue, and the request message queue includes a plurality of data units having an arrangement order;

[0022] The obtaining the target queue tail position corresponding to the target request message queue as the target request queue information includes:

[0023] Acquire the tail identifier of the last data unit in which data is written from the multiple data units as the tail position of the target queue;

[0024] The updating of the initial queue tail position currently recorded on the data processing device to the target queue tail position includes:

[0025] The tail identifier is written into the tail position register, wherein the head position register stores the head address of the head data unit that is not being moved by the data processing device among the data units storing data included in the multiple data units, and the data processing device is used to move data from the data unit indicated by the head address currently stored in the head position register for processing when the content stored in the head position register is different from the content stored in the tail position register, and update the head position register after moving the data.

[0026] In an exemplary embodiment, a response message queue is also deployed on the server host, and response queue information of the response message queue is also recorded on the data processing device;

[0027] After the initial request queue information currently stored on the data processing device is updated to reference request queue information according to the target request queue information corresponding to the target request message queue, the method includes:

[0028] The target response data returned by the data processing device is extracted from the response message queue according to the response queue information, wherein the data processing device is used to move the processed response data to the response message queue and update the response queue information.

[0029] In an exemplary embodiment, the response queue information includes a response header position and a response tail position, wherein the response header position is used to indicate the position of the data header of the data not extracted by the server host in the response message queue, and the response tail position is used to indicate the position of the data tail of the data not extracted by the server host in the response message queue;

[0030] The response message queue includes a plurality of storage units having an arrangement order, and the response request message queue also records a response header identifier and a response tail identifier, wherein the response header identifier is used to indicate the first storage unit storing data in the plurality of storage units, and the response tail identifier is used to indicate the last storage unit storing data in the plurality of storage units;

[0031] The extracting the target response data returned by the data processing device from the response message queue according to the response queue information comprises:

[0032] Polling the response header identifier;

[0033] The target response data is extracted from the storage unit indicated by the response header identifier, and the response header identifier and the response header position are updated after the target response data is extracted, wherein the data processing device is used to store the response information obtained by data processing to the next storage unit of the storage unit corresponding to the response tail position and update the response tail position and the response tail identifier.

[0034] According to another embodiment of the present application, a server data transport device is provided, which is applied to a server host, wherein the server host is configured to allow connection to a data processing device, the data processing device is used to process server data for the server host, a request message queue is deployed on the server host, and request queue information of the request message queue is recorded on the data processing device, the device comprising:

[0035] A detection module, used for detecting a data processing request generated on the server host;

[0036] A storage module is used for storing the initial data requested to be processed by the target data processing request into the current initial request message queue when detecting that a target data processing request is generated on the server host, so as to obtain a target request message queue;

[0037] An update module is used to update the initial request queue information currently stored on the data processing device to reference request queue information according to the target request queue information corresponding to the target request message queue, wherein the data processing device is used to transfer data from the request message queue according to the recorded request queue information and process the transferred data.

[0038] According to another embodiment of the present application, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when run.

[0039] According to another embodiment of the present application, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0040] Through the present application, since a request message queue is deployed on a server host that allows connection to a data processing device, request queue information of the request message queue is recorded on a data processing device that processes server data for the server host, and a data processing request generated on the server host is detected. When a target data processing request is detected on the server host, the initial data requested for processing by the target data processing request is stored in the current initial request message queue to obtain a target request message queue. The initial request queue information currently stored on the data processing device is updated to reference request queue information according to the target request queue information corresponding to the target request message queue. The data processing device moves data from the request message queue according to the recorded request queue information and processes the moved data, that is, a request message queue is deployed on the server host to store data processing. The initial data requested for processing is requested, and the request message queue is updated when a target data processing request is detected on the server host. The request queue information in the data processing device that serves as the basis for data transfer is updated according to the updated request message queue. The data processing device can directly transfer data from the request queue and process the transferred data according to the recorded request queue information, without having to parse the data processing request and transfer the data to be processed from the server host storage area, thereby reducing the difficulty of data transfer in the data processing device and increasing the speed of data transfer. The data processing device can obtain the data to be processed more simply and quickly for data processing. Therefore, the problem of low processing efficiency of server data processing requests with the participation of data processing devices can be solved, thereby achieving the effect of improving the processing efficiency of server data processing requests with the participation of data processing devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1It is a hardware structure block diagram of a server device of a method for transferring server data in an embodiment of the present application;

[0042] Figure 2 is a flow chart of a method for transporting server data according to an embodiment of the present application;

[0043] Figure 3 is a schematic diagram of a process of writing a request message into a request queue according to an embodiment of the present application;

[0044] Figure 4 This is a schematic diagram of a process in which a response message is sent out of a response queue according to an embodiment of the present application;

[0045] Figure 5 This is a schematic diagram of the algorithm core workflow according to the embodiment of the present application. Figure 1 ;

[0046] Figure 6 This is a schematic diagram of the algorithm core workflow according to the embodiment of the present application. Figure 2 ;

[0047] Figure 7 It is a flow chart of a method for transferring data of a PCIe device based on a Linux operating system according to an embodiment of the present application;

[0048] Figure 8 It is a structural block diagram of a server data transport device according to an embodiment of the present application. DETAILED DESCRIPTION

[0049] The embodiments of the present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0050] It should be noted that the terms "first", "second", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0051] The method embodiments provided in the embodiments of the present application can be executed in a server device or a similar computing device. Taking running on a server device as an example, Figure 1 1 is a hardware structure block diagram of a server device of a method for transferring server data in an embodiment of the present application. Figure 1 As shown, the server device may include one or more ( Figure 1 Only one is shown in the figure) a processor 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data, wherein the above-mentioned server device may also include a transmission device 106 and an input / output device 108 for communication functions. It can be understood by those skilled in the art that Figure 1The structure shown is only for illustration and does not limit the structure of the above server device. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations are shown.

[0052] The memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the method for carrying server data in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, to implement the above method. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the server device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0053] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the server device. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, referred to as NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0054] In this embodiment, a method for transporting server data is provided, which is applied to a server host. The server host is configured to allow connection to a data processing device, the data processing device is used to process server data for the server host, a request message queue is deployed on the server host, and request queue information of the request message queue is recorded on the data processing device. Figure 2 is a flow chart of a method for transferring server data according to an embodiment of the present application. Figure 2 As shown, the process includes the following steps:

[0055] Step S202, detecting a data processing request generated on the server host;

[0056] Step S204, when it is detected that a target data processing request is generated on the server host, the initial data requested to be processed by the target data processing request is stored in the current initial request message queue to obtain a target request message queue;

[0057] Step S206, updates the initial request queue information currently stored on the data processing device to reference request queue information according to the target request queue information corresponding to the target request message queue, wherein the data processing device is used to move data from the request message queue according to the recorded request queue information and process the moved data.

[0058] Through the above steps, since a request message queue is deployed on the server host that allows connection to the data processing device, the request queue information of the request message queue is recorded on the data processing device that processes server data for the server host, and the data processing request generated on the server host is detected. When it is detected that a target data processing request is generated on the server host, the initial data requested to be processed by the target data processing request is stored in the current initial request message queue to obtain the target request message queue. The initial request queue information currently stored on the data processing device is updated to the reference request queue information according to the target request queue information corresponding to the target request message queue. The data processing device moves data from the request message queue according to the recorded request queue information and processes the moved data, that is, the request message queue is deployed on the server host to store data processing. The initial data requested for processing is requested, and the request message queue is updated when a target data processing request is detected on the server host. The request queue information in the data processing device that serves as the basis for data transfer is updated according to the updated request message queue. The data processing device can directly transfer data from the request queue and process the transferred data according to the recorded request queue information, without having to parse the data processing request and transfer the data to be processed from the server host storage area, thereby reducing the difficulty of data transfer in the data processing device and increasing the speed of data transfer. The data processing device can obtain the data to be processed more simply and quickly for data processing. Therefore, the problem of low processing efficiency of server data processing requests with the participation of data processing devices can be solved, thereby achieving the effect of improving the processing efficiency of server data processing requests with the participation of data processing devices.

[0059] Optionally, in an embodiment of the present application, the data processing device includes but is not limited to a PCIe device including a PCIe cryptographic card, and the external data processing device can help the server host process data processing requests including data encryption requests.

[0060] Optionally, in an embodiment of the present application, a RING message queue is deployed in the driver layer of the server host, including but not limited to a request message queue and a response message queue. The request message queue includes but is not limited to storing source data for data processing requests, and the response message queue includes but is not limited to storing data processing results corresponding to the data processing requests.

[0061] Optionally, in an embodiment of the present application, including but not limited to deploying a first register group and a second register group on a data processing device, the first register group is used to record request queue information of the request message queue, and the second register group is used to record response queue information of the response message queue.

[0062] Optionally, in an embodiment of the present application, including but not limited to, the server host is simultaneously connected to multiple data processing devices, and the multiple data processing devices process multiple data processing requests accordingly. Multiple pairs of request message queues and response message queues are deployed in the server host corresponding to the multiple data processing devices, and the request queue information of the corresponding request message queue and the response queue information of the response message queue are recorded in each data processing device of the multiple data processing devices.

[0063] In the embodiment provided in step S202, detecting the data processing request generated on the server host includes but is not limited to detecting the request type of the data processing request, wherein the request type is used to indicate the data processing operation corresponding to the data processing request, and the data processing device has a corresponding relationship with the data processing operation; when it is detected that the request type of the data processing request is a target request type, it is determined that a target data processing request has been generated on the server host.

[0064] In the embodiment provided in step S204, the initial data requested to be processed by the target data processing request is stored in the current initial request message queue, and the target request message queue obtained includes but is not limited to the storage address information of the target data to be processed carried in the target data request, wherein the target data processing is completed by the data processing device, and the target data is stored in the current initial request message queue according to the storage address information to obtain the target request message queue.

[0065] Optionally, in an embodiment of the present application, the request message queue and the response message queue include but are not limited to M request message queue blocks and M response message queue blocks, each of the M request message queue blocks occupies the same size of storage space, each of the M response message queue blocks occupies the same size of storage space, the M request message queue blocks and the M response message queue blocks are numbered 1 to M, and the selection of the request message queue blocks and the response message queue blocks follows the rule of numbering from small to large, and the request message queue blocks or response message queue blocks with small numbers in the request message queue blocks or response message queue blocks that do not store data are used first, and the target The initial data requested to be processed by the data processing request is stored in the current initial request message queue, including but not limited to querying the smallest number N among the numbers of multiple request message queue blocks that are currently not in use in the request message queue, and storing the initial data requested to be processed by the target data processing request in the message queue block corresponding to number N; when it is detected that N=M, query the smallest number P among the numbers of multiple response message queue blocks that are currently not in use in the corresponding response message queue; when P=N-1, increase the corresponding numbers of the M request message queue blocks by M, so that the corresponding numbers of the M request message queue blocks are correspondingly modified from 1 to M to 1+M to M+M. In the above manner, the storage space corresponding to the fixed request message queue can be reused, avoiding the processed data from existing in the message queue for a long time, avoiding the waste of the storage space corresponding to the request message queue, and the server host can allocate less storage space for the request message queue, thereby improving the utilization rate of the storage space of the server host.

[0066] In the embodiment provided in step S206, the target request queue information includes but is not limited to recording the storage location of the initial data requested to be processed by the target data processing request in the target request message queue.

[0067] Optionally, in an embodiment of the present application, updating the initial request queue information currently stored on the data processing device to reference request queue information according to the target request queue information corresponding to the target request message queue includes but is not limited to sending a request queue information change request to the data processing device when the request message queue changes, wherein the request queue information change request is used to indicate that new data to be processed has been added to the request message queue, and the request queue information change request carries the target request queue information corresponding to the target request message queue; receiving the request queue information change request by the data processing device; and updating the currently stored initial request queue information to reference request queue information by the data processing device according to the request queue information change request when the data processing device is idle.

[0068] As an optional implementation manner, storing the initial data requested to be processed by the target data processing request in the current initial request message queue to obtain the target request message queue includes:

[0069] Extracting a processing instruction and a data address from the target data processing request, wherein the processing instruction is an instruction requested by the target data processing request for the data processing device to execute, and the data address is a storage address of data requested by the target data processing request for the data processing device to execute the processing instruction;

[0070] Reading the data at the data address from the data storage space deployed on the server host to obtain data to be processed;

[0071] The processing instructions and the data to be processed are packaged according to a target data format to obtain the initial data; and the initial data is stored at the end of the initial request message queue to obtain the target request message queue.

[0072] Optionally, in an embodiment of the present application, including but not limited to a case where a server host is connected to multiple data processing devices and the data processing devices can only execute one data processing scheme, the target data processing device is matched according to the processing instructions, and the initial data packaging process does not involve processing instructions. The data to be processed is directly packaged according to the target data format to obtain the initial data, and the initial data is then stored at the end of the initial request message queue corresponding to the target data processing device to obtain the target request message queue corresponding to the target data processing device.

[0073] Optionally, through the above steps, the data corresponding to the target data processing request is read from the data storage space, and the initial data including the above data is stored in the request message queue, which is equivalent to storing the data to be processed inside the host to a location where the data processing device can easily obtain it, thereby improving the efficiency of the data processing device in carrying the server host data.

[0074] As an optional implementation, the request message queue includes multiple data units having an arrangement order, and the initial request message queue also records a request header identifier and a request tail identifier, the request header identifier is used to indicate the first data unit storing data in the multiple data units, and the request tail identifier is used to indicate the last data unit storing data in the multiple data units;

[0075] The storing the initial data to the tail of the initial request message queue to obtain the target request message queue includes:

[0076] Query the current request tail identifier to obtain the current end data unit;

[0077] Storing the initial data in a data unit next to the current end data unit among the multiple data units;

[0078] Move the current request tail marker to the next data unit.

[0079] Optionally, in an embodiment of the present application, each data unit among the multiple data units includes but is not limited to corresponding to an equal data storage space size, and the corresponding data storage space size includes but is not limited to being agreed upon by the server host and the data processing device, including but not limited to determining the size of the data storage space corresponding to the data unit based on the amount of data that the data processing device can process at one time.

[0080] As an optional implementation, the request queue information includes a queue head position and a queue tail position, the queue head position is used to indicate the position of the queue head in the request message queue where the data processing device does not carry out data transfer, and the queue tail position is used to indicate the position of the queue tail in the request message queue where the data processing device does not carry out data transfer;

[0081] The updating of the initial request queue information currently stored on the data processing device to the reference request queue information according to the target request queue information corresponding to the target request message queue includes:

[0082] Obtaining the target queue tail position corresponding to the target request message queue as the target request queue information;

[0083] The initial queue tail position currently recorded on the data processing device is updated to the target queue tail position, wherein the initial request queue information includes the initial queue tail position, and the data processing device is used to transfer data from the recorded queue head position for processing when the queue head position and the queue tail position are different and update the queue head position after transferring the data.

[0084] Optionally, through the above steps, the data processing device can move data from the recorded queue head position for processing when the queue head position and the queue tail position are different, so that it can timely and accurately determine that there is data to be processed in the request message queue, thereby improving the processing efficiency of the data processing device on the server host data.

[0085] As an optional implementation, a head position register and a tail position register are deployed on the data processing device, the head position register is used to store the head position of the queue, the tail position register is used to store the tail position of the queue, and the request message queue includes a plurality of data units having an arrangement order;

[0086] The obtaining the target queue tail position corresponding to the target request message queue as the target request queue information includes:

[0087] Acquire the tail identifier of the last data unit in which data is written from the multiple data units as the tail position of the target queue;

[0088] The updating of the initial queue tail position currently recorded on the data processing device to the target queue tail position includes:

[0089] The tail identifier is written into the tail position register, wherein the head position register stores the head address of the head data unit that is not being moved by the data processing device among the data units storing data included in the multiple data units, and the data processing device is used to move data from the data unit indicated by the head address currently stored in the head position register for processing when the content stored in the head position register is different from the content stored in the tail position register, and update the head position register after moving the data.

[0090] Optionally, through the above steps, through the cooperation of the head position register, the tail position register and the tail identifier, the pending data corresponding to the next pending data processing request in the request message queue is accurately extracted, thereby improving the processing efficiency of the data processing device on the server host data.

[0091] As an optional implementation manner, a response message queue is also deployed on the server host, and response queue information of the response message queue is also recorded on the data processing device;

[0092] After the initial request queue information currently stored on the data processing device is updated to reference request queue information according to the target request queue information corresponding to the target request message queue, the method includes:

[0093] The target response data returned by the data processing device is extracted from the response message queue according to the response queue information, wherein the data processing device is used to move the processed response data to the response message queue and update the response queue information.

[0094] Optionally, in an embodiment of the present application, the response message queue includes but is not limited to corresponding to the request message queue. By deploying the request message queue and the response message queue in the server host, the request queue information of the request message queue and the response queue information of the response message queue are recorded on the data processing device, the data to be processed is written into the request message queue on the server host, the data to be processed is obtained on the data processing device according to the request queue information of the request message queue, the data to be processed is processed on the data processing device to obtain the processing result data, the processing result data is written into the response message queue on the data processing device according to the response queue information of the response message queue, and the server host polls the response message queue to obtain the processing result data.

[0095] As an optional implementation, the response queue information includes a response header position and a response tail position, wherein the response header position is used to indicate the position of a data header of the data not extracted by the server host in the response message queue, and the response tail position is used to indicate the position of a data tail of the data not extracted by the server host in the response message queue;

[0096] The response message queue includes a plurality of storage units having an arrangement order, and the response request message queue also records a response header identifier and a response tail identifier, wherein the response header identifier is used to indicate the first storage unit storing data in the plurality of storage units, and the response tail identifier is used to indicate the last storage unit storing data in the plurality of storage units;

[0097] The extracting the target response data returned by the data processing device from the response message queue according to the response queue information comprises:

[0098] Polling the response header identifier;

[0099] The target response data is extracted from the storage unit indicated by the response header identifier, and the response header identifier and the response header position are updated after the target response data is extracted, wherein the data processing device is used to store the response information obtained by data processing to the next storage unit of the storage unit corresponding to the response tail position and update the response tail position and the response tail identifier.

[0100] Optionally, in an embodiment of the present application, including but not limited to polling the response header identifier through a poll mechanism, polling the response header identifier within a target time, and updating the response header identifier and the response header position when the target response data is extracted or the polling continues for the target time.

[0101] Optionally, through the above steps, the response header identifier is polled and the target response data is extracted from the storage unit indicated by the response header identifier. The target response data is stored in the response message queue accordingly, which makes it convenient for the data processing device to return the processed data to the server host, and also makes it convenient for the server host to extract the target response data to obtain the processing result of the target data processing request, thereby improving the processing efficiency of the server data processing request with the participation of the data processing device.

[0102] As an optional implementation, the present application also provides a data transfer method for a PCIe device (i.e., a data processing device) under a Linux system. Based on the Linux operating system, a data encryption and decryption operation and transfer method is proposed. By combining the driver's message queue with the algorithm core hardware encryption, rapid data transfer between the host (i.e., the server host) and the PCIe cryptographic card is achieved, thereby improving the cryptographic operation rate and communication efficiency.

[0103] Combined with the overall structure of the Linux system, the content involved in this application is divided into two parts, the application part of the user space and the OS kernel part of the kernel space, wherein the OS kernel includes a driver. More specifically, in the solution provided by this application, it mainly includes the application and driver shown below (corresponding to the server host), and the algorithm core implemented by the chip hardware circuit (corresponding to the data processing device).

[0104] 1. Application:

[0105] The upper-level user program is mainly responsible for the business logic conversion between data encryption and decryption, as well as the assembly and parsing of the message body.

[0106] 2. Driver:

[0107] Driver: runs under the kernel OS and serves as a transmission medium between the application program and the hardware circuit. In this application, it mainly involves the request message queue and the response message queue, as well as the message processing thread.

[0108] The RING message queue is a message queue that exists in the driver layer. It is the medium for transmitting messages between the application layer and the algorithm core. It is divided into a request queue (i.e., a request message queue) and a response queue (i.e., a response message queue). It carries source data (i.e., initial data) and operation results (i.e., response data). When the driver is initialized, it applies for DMA space for the RING queue and fills in the initial parameters. The main members of the RING message queue are:

[0109] req_addr: request message queue virtual pointer first address;

[0110] req_base: request message queue DMA physical pointer first address;

[0111] req_head (i.e. request header identifier): request message queue message header identifier;

[0112] req_tail (i.e. request tail mark): request message queue message tail mark;

[0113] resp_addr: the first address of the virtual pointer of the response message queue;

[0114] resp_base: the first address of the DMA physical pointer of the response message queue;

[0115] resp_head (i.e. response header identifier): response message queue message header identifier;

[0116] resp_tail (i.e. response tail identifier): the tail identifier of the response message queue.

[0117] In addition, the driver in the embodiment of the present application is also responsible for the following tasks:

[0118] (1) Create a message processing thread;

[0119] When the driver is initialized, a message processing thread is created. The thread creates a communication message body, which contains a request message queue pointer. The pointer points to the corresponding message body queue first address req_addr. The virtual address actually corresponds to the DMA physical address req_base. The same is true for the response message queue.

[0120] (2) The request message is written into the request queue;

[0121] Figure 3 is a schematic diagram of a process of writing a request message into a request queue according to an embodiment of the present application, such as Figure 3 As shown, the application layer (ie, user) accesses the kernel through the character device (ie, APP), assembles a request message, and passes it to the kernel layer (ie, kernel) through the ioctl system call. The driver writes the message into the request queue (reqenqueue) according to the request message tail req_tail.

[0122] (3) The response message is sent out of the response queue;

[0123] Figure 4 Schematic diagram of the process of the response message out of the response queue according to the embodiment of the present application. Figure 4As shown, after the application layer (i.e. user) initializes (i.e. init) the message processing thread (i.e. thread), the message processing thread executes cyclically, and the kernel (i.e. kernel) polls the response message queue message head resp_head through the while(1) mode of the polling mechanism. When the response message is found to exist, the message is taken out of the queue (i.e. resp dequeue) for processing.

[0124] The above is a brief design idea for the driver program. It will not be introduced in detail here. This application mainly introduces how the driver bottom layer realizes the data transfer operation of the algorithm core hardware circuit by reading and writing registers.

[0125] 3. Algorithm core:

[0126] Algorithm core: It is implemented by the hardware circuit of the PCIe cryptographic operation chip, and triggers data transmission and cryptographic operations by interacting with the driver to fill each register. The algorithm core mainly contains several key registers, which are used to store data and communicate messages with the driver. The registers are mapped through the Linux DMA Mapping mechanism and correspond to the registers in the PCIe device. The following is an introduction to the registers:

[0127] (1) TX register group (corresponding to record request queue information):

[0128] TX_BASE_ADDR_ADDR1 = the lower 32 bits of the physical address of the first address of the RING request queue;

[0129] TX_BASE_ADDR_ADDR2 = the high 32 bits of the physical address of the first address of the RING request queue;

[0130] TX_RING_SIZE_ADDR = queue length of RING request queue;

[0131] TX_HEAD_ADDR = 0 (pointer, pointing to the queue head, initial value is 0);

[0132] TX_TAIL_ADDR = 0 (pointer, pointing to the tail of the queue, initial value is 0);

[0133] TX_RING_STATUS_ADDR=1 (status register, set to 1 to enter working state).

[0134] Figure 5 This is a schematic diagram of the algorithm core workflow according to the embodiment of the present application. Figure 1 ,like Figure 5As shown, in the initial state, the pointer TX_TAIL = TX_HEAD = 0, and both point to the same position. When the driver receives a request message, the position of the current message body in the message queue, req_tail, is assigned to the TX_TAIL register (i.e., the head position register, corresponding to the queue head position) to trigger the algorithm core operation. The algorithm core will offset based on the value of the TX_HEAD register (i.e., the tail position register, corresponding to the queue tail position) on the basis of TX_BASE_ADDR_ADDR, find the data at the corresponding position of TX_HEAD, i.e., the current request message, find the corresponding DMA physical address, and move the data at the address. After the transfer is completed, the algorithm core will automatically move the value in the TX_HEAD register backward by one unit through the pre-constrained hardware design, without the need to specify the location of the message through the driver. At the same time, the driver flag is req_tail++. When the next message arrives, the driver will store the message at the DMA physical address corresponding to the position.

[0135] (2) RX register group (corresponding to recording response queue information):

[0136] RX_BASE_ADDR_ADDR1 = the lower 32 bits of the physical address of the first address of the RING response queue;

[0137] RX_BASE_ADDR_ADDR2 = the high 32 bits of the physical address of the first address of the RING response queue;

[0138] RX_RING_SIZE_ADDR = queue length of RING response queue;

[0139] RX_HEAD_ADDR = 0 (pointer, pointing to the queue head, initial value is 0);

[0140] RX_TAIL_ADDR = 0 (pointer, pointing to the tail of the queue, initial value is 0);

[0141] RX_RING_STATUS_ADDR=1 (status register, set to 1 to enter working state).

[0142] Figure 6 This is a schematic diagram of the algorithm core workflow according to the embodiment of the present application. Figure 2 ,like Figure 6As shown, in the initial state, RX_TAIL = RX_HEAD = 0. After the algorithm core completes an operation, it will fill the data in the physical address corresponding to the RX_TAIL register (corresponding to the response tail position), and then automatically move RX_TAIL to the next unit. The message processing thread polls the message status of the resp_head position through the poll mechanism. At this time, the driver's flag resp_head and the algorithm core pointer RX_HEAD are both 0. After fetching the message, the driver will resp_head++, which corresponds to the position of the next message fetch.

[0143] Figure 7 1 is a flow chart of a method for transferring data of a PCIe device based on a Linux operating system according to an embodiment of the present application. Figure 7As shown, the application layer initiates a request command according to business needs, packages the original data according to the agreed format, and passes it to the driver in the kernel through the ioctl system call. The driver parses the message packet according to the format, obtains the original data, and packages the original data again according to the driver layer rules to encapsulate it into a request message. When a new message request arrives, the driver inserts it into the tail req_tail of the request queue (corresponding to the TX register group), and assigns the current req_tail to the register TX_TAIL, triggering the calculation core to fetch the message. The calculation core obtains the physical address of the request message based on the value of the TX_HEAD register and the offset TX_HEAD based on TX_BASE_ADDR. The algorithm core contains the SM1 national secret algorithm hardware encryption circuit. When the algorithm core is triggered once, the original data is moved from the address corresponding to TX_HEAD. At this time, TX_HEAD slides back one unit from the self-increment. After the transfer is completed, the driver flags req_tail++. When the next message arrives, it is inserted into the new req_tail position of the RING request queue, and the above logic is triggered again. After the hardware encryption circuit completes the SM1 cryptographic operation, the algorithm core places the encrypted data at the tail RX_TAIL position of the response queue (corresponding to the RX register group). For the driver, this is a response message. The message processing thread POLL polls the message at resp_head within the target time. After taking out the message or after the fixed polling time arrives, resp_head++ is added. At this time, the algorithm core automatically maintains RX_TAIL and moves it to the next unit. In the whole process, req_tail and TX_TAIL, req_head and TX_HEAD, resp_tail and RX_TAIL, resp_head and RX_HEAD are synchronized with each other. The TX and RX pointers are automatically maintained by the algorithm core, and the req and resp flags are logically controlled by the driver. After being processed by the algorithm core, the driver returns the response message body to the driver layer, and then the driver layer returns it to the application layer, completing a complete data operation process.

[0144] Through the above operations, the RING queue in the driver is divided into two message queues, request and response, to process messages with the algorithm core, ensuring that each message interaction is independent, and the blocking of one message will not affect the processing of the next message, thereby improving the message processing efficiency. That is, through the driver's request queue and request flag, response queue and response flag, and the pointer in the algorithm core hardware circuit one-to-one correspondence, the data interaction between the driver layer and the algorithm hardware layer is realized. In the entire message processing mechanism, the blocking of a certain message will not affect the processing of other messages, thereby improving the data handling and operation speed in cryptographic operations, improving the smoothness of product operation, and enhancing the market competitiveness of products.

[0145] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0146] In this embodiment, a server data handling device is also provided, which is applied to a server host, and the server host is configured to allow connection to a data processing device, and the data processing device is used to process server data for the server host. A request message queue is deployed on the server host, and the request queue information of the request message queue is recorded on the data processing device. The device is used to implement the above-mentioned embodiments and preferred implementation modes, and those that have been explained will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware for a predetermined function. Although the device described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0147] Figure 8 is a structural block diagram of a server data transfer device according to an embodiment of the present application, such as Figure 8 As shown, the device comprises:

[0148] A detection module 802, used to detect a data processing request generated on the server host;

[0149] The storage module 804 is used to store the initial data requested to be processed by the target data processing request into the current initial request message queue when detecting that a target data processing request is generated on the server host, so as to obtain a target request message queue;

[0150] The update module 806 is used to update the initial request queue information currently stored on the data processing device to the reference request queue information according to the target request queue information corresponding to the target request message queue, wherein the data processing device is used to move data from the request message queue according to the recorded request queue information and process the moved data.

[0151] Through the above steps, since a request message queue is deployed on the server host that allows connection to the data processing device, the request queue information of the request message queue is recorded on the data processing device that processes server data for the server host, and the data processing request generated on the server host is detected. When it is detected that a target data processing request is generated on the server host, the initial data requested to be processed by the target data processing request is stored in the current initial request message queue to obtain the target request message queue. The initial request queue information currently stored on the data processing device is updated to the reference request queue information according to the target request queue information corresponding to the target request message queue. The data processing device moves data from the request message queue according to the recorded request queue information and processes the moved data, that is, the request message queue is deployed on the server host to store data processing. The initial data requested for processing is requested, and the request message queue is updated when a target data processing request is detected on the server host. The request queue information in the data processing device that serves as the basis for data transfer is updated according to the updated request message queue. The data processing device can directly transfer data from the request queue and process the transferred data according to the recorded request queue information, without having to parse the data processing request and transfer the data to be processed from the server host storage area, thereby reducing the difficulty of data transfer in the data processing device and increasing the speed of data transfer. The data processing device can obtain the data to be processed more simply and quickly for data processing. Therefore, the problem of low processing efficiency of server data processing requests with the participation of data processing devices can be solved, thereby achieving the effect of improving the processing efficiency of server data processing requests with the participation of data processing devices.

[0152] As an optional implementation, the storage module includes:

[0153] a first extraction unit, configured to extract a processing instruction and a data address from the target data processing request, wherein the processing instruction is an instruction requested by the target data processing request for the data processing device to execute, and the data address is a storage address of data requested by the target data processing request for the data processing device to execute the processing instruction;

[0154] A reading unit, used for reading the data at the data address from the data storage space deployed on the server host to obtain data to be processed;

[0155] A packing unit, used for packing the processing instruction and the data to be processed according to a target data format to obtain the initial data;

[0156] The storage unit is used to store the initial data at the end of the initial request message queue to obtain the target request message queue.

[0157] As an optional implementation, the request message queue includes multiple data units having an arrangement order, and the initial request message queue also records a request header identifier and a request tail identifier, the request header identifier is used to indicate the first data unit storing data in the multiple data units, and the request tail identifier is used to indicate the last data unit storing data in the multiple data units;

[0158] The storage unit is further used for:

[0159] Query the current request tail identifier to obtain the current end data unit;

[0160] Storing the initial data in a data unit next to the current end data unit among the multiple data units;

[0161] Move the current request tail marker to the next data unit.

[0162] As an optional implementation, the request queue information includes a queue head position and a queue tail position, the queue head position is used to indicate the position of the queue head in the request message queue where the data processing device does not carry out data transfer, and the queue tail position is used to indicate the position of the queue tail in the request message queue where the data processing device does not carry out data transfer;

[0163] The update module comprises:

[0164] An acquiring unit, configured to acquire a target queue tail position corresponding to the target request message queue as the target request queue information;

[0165] An updating unit is used to update the initial queue tail position currently recorded on the data processing device to the target queue tail position, wherein the initial request queue information includes the initial queue tail position, and the data processing device is used to transfer data from the recorded queue head position for processing when the queue head position and the queue tail position are different and update the queue head position after transferring the data.

[0166] As an optional implementation, a head position register and a tail position register are deployed on the data processing device, the head position register is used to store the head position of the queue, the tail position register is used to store the tail position of the queue, and the request message queue includes a plurality of data units having an arrangement order;

[0167] The acquisition unit is further used for:

[0168] Acquire the tail identifier of the last data unit in which data is written from the multiple data units as the tail position of the target queue;

[0169] The updating unit is further used for:

[0170] The tail identifier is written into the tail position register, wherein the head position register stores the head address of the head data unit that is not being moved by the data processing device among the data units storing data included in the multiple data units, and the data processing device is used to move data from the data unit indicated by the head address currently stored in the head position register for processing when the content stored in the head position register is different from the content stored in the tail position register, and update the head position register after moving the data.

[0171] As an optional implementation manner, a response message queue is also deployed on the server host, and response queue information of the response message queue is also recorded on the data processing device;

[0172] The device also includes:

[0173] An extraction module is used to extract the target response data returned by the data processing device from the response message queue according to the response queue information, wherein the data processing device is used to move the processed response data to the response message queue and update the response queue information.

[0174] As an optional implementation, the response queue information includes a response header position and a response tail position, wherein the response header position is used to indicate the position of a data header of the data not extracted by the server host in the response message queue, and the response tail position is used to indicate the position of a data tail of the data not extracted by the server host in the response message queue;

[0175] The response message queue includes a plurality of storage units having an arrangement order, and the response request message queue also records a response header identifier and a response tail identifier, wherein the response header identifier is used to indicate the first storage unit storing data in the plurality of storage units, and the response tail identifier is used to indicate the last storage unit storing data in the plurality of storage units;

[0176] The extraction module comprises:

[0177] A polling unit, used for polling the response header identifier;

[0178] A second extraction unit is used to extract the target response data from the storage unit indicated by the response header identifier, and to update the response header identifier and the response header position after the target response data is extracted, wherein the data processing device is used to store the response information obtained by data processing to the next storage unit of the storage unit corresponding to the response tail position and to update the response tail position and the response tail identifier.

[0179] It should be noted that the above modules can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.

[0180] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when running.

[0181] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0182] An embodiment of the present application further provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0183] In an exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0184] An embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps in any one of the above method embodiments are implemented.

[0185] An embodiment of the present application further provides another computer program product, including a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in any of the above method embodiments are implemented.

[0186] An embodiment of the present application also provides a computer program, which includes computer instructions, which are stored in a computer-readable storage medium; a processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the steps in any one of the above method embodiments.

[0187] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail herein.

[0188] Obviously, those skilled in the art should understand that the above modules or steps of the present application can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order from that herein, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present application is not limited to any specific combination of hardware and software.

[0189] The above description is only the preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the principles of the present application shall be included in the protection scope of the present application.

Claims

1. A method for transporting server data. It is characterized in that Applied to a server host, the server host is configured to allow connection to a data processing device, the data processing device is used to process server data for the server host, a request message queue is deployed on the server host, and request queue information of the request message queue is recorded on the data processing device, the method comprises: Detecting a data processing request generated on the server host; When it is detected that a target data processing request is generated on the server host, the initial data requested to be processed by the target data processing request is stored in a current initial request message queue to obtain a target request message queue; According to the target request queue information corresponding to the target request message queue, the initial request queue information currently stored on the data processing device is updated to the reference request queue information, wherein the data processing device is used to move data from the request message queue according to the recorded request queue information and process the moved data.

2. The method according to claim 1, It is characterized in that The storing of the initial data requested to be processed by the target data processing request into the current initial request message queue to obtain the target request message queue comprises: Extracting a processing instruction and a data address from the target data processing request, wherein the processing instruction is an instruction requested by the target data processing request for the data processing device to execute, and the data address is a storage address of data requested by the target data processing request for the data processing device to execute the processing instruction; Reading the data at the data address from the data storage space deployed on the server host to obtain data to be processed; Packing the processing instruction and the data to be processed according to the target data format to obtain the initial data; The initial data is stored at the end of the initial request message queue to obtain the target request message queue.

3. The method according to claim 2, It is characterized in that The request message queue includes a plurality of data units in an arrangement order, and the initial request message queue also records a request header identifier and a request tail identifier, wherein the request header identifier is used to indicate a first data unit storing data in the plurality of data units, and the request tail identifier is used to indicate an end data unit storing data in the plurality of data units; The storing the initial data to the tail of the initial request message queue to obtain the target request message queue includes: Query the current request tail identifier to obtain the current end data unit; Storing the initial data in a data unit next to the current end data unit among the multiple data units; Move the current request tail marker to the next data unit.

4. The method according to claim 1, It is characterized in that The request queue information includes a queue head position and a queue tail position, wherein the queue head position is used to indicate the position of the queue head where the data processing device does not carry out data transfer in the request message queue, and the queue tail position is used to indicate the position of the queue tail where the data processing device does not carry out data transfer in the request message queue; The updating of the initial request queue information currently stored on the data processing device to the reference request queue information according to the target request queue information corresponding to the target request message queue includes: Obtaining the target queue tail position corresponding to the target request message queue as the target request queue information; The initial queue tail position currently recorded on the data processing device is updated to the target queue tail position, wherein the initial request queue information includes the initial queue tail position, and the data processing device is used to transfer data from the recorded queue head position for processing when the queue head position and the queue tail position are different and update the queue head position after transferring the data.

5. The method according to claim 4, It is characterized in that A head position register and a tail position register are deployed on the data processing device, the head position register is used to store the head position of the queue, and the tail position register is used to store the tail position of the queue, and the request message queue includes a plurality of data units having an arrangement order; The obtaining the target queue tail position corresponding to the target request message queue as the target request queue information includes: Acquire the tail identifier of the last data unit in which data is written from the multiple data units as the tail position of the target queue; The updating of the initial queue tail position currently recorded on the data processing device to the target queue tail position includes: The tail identifier is written into the tail position register, wherein the head position register stores the head address of the head data unit that is not being moved by the data processing device among the data units storing data included in the multiple data units, and the data processing device is used to move data from the data unit indicated by the head address currently stored in the head position register for processing when the content stored in the head position register is different from the content stored in the tail position register, and update the head position register after moving the data.

6. The method according to claim 1, It is characterized in that A response message queue is also deployed on the server host, and response queue information of the response message queue is also recorded on the data processing device; After the initial request queue information currently stored on the data processing device is updated to reference request queue information according to the target request queue information corresponding to the target request message queue, the method includes: The target response data returned by the data processing device is extracted from the response message queue according to the response queue information, wherein the data processing device is used to move the processed response data to the response message queue and update the response queue information.

7. The method according to claim 6, It is characterized in that The response queue information includes a response header position and a response tail position, wherein the response header position is used to indicate the position of the data header of the data not extracted by the server host in the response message queue, and the response tail position is used to indicate the position of the data tail of the data not extracted by the server host in the response message queue; The response message queue includes a plurality of storage units having an arrangement order, and the response request message queue also records a response header identifier and a response tail identifier, wherein the response header identifier is used to indicate the first storage unit storing data in the plurality of storage units, and the response tail identifier is used to indicate the last storage unit storing data in the plurality of storage units; The extracting the target response data returned by the data processing device from the response message queue according to the response queue information comprises: Polling the response header identifier; The target response data is extracted from the storage unit indicated by the response header identifier, and the response header identifier and the response header position are updated after the target response data is extracted, wherein the data processing device is used to store the response information obtained by data processing to the next storage unit of the storage unit corresponding to the response tail position and update the response tail position and the response tail identifier.

8. A device for transporting server data, It is characterized in that Applied to a server host, the server host is configured to allow connection to a data processing device, the data processing device is used to process server data for the server host, a request message queue is deployed on the server host, and request queue information of the request message queue is recorded on the data processing device, the device comprises: A detection module, used for detecting a data processing request generated on the server host; A storage module is used for storing the initial data requested to be processed by the target data processing request into the current initial request message queue when detecting that a target data processing request is generated on the server host, so as to obtain a target request message queue; An update module is used to update the initial request queue information currently stored on the data processing device to reference request queue information according to the target request queue information corresponding to the target request message queue, wherein the data processing device is used to transfer data from the request message queue according to the recorded request queue information and process the transferred data.

9. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores a computer program, wherein the computer program implements the steps of the method described in any one of claims 1 to 7 when executed by a processor.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, It is characterized in that When the processor executes the computer program, the steps of the method described in any one of claims 1 to 7 are implemented.

Citation Information

Cited By

  • Data processing method based on SW CPU instruction set

    CN119341744A