Software and hardware collaborative message processing method and related device
Through the message processing method of software and hardware collaboration, the software processing layer is used to obtain topological network and device capability information, which solves the problem of insufficient resource consumption and flexibility caused by the hardware processing layer being cured in advance, and achieves richer transmission and maintenance capabilities.
Patent Information
- Application Number
- CN202310611906.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-26
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2043-05-26
AI Technical Summary
After the equipment deployment density increases, the prior art solidifies the topological network and equipment capabilities through the hardware processing layer in advance, resulting in high hardware resource consumption and inability to meet the transmission and equipment maintenance needs in different scenarios.
The message processing method of software and hardware collaboration is adopted to obtain topology network and device capability information through the software processing layer, flexibly change topology network and device capabilities, reduce hardware resource overhead, and meet the transmission needs of different scenarios.
Effectively save hardware resources, improve transmission flexibility and equipment maintenance capabilities, and meet diverse transmission needs.
Smart Images

Figure CN119030869A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to the field of cloud technology, and specifically to a software-hardware collaborative message processing method and related devices. Background Art
[0002] With the rapid development of cloud computing, major cloud vendors currently generally use data processing units (DPUs) to meet users' growing network and storage needs.
[0003] Currently, the hardware processing layer is mainly used in the market to pre-solidify the topology network and device capabilities of the device, so as to plan the configuration space of the device. After planning the configuration space, the hardware processing layer continues to respond to the transaction layer packet (TLP) message to respond to the read and write operations of the TLP message, and present the topology network of the device to the host side device. However, as the density of device deployment continues to increase, the current pre-solidification of the topology network and device capabilities of the device through the hardware processing layer will consume a large amount of hardware resources, and cannot meet the transmission requirements in different scenarios and the subsequent equipment maintenance. Summary of the invention
[0004] The embodiments of the present application provide a software-hardware collaborative message processing method and related devices, which can flexibly change the topology network and device capabilities, greatly reduce hardware resource overhead, provide richer maintainable capabilities, and meet the transmission requirements of different scenarios.
[0005] In the first aspect, an embodiment of the present application provides a method for processing a message in software-hardware collaboration. The message processing method is applied to a software-hardware collaborative device. In addition, the software-hardware collaborative device includes a software processing layer and a hardware processing layer. In the method, the configuration information and the configuration space read-write request sent by the host-side device are obtained through the software processing layer. The configuration information includes a topology network and capability information. The topology network is used to indicate the topological relationship between at least two transmission devices. The capability information is used to indicate the device capability of each transmission device in at least two transmission devices. The configuration space read-write request carries a transmission message, and the transmission message includes field information indicating the target device address to which the transmission message needs to reach; the software processing layer searches for the configuration space of the target device corresponding to the target device address based on the configuration information and field information, and the target device is any device in at least two transmission devices; in the configuration space of the target device, the software processing layer performs read-write operations on the transmission message; after the software processing layer completes the read-write operations on the transmission message, the hardware processing layer forwards the read-write response message corresponding to the configuration space read-write request to the host-side device, and the read-write response message includes the topology network and capability information.
[0006] In the second aspect, an embodiment of the present application provides a message processing method for software-hardware collaboration. The message processing method is applied to a host-side device. In this method, a configuration space read and write request is sent to a software-hardware collaborative device. The configuration space read and write request carries a transmission message. The transmission message includes field information indicating the address of the target device to which the transmission message needs to go. The field information is used by the software-hardware collaborative device to find the configuration space of the target device corresponding to the target device address; a read and write response message corresponding to the configuration space read and write request sent by the software-hardware collaborative device is received. The read and write response message is sent by the software-hardware collaborative device after completing the read and write operation of the transmission message in the configuration space of the target device, and displays the topological network and capability information. Among them, the read and write response message includes a topological network and capability information. The topological network is used to indicate the topological relationship between at least two transmission devices. The capability information is used to indicate the device capability of each of the at least two transmission devices. The target device is any device of the at least two transmission devices.
[0007] In a third aspect, an embodiment of the present application provides a hardware-software collaborative device. The hardware-software collaborative device includes an acquisition unit, a processing unit, and a sending unit. The acquisition unit is used to acquire configuration information and a configuration space read and write request sent by a host-side device through a software processing layer in the hardware-software collaborative device. The configuration information includes a topology network and capability information. The topology network is used to indicate the topological relationship between at least two transmission devices. The capability information is used to indicate the device capability of each transmission device in at least two transmission devices. The configuration space read and write request carries a transmission message, and the transmission message includes field information indicating the address of the target device to be reached by the transmission message. The processing unit is used to find the configuration space of the target device corresponding to the target device address based on the configuration information and field information through the software processing layer. The target device is any device in at least two transmission devices. The processing unit is used to perform read and write operations on the transmission message through the software processing layer in the configuration space of the target device. The sending unit is used to forward the read and write response message corresponding to the configuration space read and write request to the host-side device through the hardware processing layer after the software processing layer completes the read and write operations on the transmission message. The read and write response message includes the topology network and capability information.
[0008] In some optional implementations, the acquisition unit is further configured to acquire topology network and capability information through the software processing layer before acquiring configuration information and a configuration space read and write request sent by the host side device through the software processing layer. The processing unit is configured to allocate the configuration space of each transmission device according to the topology network and capability information through the software processing layer.
[0009] In some other optional implementations, the acquisition unit is further used to acquire the queue depth after forwarding the read / write response message corresponding to the configuration space read / write request to the host-side device via the hardware processing layer, and the queue depth is used to indicate the number of messages to be transmitted in the hardware processing layer. The processing unit is used to send a first message to the host-side device through the hardware processing layer when the queue depth is greater than a preset overload threshold, and the first message is used to instruct the host-side device to suspend sending the configuration space read / write request.
[0010] In some other optional implementations, the acquisition unit is used to acquire a read / write flag, which is used to indicate the execution status of the software processing layer when performing a read / write operation on the transmission message. The processing unit is used to determine that the software processing layer has completed the read / write operation on the transmission message when the read / write flag is a preset mark.
[0011] In some other optional implementations, the processing unit is also used for: in the configuration space of the target device, after the software processing layer completes the read and write operations on the transmission message, the hardware processing layer performs message update processing on the transmission message to obtain an updated transmission message, and the updated transmission message includes an entry time, which is the time when the transmission message is written into the message queue of the hardware processing layer; the acquisition unit is also used to obtain the feedback time, which is the time when the corresponding read and write response message is fed back to the hardware processing layer after the software processing layer completes the read and write operations on the updated transmission message in the configuration space of the target device. The processing unit is used for: performing delay calculation processing on the entry time and the feedback time through the hardware processing layer to obtain the target time consumption, which includes the round-trip transmission delay of the transmission message and the processing delay required for the software processing layer to read and write the updated transmission message. The sending unit is used to send a second message to the host side device through the hardware processing layer when the target time consumption is greater than a preset threshold, and the second message is used to prompt the host side device to perform abnormal read and write processing on the transmission message.
[0012] In some other optional implementations, the acquisition unit is further used to acquire the queue entry time before performing message update processing on the transmission message through the hardware processing layer to obtain the updated transmission message. The processing unit is used to map the queue entry time into the transmission message through the hardware processing layer to obtain the updated transmission message.
[0013] In some other optional implementations, the processing unit is further used to record the target time consumption and transmission message through the software processing layer.
[0014] In some other optional implementations, the acquisition unit is further configured to receive a third message before acquiring the configuration information through the software processing layer and the configuration space read and write request sent by the host-side device, the third message being used to instruct to perform a power-on operation on the software-hardware collaborative device before performing a power-on operation on the host-side device. The processing unit is configured to perform a power-on operation on the software-hardware collaborative device based on the third message.
[0015] In some other optional implementations, the transmission message includes a transaction layer data packet TLP message.
[0016] In a fourth aspect, an embodiment of the present application provides a host-side device. The host-side device includes a sending unit, a receiving unit, and a processing unit. Among them, the sending unit is used to send a configuration space read and write request to the software and hardware collaborative device. The configuration space read and write request carries a transmission message. The transmission message includes field information indicating the target device address to which the transmission message needs to reach. The field information is used for the software and hardware collaborative device to find the configuration space of the target device corresponding to the target device address. The receiving unit is used to receive a read and write response message corresponding to the configuration space read and write request sent by the software and hardware collaborative device. The read and write response message is sent by the software and hardware collaborative device after completing the read and write operation of the transmission message in the configuration space of the target device. The read and write response message includes a topology network and capability information. The topology network is used to indicate the topological relationship between at least two transmission devices. The capability information is used to indicate the device capability of each transmission device in at least two transmission devices. The target device is any device in at least two transmission devices. The processing unit is used to display the topology network and capability information.
[0017] The fifth aspect of the embodiment of the present application provides a message processing device, including: a memory, an input / output (I / O) interface and a memory. The memory is used to store program instructions. The processor is used to execute the program instructions in the memory to execute the software-hardware coordinated message processing method corresponding to the implementation method of the first aspect above; or to execute the software-hardware coordinated message processing method corresponding to the implementation method of the second aspect above.
[0018] The sixth aspect of the embodiments of the present application provides a computer-readable storage medium, which stores instructions. When the computer-readable storage medium is run on a computer, it enables the computer to execute the method corresponding to the implementation method of the first aspect above; or to execute the method corresponding to the implementation method of the second aspect above.
[0019] The seventh aspect of the embodiments of the present application provides a computer program product comprising instructions, which, when executed on a computer or a processor, enables the computer or the processor to execute the method corresponding to the implementation of the first aspect; or, to execute the method corresponding to the implementation of the second aspect.
[0020] It can be seen from the above technical solutions that the embodiments of the present application have the following advantages:
[0021] In an embodiment of the present application, the configuration information includes a topological network and capability information, and the configuration space read and write request carries a transmission message. In addition, in the transmission message mentioned, field information indicating the target device address to which the transmission message needs to arrive is included. The mentioned topological network can indicate the topological relationship between at least two transmission devices, and the capability information can indicate the device capability of each transmission device in at least two transmission devices. Then, in the hardware and software collaborative device, the configuration information and the configuration space read and write request sent by the host side device are obtained through the software processing layer. Subsequently, the software processing layer searches for the configuration space of the target device corresponding to the target device address based on the configuration information and field information. The target device described is any device of at least two transmission devices. After the software processing layer finds the configuration space of the target device, it can perform read and write operations on the transmission message through the software processing layer in the configuration space of the target device. In this way, after the software processing layer completes the read and write operations on the transmission message, the read and write response message corresponding to the configuration space read and write request is forwarded to the host side device via the hardware processing layer, and then the host side device displays the topological network and capability information. Through the above method, there is no need to solidify the topology network and device capabilities of the device in advance through the hardware processing layer. Instead, the configuration information including the topology network and capability information can be flexibly obtained through the software processing layer, which is convenient for flexibly changing the topology network and device capabilities from the perspective of software processing, greatly saving hardware resource overhead. In addition, the software processing layer responds to the read and write operations of the transmission message, flexibly presents the topology network to the host side device, etc., which can meet the transmission needs in different scenarios and subsequent equipment maintenance. BRIEF DESCRIPTION OF THE DRAWINGS
[0022] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0023] Figure 1 A diagram showing a scenario in which a transmission message is responded to based on hardware in a traditional solution;
[0024] Figure 2 A schematic diagram of the system architecture provided in an embodiment of the present application is shown;
[0025] Figure 3 A flowchart of a software-hardware collaborative message processing method provided in an embodiment of the present application is shown;
[0026] Figure 4 A timing diagram of the upper and lower power synchronization mechanism in an embodiment of the present application is shown;
[0027] Figure 5 A schematic diagram showing an updated transmission message provided in an embodiment of the present application is shown;
[0028] Figure 6 A schematic diagram of an embodiment of a software and hardware collaboration device provided in an embodiment of the present application is shown;
[0029] Figure 7 A schematic diagram of an embodiment of a host-side device provided in an embodiment of the present application is shown;
[0030] Figure 8 A schematic diagram of the hardware structure of the message processing device provided in the embodiment of the present application is shown. DETAILED DESCRIPTION
[0031] The embodiments of the present application provide a software-hardware collaborative message processing method and related devices, which can flexibly change the topology network and device capabilities, greatly reduce hardware resource overhead, provide richer maintainable capabilities, and meet the transmission requirements of different scenarios.
[0032] It is understandable that in the specific implementation of this application, related data such as user information is involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards of relevant countries and regions.
[0033] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0034] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the implementation of the present application described herein can be implemented in an order other than those illustrated or described herein, for example. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.
[0035] As the density of device deployment continues to increase, the traditional approach is to pre-solidify the device topology network and device capabilities through the hardware processing layer, and use the software processing layer to implement read and write operations and responses to transmitted messages.
[0036] As a schematic description, Figure 1 FIG. 1 shows a scene diagram of a traditional solution in which hardware is used to respond to a transmission message. Figure 1 As shown, in the scheme of using hardware response transmission message (such as TLP message), it is necessary to pre-solidify the topological network according to its own capabilities through hardware such as network card, and solidify the device capabilities such as physical function (PF) and virtual function (VF), so as to plan the configuration space, read and write attributes, routing rules, etc. of the device. Then, when the host side device reads and writes the configuration space of the device, the hardware feeds back the corresponding response message (such as CPL message or CPLD message, etc.) to the root node (root complex, RC) device according to the pre-solidified topological structure, and then reports the response message to the host side device via the RC device. In this way, the host side device presents the topological network and device capabilities of the device according to the response message. However, pre-solidifying the topological network and device capabilities of the device through hardware will consume a large amount of hardware resources, and it cannot meet the transmission requirements in different scenarios and the subsequent equipment maintenance.
[0037] In order to solve the above-mentioned technical problems, the embodiment of the present application provides a software and hardware collaborative message processing method. The method can be applied in scenarios such as the cloud technology field, such as public cloud scenarios, private cloud scenarios, bare metal scenarios, etc., and is not specifically limited in the embodiment of the present application.
[0038] The software and hardware collaborative message processing method provided in the embodiment of the present application can also be applied to Figure 2 The system architecture shown in FIG. Figure 2As shown, the system architecture includes a software-hardware collaborative device and a host-side device. The software-hardware collaborative device includes a software processing layer and a hardware processing layer.
[0039] The configuration information and the configuration space read and write request sent by the host side device are obtained through the software processing layer. Exemplarily, after the hardware processing layer receives the configuration space read and write request sent by the host side device, the configuration space read and write request can be transparently forwarded to the software processing layer. The described configuration information includes a topological network and capability information. The topological network is used to indicate the topological relationship between at least two transmission devices, and the capability information is used to indicate the device capability of each transmission device in at least two transmission devices. In addition, the configuration space read and write request mentioned carries a transmission message, and the transmission message includes field information indicating the target device address to which the transmission message needs to arrive. In this way, the software processing layer searches for the configuration space of the target device based on the configuration information and field information. The described target device is any device in at least two transmission devices. After the software processing layer finds the configuration space of the target device, the software processing layer performs read and write operations on the transmission message in the configuration space of the target device. In this way, after the software processing layer completes the read and write operations on the transmission message, a corresponding read and write response message can be generated. Subsequently, the read / write response message is forwarded to the host-side device via the hardware processing layer in the software and hardware system device, and then the host-side device displays the topology network and capability information.
[0040] That is to say, in the embodiment of the present application, there is no need to solidify the topology network and device capabilities of the device in advance through the hardware processing layer, but from the perspective of software processing, the configuration information including the topology network and capability information is flexibly obtained through the software processing layer, saving the consumption of hardware resources. In addition, the software processing layer responds to the read and write operations of the transmission message, and flexibly presents the topology network to the host-side device, etc., which can meet the transmission requirements in different scenarios and the subsequent equipment maintenance.
[0041] The software and hardware collaborative devices mentioned above may include but are not limited to terminal devices, servers, question-and-answer robots, etc., which are not specifically limited in the embodiments of this application. The host-side devices mentioned may also include but are not limited to terminal devices, servers, etc. Among them, terminal devices may include but are not limited to smart phones, desktop computers, laptops, tablet computers, smart speakers, vehicle-mounted devices, smart watches, wearable smart devices, intelligent voice interaction devices, smart home appliances, aircraft, etc. The server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content distribution networks (context delivery networks, CDN), and big data and artificial intelligence platforms and other basic cloud computing services, etc., which are not specifically limited in this application. In addition, the terminal devices and servers mentioned can be directly or indirectly connected by wired communication or wireless communication, which is not specifically limited in this application.
[0042] The above-mentioned software and hardware collaborative message processing method can also be applied in the fields of cloud technology. The described cloud technology refers to a hosting technology that unifies a series of resources such as hardware, software, and network in a wide area network or a local area network to realize data calculation, storage, processing, and sharing. Cloud technology is a general term for network technology, information technology, integration technology, management platform technology, application technology, etc. based on the cloud computing business model application, which can form a resource pool and be used on demand, flexible and convenient. Cloud computing technology will become an important support. The background services of the technical network system require a large amount of computing and storage resources, such as video websites, picture websites, and more portal websites. With the high development and application of the Internet industry, in the future, each item may have its own identification mark, and all need to be transmitted to the background system for logical processing. Data of different levels will be processed separately. All kinds of industry data require strong system backing support, which can only be achieved through cloud computing.
[0043] The cloud computing mentioned is a computing model that distributes computing tasks on a resource pool composed of a large number of computers, so that various application systems can obtain computing power, storage space and information services as needed. The network that provides resources is called "cloud". The resources in the "cloud" are infinitely expandable in the eyes of users, and can be obtained at any time, used on demand, expanded at any time, and paid for by use. As a provider of basic cloud computing capabilities, a cloud computing resource pool (referred to as a cloud platform, generally referred to as an Infrastructure as a Service (IaaS) platform) will be established, and various types of virtual resources will be deployed in the resource pool for external customers to choose to use. The cloud computing resource pool mainly includes: computing devices (virtualized machines, including operating systems), storage devices, and network devices. According to the logical function division, the Platform as a Service (PaaS) layer can be deployed on the IaaS layer, and the Software as a Service (SaaS) layer can be deployed on the PaaS layer. SaaS can also be deployed directly on IaaS. PaaS is a platform for software operation, such as databases, web containers, etc. SaaS is a variety of business software, such as web portals, SMS mass senders, etc. Generally speaking, SaaS and PaaS are upper layers relative to IaaS.
[0044] From the perspective of the interaction between the software-hardware collaborative device and the host-side device, a software-hardware collaborative message processing method provided in an embodiment of the present application is introduced below in conjunction with the accompanying drawings. Figure 3 A flowchart of a method for processing messages in which software and hardware are coordinated is shown in the embodiment of the present application. Figure 3 As shown, the message processing method may include the following steps:
[0045] 301. A host-side device sends a configuration space read / write request to a software / hardware collaborative device. The configuration space read / write request carries a transmission message. The transmission message includes field information indicating a target device address to which the transmission message needs to go.
[0046] In this example, in order to ensure that the host-side device can correctly scan the transmission message, it is necessary to ensure that the software and hardware collaborative device can complete the initialization operation before the host-side device performs the power-on operation. The software and hardware collaborative device can obtain the third message to know that it is necessary to perform a power-on operation on the software and hardware collaborative device before performing a power-on operation on the host-side device. In other words, the third message described can indicate that a power-on operation is performed on the software and hardware collaborative device before performing a power-on operation on the host-side device. In this way, after receiving the third message, the software and hardware collaborative device can perform a power-on operation on the software and hardware collaborative device based on the third message, thereby completing the initialization operation of the software and hardware collaborative device. Subsequently, after the software and hardware collaborative device performs the power-on operation, the host-side device performs the power-on operation. The power-on mentioned can be understood as the process from turning on the power of the device to the device running stably and being able to work normally.
[0047] As a schematic description, Figure 4 FIG. 2 shows a timing diagram of the upper and lower power synchronization mechanism in an embodiment of the present application. Figure 4 As shown, the software and hardware collaborative device first performs a power-on operation, and then the host where the DPU is located also performs a power-on operation. Afterwards, the host where the DPU is located detects whether the software and hardware collaborative device has completed the power-on operation. The software and hardware collaborative device informs the host where the DPU is located through a message response that the software and hardware collaborative device has been powered on successfully, that is, the device initialization is successfully achieved. Subsequently, the host where the DPU is located sends a message to the host-side device, notifying the host-side device to perform a power-on operation. In this way, after receiving the message, the host-side device performs a power-on operation and completes the power-on process of the host-side device.
[0048] After both the software and hardware collaborative device and the host-side device perform power-on operations, the host-side device can send a configuration space read and write request to the software and hardware collaborative device when it is necessary to perform read and write operations on the configuration space of certain devices. It should be noted that the described configuration space read and write request carries a transmission message, and the transmission message includes field information indicating the address of the target device to which the transmission message needs to go. In other words, it can be known from the field information to which target device the transmission message is transmitted. Exemplarily, the described transmission message may include but is not limited to a TLP message, etc., which is not specifically limited in the embodiments of the present application.
[0049] In addition, the described software and hardware collaborative device may include a software processing layer and a hardware processing layer, wherein the software processing layer may also be understood as a software processing module in the software and hardware collaborative device, and the hardware processing layer may also be understood as a hardware processing module in the software and hardware collaborative device.
[0050] 302. The hardware and software collaborative device obtains configuration information and configuration space read and write requests sent by the host side device through the software processing layer. The configuration information includes topology network and capability information. The topology network is used to indicate the topological relationship between at least two transmission devices, and the capability information is used to indicate the device capability status of each transmission device in at least two transmission devices.
[0051] In this example, since the traditional solution mainly relies on the topological network and device capabilities of the hardware pre-cured device to process the read and write requests of the host-side device, it will not only consume a large amount of hardware resources, but also fail to meet the transmission requirements in different scenarios, and the equipment maintenance is also difficult. Therefore, in an embodiment of the present application, the host-side device can send a configuration space read and write request to the software and hardware collaborative device. Furthermore, after the host-side device sends the configuration space read and write request to the software and hardware collaborative device, the hardware processing layer in the software and hardware collaborative device can first receive the configuration space read and write request, and transparently forward the configuration space read and write request to the software processing layer in the software and hardware collaborative device. In this way, the software processing layer in the software and hardware collaborative device can obtain the configuration space read and write request.
[0052] Exemplarily, in different transmission scenarios, corresponding topological networks and capability information can be constructed by transmission devices according to different transmission requirements. The described topological network can indicate the topological relationship between two transmission devices. The capability information mentioned can indicate the device capability of each of the at least two transmission devices, such as the computing power, storage capacity, physical function, virtual function, etc. of the device, which is not limited in the specific embodiments of the present application. In this way, the topological network and capability information generated by the transmission device are obtained through the software processing layer, and then the corresponding configuration space is allocated to each transmission device according to the topological network and capability information. It should be noted that the configuration space of the described transmission device can also be understood as the memory space of the transmission device.
[0053] In order to flexibly present the topology network and device capabilities of the device, in the embodiment of the present application, after the software processing layer allocates the corresponding configuration space to each transmission device, the software processing layer can obtain the configuration information. It should be noted that the configuration information described includes the topology network and capability information mentioned above.
[0054] 303. Search, through the software processing layer, for a configuration space of a target device corresponding to the target device address based on the configuration information and the field information. The target device is any device of the at least two transmission devices.
[0055] In this example, since the configuration information includes the topology network and the field information can indicate the address of the target device, after the software processing layer obtains the configuration information and the configuration space read and write request sent by the host device, the field information contained in the transmission message can be demapped from the configuration space read and write request. In this way, based on the configuration information and field information, the software processing layer can find the configuration space of the target device corresponding to the target device address from the configuration space of each transmission device generated.
[0056] 304. In the configuration space of the target device, read and write operations are performed on the transmission message through the software processing layer.
[0057] In this example, after finding the configuration space of the target device, the software processing layer can perform read and write operations on the transmission message in the configuration space of the target device. As an illustrative description, the software processing layer can write the transmission message into the configuration space of the target device; or, the software processing layer can also read the transmission message in the configuration space of the target device.
[0058] 305. After the software processing layer completes the read and write operations on the transmission message, the hardware processing layer forwards the read and write response message corresponding to the configuration space read and write request to the host side device, and the read and write response message includes the topology network and capability information.
[0059] In this example, the preset mark can be used to indicate that the software processing layer has completed the read and write operations on the transmission message. In the process of the software processing layer performing the read and write operations on the transmission message, a corresponding read and write identifier will be generated based on the execution status when the read and write operations are performed. In other words, the read and write identifier can be used to indicate the execution status when the software processing layer performs read and write operations on the transmission message. The software processing layer determines whether the read and write identifier is a preset mark, and then determines that the read and write operations on the transmission message have been completed when it is determined that the read and write identifier is a preset mark. In this way, after the software processing layer completes the read and write operations on the transmission message, a read and write response message corresponding to the configuration space read and write request can be generated. Subsequently, the read and write response message is forwarded to the host side device via the hardware processing layer in the software and hardware system device. It should be noted that the read and write response message includes the topological network and capability information mentioned above.
[0060] The read and write response messages described may include but are not limited to CPL messages or CPLD messages, etc., and are not specifically limited in the embodiments of the present application.
[0061] In other examples, due to high requirements on the processing delay of transmission messages, the hardware and software collaborative devices need to complete the transmission, response and other operations of the transmission messages within the time specified by the protocol. Based on this, in the configuration space of the target device, after the software processing layer completes the read and write operations on the transmission message, the enqueuing time can also be obtained first. The described enqueuing time can be understood as the time when the transmission message is written to the message queue of the hardware processing layer. Then, through the hardware processing layer, the enqueuing time is mapped to the transmission message to obtain the updated transmission message. As a schematic description, Figure 5 FIG. 1 shows a schematic diagram of an updated transmission message provided in an embodiment of the present application. Figure 5 As shown, the updated transmission message includes doubleword (DW) 0 to DW4. The original transmission message is mainly mapped to DW0 to DW3, and the queue entry time is mapped to DW4. It should be noted that the updated transmission message described includes the queue entry time mentioned above.
[0062] Subsequently, after the software processing layer obtains the updated transmission message from the hardware processing layer, it can perform read and write operations on the updated transmission message in the configuration space of the target device, and then feed back the corresponding read and write response message to the hardware processing layer. In this way, after the hardware processing layer obtains the corresponding read and write response message, it can obtain the feedback time from the read and write response message. The feedback time mentioned can be understood as the time when the corresponding read and write response message is fed back to the hardware processing layer after the software processing layer performs read and write operations on the updated transmission message in the configuration space of the target device. In this way, after knowing the queue entry time and feedback time, the hardware processing layer performs delay calculation processing on the queue entry time and feedback time, and calculates the target time consumption. It should be noted that the target time consumption includes the round-trip transmission delay of the message to be transmitted and the processing delay required for the software processing layer to read and write the updated transmission message.
[0063] After calculating the target time, the hardware processing layer continues to determine whether the target time is greater than a preset threshold. Further, if it is determined that the target time is greater than the preset threshold, the hardware processing layer sends a second message to the host device. The second message can instruct the host device to perform abnormal read and write processing on the transmission message.
[0064] Exemplarily, the target time consumption and the transmission message can also be recorded through the software processing layer, so as to analyze the time consumption of the transmission message in different processing stages, and provide data support for subsequent analysis and operation and maintenance.
[0065] In some examples, in order to avoid overload of transmission messages, after sending the read and write response message corresponding to the configuration space request to the host side device, the hardware processing layer can also obtain its own queue depth. The described queue depth can be understood as the number of messages to be processed in the hardware processing layer. When the queue depth is greater than the preset overload threshold, it means that the software and hardware collaborative device has experienced message transmission overload, and overload is likely to cause message transmission timeout and other situations. Therefore, after obtaining the queue depth, the hardware processing layer also needs to determine whether the queue depth is greater than the preset overload threshold. Further, the hardware processing layer sends a first message to the host side device when it is determined that the queue depth is greater than the preset overload threshold. For example, if the queue depth is 10 and the preset overload threshold is 8, it is obvious that 10>8. At this time, the hardware processing layer sends the first message to the host side device. It should be noted that the first message can instruct the host side device to suspend sending configuration space read and write requests. After receiving the first message, the host side device can suspend sending configuration space read and write requests to the software and hardware collaborative device based on the first message, thereby preventing too many transmission messages from being written into the queue of the software and hardware collaborative device, thereby preventing message transmission overload.
[0066] 306. The host-side device displays the topology network and capability information.
[0067] In this example, after the software processing layer generates a read-write response message and forwards the read-write response message to the host-side device via the hardware processing layer in the software and hardware system device, the host-side device can receive the read-write response message. It should be noted that the read-write response message includes topological network and capability information. In this way, after receiving the read-write response message, the host-side device can demap the read-write response message to extract the topological network and capability information in the read-write response message. Subsequently, the host-side device can display the topological network and capability information.
[0068] In the embodiment of the present application, there is no need to solidify the topology network and device capabilities of the device in advance through the hardware processing layer, but the configuration information including the topology network and capability information is flexibly obtained through the software processing layer, which is convenient for flexibly changing the topology network and device capabilities from the perspective of software processing, greatly saving hardware resource overhead. In addition, the software processing layer responds to the read and write operations of the transmission message, flexibly presents the topology network to the host side device, etc., which can meet the transmission requirements in different scenarios and the subsequent equipment maintenance.
[0069] The above mainly introduces the scheme provided by the embodiment of the present application from the perspective of the method. It can be understood that in order to realize the above functions, the hardware structure and / or software module corresponding to the execution of each function are included. Those skilled in the art should easily realize that, in combination with the modules and algorithm steps of each example described in the embodiment disclosed in this application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.
[0070] The embodiment of the present application can divide the functional modules of the device according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.
[0071] The following is a detailed description of the hardware and software collaboration device in the embodiment of the present application. Figure 6 Schematic diagram of an embodiment of the software and hardware collaboration device provided in the embodiment of the present application. Figure 6 As shown, the software and hardware collaborative device may include an acquisition unit 601 , a processing unit 602 , and a sending unit 603 .
[0072] Among them, the acquisition unit 601 is used to obtain configuration information and the configuration space read and write request sent by the host side device through the software processing layer in the software and hardware collaborative device. The configuration information includes the topology network and capability information. The topology network is used to indicate the topological relationship between at least two transmission devices. The capability information is used to indicate the device capability of each transmission device in at least two transmission devices. The configuration space read and write request carries a transmission message, and the transmission message includes field information indicating the target device address that the transmission message needs to reach. For details, please refer to the aforementioned Figure 3 The contents described in step 302 in the above description can be understood and will not be described in detail here.
[0073] The processing unit 602 is used to search the configuration space of the target device corresponding to the target device address based on the configuration information and field information through the software processing layer, and the target device is any device in at least two transmission devices. Figure 3 The contents described in step 303 in the above description can be understood and will not be described in detail here.
[0074] The processing unit 602 is used to perform read and write operations on the transmission message in the configuration space of the target device through the software processing layer. Figure 3 The contents described in step 304 in the above description can be understood and will not be described in detail here.
[0075] The sending unit 603 is used to forward the read and write response message corresponding to the configuration space read and write request to the host side device via the hardware processing layer after the software processing layer completes the read and write operation on the transmission message. The read and write response message includes the topology network and capability information. Figure 3 The contents described in step 305 in the above description can be understood and will not be described in detail here.
[0076] In some optional implementations, the acquisition unit 601 is further configured to acquire the topology network and capability information through the software processing layer before acquiring the configuration information and the configuration space read and write request sent by the host side device through the software processing layer. The processing unit 602 is configured to allocate the configuration space of each transmission device according to the topology network and capability information through the software processing layer.
[0077] In some other optional implementations, the acquisition unit 601 is further used to acquire the queue depth after forwarding the read / write response message corresponding to the configuration space read / write request to the host-side device via the hardware processing layer, and the queue depth is used to indicate the number of messages to be transmitted in the hardware processing layer. The processing unit 602 is used to send a first message to the host-side device through the hardware processing layer when the queue depth is greater than a preset overload threshold, and the first message is used to instruct the host-side device to suspend sending the configuration space read / write request.
[0078] In some other optional implementations, the acquisition unit 601 is used to acquire a read / write flag, which is used to indicate the execution status of the software processing layer when performing a read / write operation on the transmission message. The processing unit 602 is used to determine that the software processing layer has completed the read / write operation on the transmission message when the read / write flag is a preset mark.
[0079] In some other optional implementations, the processing unit 602 is also used for: in the configuration space of the target device, after the software processing layer performs read and write operations on the transmission message, the hardware processing layer performs message update processing on the transmission message to obtain an updated transmission message, and the updated transmission message includes an entry time, and the entry time is the time when the transmission message is written into the message queue of the hardware processing layer; the acquisition unit 601 is also used to obtain the feedback time, and the feedback time is the time when the corresponding read and write response message is fed back to the hardware processing layer after the software processing layer performs read and write operations on the updated transmission message in the configuration space of the target device. The processing unit 602 is used for: performing delay calculation processing on the entry time and the feedback time through the hardware processing layer to obtain the target time consumption, and the target time consumption includes the round-trip transmission delay of the transmission message and the processing delay required for the software processing layer to read and write the updated transmission message. The sending unit 603 is used to send a second message to the host side device through the hardware processing layer when the target time consumption is greater than a preset threshold, and the second message is used to prompt the host side device to perform abnormal read and write processing on the transmission message.
[0080] In some other optional implementations, the acquisition unit 601 is further used to acquire the queue entry time before performing message update processing on the transmission message through the hardware processing layer to obtain the updated transmission message. The processing unit 602 is used to map the queue entry time into the transmission message through the hardware processing layer to obtain the updated transmission message.
[0081] In some other optional implementations, the processing unit 602 is further configured to record target time consumption and transmission messages through a software processing layer.
[0082] In some other optional implementations, the acquisition unit 601 is further configured to receive a third message before acquiring the configuration information through the software processing layer and the configuration space read and write request sent by the host-side device, the third message being used to instruct to perform a power-on operation on the software-hardware collaborative device before performing a power-on operation on the host-side device. The processing unit 602 is configured to perform a power-on operation on the software-hardware collaborative device based on the third message.
[0083] In some other optional implementations, the transmission message includes a transaction layer data packet TLP message.
[0084] The above mainly describes the hardware and software collaborative device from the perspective of functional modules. The host side device in the embodiment of the present application will be described in detail from the perspective of functional modules. Figure 7 FIG. 1 is a schematic diagram of an embodiment of a host-side device provided in an embodiment of the present application. Figure 7 As shown, the host-side device includes a sending unit 701 , a receiving unit 702 and a processing unit 703 .
[0085] Among them, the sending unit 701 is used to send a configuration space read and write request to the software and hardware collaborative device. The configuration space read and write request carries a transmission message. The transmission message includes field information indicating the target device address to which the transmission message needs to be sent. The field information is used by the software and hardware collaborative device to find the configuration space of the target device corresponding to the target device address. For details, please refer to the aforementioned Figure 3 The contents described in step 301 in the above description can be understood and will not be described in detail here.
[0086] The receiving unit 702 is used to receive a read / write response message corresponding to a configuration space read / write request sent by a software / hardware collaborative device. The read / write response message is sent by the software / hardware collaborative device after completing the read / write operation of the transmission message in the configuration space of the target device. The read / write response message mentioned includes a topology network and capability information. The topology network is used to indicate the topological relationship between at least two transmission devices. The capability information is used to indicate the device capability of each transmission device in at least two transmission devices. The target device is any device in at least two transmission devices. For details, please refer to the aforementioned Figure 3 The contents described in step 305 in the above description can be understood and will not be described in detail here.
[0087] Processing unit 703 is used to display topology network and capability information. Figure 3 The contents described in step 306 in the above description can be understood and will not be described in detail here.
[0088] The above describes the hardware and software collaborative device and the host-side device in the embodiment of the present application from the perspective of modular functional entities. The following describes the message processing device in the embodiment of the present application from the perspective of hardware processing. The described message processing device may include but is not limited to the aforementioned Figure 6 The hardware and software collaborative equipment mentioned in Figure 7 The host side devices mentioned in etc. Figure 8 801 , a communication line 807 , a memory 803 , and at least one communication interface 804 .
[0089] The processor 801 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (server IC), or one or more integrated circuits for controlling the execution of the program of the present application.
[0090] The communication link 807 may include a pathway to transmit information between the above-mentioned components.
[0091] The communication interface 804 uses any transceiver-like device for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc.
[0092] The memory 803 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, and the memory may exist independently and be connected to the processor via a communication line 807. The memory may also be integrated with the processor.
[0093] The memory 803 is used to store computer-executable instructions for executing the solution of the present application, and the execution is controlled by the processor 801. The processor 801 is used to execute the computer-executable instructions stored in the memory 803, thereby implementing the message processing method provided in the above embodiment of the present application.
[0094] Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application code, which is not specifically limited in the embodiments of the present application.
[0095] In a specific implementation, as an embodiment, the message processing device may include multiple processors, such as Figure 8 801 and processor 802 in the embodiment of the present invention. Each of these processors may be a single-CPU processor or a multi-CPU processor. The processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).
[0096] In a specific implementation, as an embodiment, the message processing device may further include an output device 805 and an input device 806. The output device 805 communicates with the processor 801 and may display information in a variety of ways. The input device 806 communicates with the processor 801 and may receive input from a target object in a variety of ways. For example, the input device 806 may be a mouse, a touch screen device, or a sensor device.
[0097] The message processing device mentioned above can be a general device or a dedicated device. In a specific implementation, the message processing device can be a server, a terminal, etc. or a Figure 8 The embodiment of the present application does not limit the type of the message processing device.
[0098] Need to explain, Figure 8 The processor 801 in the embodiment can call the computer execution instruction stored in the memory 803 to make the message processing device execute the following Figure 3 to Figure 4 The method in the corresponding method embodiment.
[0099] Specifically, Figure 6 The processing unit 602, Figure 7 The function / implementation process of the processing unit 703 in Figure 8 The processor 801 in the embodiment calls the computer execution instructions stored in the memory 803 to implement. Figure 6 The acquisition unit 601 and the sending unit 603 in Figure 7 The functions / implementation processes of the sending unit 701 and the receiving unit 702 can be Figure 8 It is implemented by the communication interface 804 in.
[0100] An embodiment of the present application also provides a computer storage medium, wherein the computer storage medium stores a computer program for electronic data exchange, and the computer program enables a computer to execute part or all of the steps of any software-hardware collaborative message processing method recorded in the above method embodiments.
[0101] An embodiment of the present application also provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program, and the computer program can be operated to cause a computer to execute part or all of the steps of any software-hardware collaborative message processing method recorded in the above method embodiments.
[0102] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product.
[0103] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0104] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.
[0105] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0106] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
[0107] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store program codes.
[0108] The above embodiments may be implemented in whole or in part through software, hardware, firmware or any combination thereof. When implemented by software, they may be implemented in whole or in part in the form of a computer program product.
[0109] The computer program product includes one or more computer instructions. When loading and executing the computer execution instruction on the computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable devices. The computer instruction can be stored in a computer-readable storage medium, or transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instruction can be transmitted from a website site, a computer, a server or a data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a server, a data center, etc. that includes one or more available media integration. Available media can be magnetic media, (for example, floppy disk, hard disk, tape), optical media (for example, DVD), or semiconductor media (such as SSD)) and the like.
[0110] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.
Claims
1. A software-hardware collaborative message processing method, characterized in that: Applied to a software-hardware collaborative device, the software-hardware collaborative device includes a software processing layer and a hardware processing layer, and the method includes: The configuration information and the configuration space read / write request sent by the host-side device are obtained through the software processing layer, wherein the configuration information includes a topology network and capability information, wherein the topology network is used to indicate a topological relationship between at least two transmission devices, and the capability information is used to indicate the device capability of each of the at least two transmission devices, and the configuration space read / write request carries a transmission message, and the transmission message includes field information indicating a target device address to which the transmission message needs to reach; Searching, by the software processing layer, for a configuration space of a target device corresponding to the target device address based on the configuration information and the field information, wherein the target device is any device of the at least two transmission devices; In the configuration space of the target device, performing read and write operations on the transmission message through the software processing layer; After the software processing layer completes the read and write operations on the transmission message, the read and write response message corresponding to the configuration space read and write request is forwarded to the host side device via the hardware processing layer, and the read and write response message includes the topology network and the capability information.
2. The method according to claim 1, characterized in that Before obtaining the configuration information and the configuration space read and write request sent by the host side device through the software processing layer, the method further includes: Acquiring topological network and capability information through the software processing layer; The configuration space of each transmission device is allocated through the software processing layer according to the topology network and the capability information.
3. The method according to any one of claims 1 to 2, characterized in that After forwarding the read / write response message corresponding to the configuration space read / write request to the host-side device via the hardware processing layer, the method further includes: Obtaining a queue depth, where the queue depth is used to indicate the number of messages to be transmitted in the hardware processing layer; When the queue depth is greater than a preset overload threshold, a first message is sent to the host-side device through the hardware processing layer, where the first message is used to instruct the host-side device to suspend sending the configuration space read and write requests.
4. The method according to any one of claims 1 to 2, characterized in that After the read and write operations on the transmission message are completed by the software processing layer in the configuration space of the target device, the method further includes: Performing message update processing on the transmission message through the hardware processing layer to obtain an updated transmission message, wherein the updated transmission message includes an entry time, and the entry time is the time when the transmission message is written into the message queue of the hardware processing layer; Acquire a feedback time, where the feedback time is the time when, after the software processing layer completes the read and write operations on the updated transmission message in the configuration space of the target device, a corresponding read and write response message is fed back to the hardware processing layer; Performing delay calculation processing on the queue entry time and the feedback time by the hardware processing layer to obtain a target time consumption, wherein the target time consumption includes a round-trip transmission delay of the transmission message and a processing delay required for the software processing layer to read and write the updated transmission message; When the target time consumption is greater than a preset threshold, a second message is sent to the host-side device through the hardware processing layer, where the second message is used to prompt the host-side device to perform abnormal reading and writing processing on the transmission message.
5. The method according to claim 4, characterized in that Before performing message update processing on the transmission message through the hardware processing layer to obtain an updated transmission message, the method further includes: Obtain the team entry time; The performing message update processing on the transmission message by the hardware processing layer to obtain an updated transmission message includes: The enqueue time is mapped into the transmission message through the hardware processing layer to obtain an updated transmission message.
6. The method according to claim 4, characterized in that The method further comprises: The target time consumption and the transmission message are recorded through the software processing layer.
7. The method according to any one of claims 1 to 2, characterized in that The software processing layer performs the read and write operations on the transmission message to complete, including: Acquire a read / write identifier, where the read / write identifier is used to indicate the execution status of the software processing layer when performing the read / write operation on the transmission message; When the read / write flag is a preset flag, it is determined that the software processing layer completes the read / write operation on the transmission message.
8. The method according to any one of claims 1 to 2, characterized in that Before obtaining the configuration information and the configuration space read and write request sent by the host side device through the software processing layer, the method further includes: receiving a third message, wherein the third message is used to instruct to perform the power-on operation on the hardware-software collaborative device before performing the power-on operation on the host-side device; The power-on operation is performed on the software-hardware collaborative device based on the third message.
9. The method according to any one of claims 1 to 2, characterized in that The transmission message includes a transaction layer data packet TLP message.
10. A software-hardware collaborative message processing method, characterized in that: Applied to a host-side device, the method includes: Sending a configuration space read / write request to the software / hardware collaborative device, wherein the configuration space read / write request carries a transmission message, wherein the transmission message includes field information indicating a target device address to which the transmission message needs to go, and the field information is used by the software / hardware collaborative device to search for a configuration space of a target device corresponding to the target device address; Receive a read / write response message corresponding to the configuration space read / write request sent by the software / hardware collaborative device, the read / write response message is sent by the software / hardware collaborative device after completing the read / write operation on the transmission message in the configuration space of the target device, the read / write response message includes a topology network and capability information, the topology network is used to indicate the topological relationship between at least two transmission devices, the capability information is used to indicate the device capability status of each of the at least two transmission devices, and the target device is any device among the at least two transmission devices; The topology network and the capability information are displayed.
11. A software and hardware collaborative device, characterized in that: include: an acquisition unit, configured to acquire configuration information and a configuration space read / write request sent by a host-side device through a software processing layer in the software / hardware collaborative device, wherein the configuration information includes a topology network and capability information, wherein the topology network is used to indicate a topological relationship between at least two transmission devices, and the capability information is used to indicate a device capability of each of the at least two transmission devices, and the configuration space read / write request carries a transmission message, and the transmission message includes field information indicating a target device address to which the transmission message needs to reach; a processing unit, configured to search, through the software processing layer, based on the configuration information and the field information, a configuration space of a target device corresponding to the target device address, wherein the target device is any device of the at least two transmission devices; The processing unit is used to perform read and write operations on the transmission message through the software processing layer in the configuration space of the target device; A sending unit is used to forward the read / write response message corresponding to the configuration space read / write request to the host side device via the hardware processing layer after the software processing layer completes the read / write operation on the transmission message, wherein the read / write response message includes the topology network and the capability information.
12. A host-side device, characterized in that: include: A sending unit, used to send a configuration space read / write request to a software / hardware collaborative device, wherein the configuration space read / write request carries a transmission message, wherein the transmission message includes field information indicating a target device address to which the transmission message needs to arrive, and wherein the field information is used by the software / hardware collaborative device to search for a configuration space of a target device corresponding to the target device address; A receiving unit, used for receiving a read / write response message corresponding to the configuration space read / write request and sent by the software / hardware collaborative device, wherein the read / write response message is sent by the software / hardware collaborative device after completing the read / write operation on the transmission message in the configuration space of the target device, and the read / write response message includes a topology network and capability information, wherein the topology network is used to indicate the topological relationship between at least two transmission devices, and the capability information is used to indicate the device capability status of each of the at least two transmission devices, and the target device is any device among the at least two transmission devices; A processing unit is used to display the topology network and the capability information.
13. A message processing device, characterized in that: include: An input / output interface, a processor and a memory, wherein program instructions are stored in the memory; The processor is used to execute program instructions stored in the memory to perform the method according to any one of claims 1 to 10.
14. A computer-readable storage medium, characterized in that: The computer-readable storage medium comprises instructions, which, when executed on a computer device, cause the computer device to perform the method according to any one of claims 1 to 10.
15. A computer program product, characterized in that The computer program product comprises instructions, which, when executed on a computer device, cause the computer device to perform the method according to any one of claims 1 to 10.
Citation Information
Patent Citations
Software and hardware collaborative message acceleration method and device
CN112003792A
Software and hardware cooperative programmable forwarding system, method and device
CN112491889A
Message processing method and device, electronic equipment and computer readable storage medium
CN116015613A
Memory resource allocation in an end-point device
US20190132198A1
Flexible configuration space
US7752376B1
