CN107145399A - A kind of shared-memory management method and shared-memory management equipment - Google Patents

Abstract

The embodiment of the present invention discloses a shared memory management method and a shared memory management device. The method is applied to a message zero-copy system. The message zero-copy system runs on an operating system. The message zero-copy system includes at least two Application program APPs, APPs share the first packet cache pbuf memory, the method includes: any application program APP in the APPs sets the read-write operation protection attribute of the APP to the first pbuf memory to be read-only at the current moment; if The APP receives the pbuf memory misoperation notification message sent by the operating system, then obtains the pbuf memory misoperation site information in the pbuf memory misoperation notification message; determines the memory misoperation based on the pbuf memory misoperation site information on site. Therefore, when the APP misuses the shared pbuf memory, it can accurately locate the problem site where the misoperation occurs and ensure system reliability.

Description

A shared memory management method and shared memory management device

technical field

The invention relates to the communication field, in particular to a shared memory management method and a shared memory management device.

Background technique

Network Function Virtualization (English: Network Function Virtualization, NFV) system decouples software and hardware and abstracts functions, so that network device functions no longer depend on dedicated hardware, resources can be fully and flexibly shared, and rapid development and deployment of new services are realized. The basis of NFV technology includes cloud computing technology and virtualization technology. General-purpose computing, storage, network and other hardware devices can be decomposed into various virtual resources through virtualization technology for use by various upper-level applications.

When running multiple applications (English: Application, APP) on the NFV system, in order to realize message forwarding between different application processes, the zero-copy technology of the shared memory mechanism can be used, that is, different application programs share The same packet cache (English: packet buffer, pbuf) memory can avoid copying operations between different applications and improve system performance. However, when the shared memory mechanism is used at the same time, since each application program shares the same pbuf memory, the isolation between applications is destroyed. As a result, when a pbuf memory misuse problem occurs, it is impossible to accurately locate the memory problem site.

Contents of the invention

Embodiments of the present invention provide a shared memory management method and a shared memory management device, so as to accurately locate the problem site where the misoperation occurs when an APP misuses the shared pbuf memory.

In the first aspect, the embodiment of the present invention provides a shared memory management method, the method is applied to a message zero-copy system, the message zero-copy system runs on an operating system, and the message zero-copy system includes at least two applications For the program APPs, the shared memory of the APPs is first the pbuf memory, and the method performs shared memory management through the following steps. First, any application APP in the APPs sets the protection attribute of the APP to the read and write operation of the first pbuf memory as read-only at the current moment; then, when the APP receives the pbuf memory misoperation notification message sent by the operating system, it obtains the pbuf memory The pbuf memory misuse site information in the misoperation notification message, the pbuf memory misuse notification message is used to remind the APP to write the first pbuf memory and the specific location of the write operation; finally, the APP determines based on the pbuf memory misuse site information The memory misoperation scene where the APP writes to the first pbuf memory. In this way, when multiple APPs share the same pbuf memory, when a memory misoperation occurs in the shared pbuf memory, the APP and the specific location that caused the pbuf memory misoperation can be quickly and accurately located, that is, the pbuf memory misoperation site can be determined , to ensure system reliability.

In a possible design, the operating system includes a Linux operating system, the Linux operating system includes an mprotect memory management interface, and the mprotect memory management interface is used to be called to set the read and write operation attributes of the first pbuf memory; thus the APP calls The mprotect memory management interface sets the APP's read and write operation attribute to the first pbuf memory as read-only at the current moment. Therefore, by calling the mprotect memory management interface of the Linux operating system, the read and write operation attributes of the first pbuf memory can be conveniently set under the Linux operating system.

In a possible design, the mprotect memory management interface is used to be called by the APP to set the read and write operation attributes of the APP to the first pbuf memory based on one or more page tables. Therefore, the mprotect memory read and write operation management mechanism based on page table management can independently control the first pbuf memory.

In a possible design, the message zero-copy system also includes a second pbuf memory, and the shared memory of APPs also includes the second pbuf memory, wherein the first pbuf memory is a small page memory, and the second pbuf memory is Huge page memory, the first pbuf memory has a unique correspondence with one or more page tables. The APP determines that the first pbuf memory is the shared memory of the APPs at a preset time, and the APP determines that the second pbuf memory is the shared memory of the APPs outside the preset time. When the frequency of the preset time is smaller, it means that the frequency of pbuf memory monitoring is smaller, so the reliability of the system is relatively low at this time, and at this time, the relative times of filling the second pbuf memory with the large page memory is more, the system The performance improvement is greater; the higher the frequency at the preset time, the greater the frequency of pbuf memory monitoring, so the reliability of the system is relatively high at this time, and at this time, use the second pbuf memory of the large page memory to fill The relative number of times is small, and the performance improvement of the system is small. Therefore, the preset time can be set according to the requirements and by weighing the performance improvement and reliability of the system.

In a possible design, the first pbuf memory is also used to cache the track ID, and the APP also records the track point information of the first pbuf memory through the track ID, and the track point information includes the application program ID and the current process ID of the application program and the current moment. Through the trajectory of the first pbuf determined by the trajectory point information of the first pbuf, the upstream APP passed by the first pbuf is further determined, so that after determining the memory misoperation site where the APP performs a write operation on the memory of the first pbuf, you can Further use the upstream APP of this APP to troubleshoot pbuf memory problems to further improve system reliability.

In the first aspect, the embodiment of the present invention provides a shared memory management method, the method is applied to the operating system, the message zero-copy system runs on the operating system, and the message zero-copy system includes at least two application programs APPs, APPs Including the first message cache pbuf memory, the method implements shared memory management through the following steps. First, the operating system sets an instruction to record that the read-write operation attribute of the APP to the first pbuf memory is read-only according to any application program APP in the APPs. The pbuf memory performs a write operation, and the operating system sends a pbuf memory misoperation notification message to the APP. The pbuf memory misoperation notification message is used to remind the APP to perform a write operation on the first pbuf memory and the specific location of the write operation. In this way, when multiple APPs share the same pbuf memory, when a memory misoperation occurs in the shared pbuf memory, the APP and the specific location that caused the pbuf memory misoperation can be quickly and accurately located, that is, the pbuf memory misoperation site can be determined , to improve system performance while ensuring system reliability.

In a possible design, the operating system includes a Linux operating system, the Linux operating system includes an mprotect memory management interface, and the mprotect memory management interface is used to be called by the APP to set the APP's read and write operation attributes to the first pbuf memory; When the APP sets the read-write operation attribute of the APP to the first pbuf memory as read-only at the current moment by calling the mprotect memory management interface, the Linux operating system records the read-write operation attribute of the APP to the first pbuf memory. Therefore, by calling the mprotect memory management interface of the Linux operating system, the read and write operation attributes of the first pbuf memory can be conveniently set under the Linux operating system.

In a possible design, the mprotect memory management interface is used to be called by the APP to set the read and write operation attributes of the APP to the first pbuf memory based on one or more page tables. Therefore, the mprotect memory read and write operation management mechanism based on page table management can independently control the first pbuf memory.

In a possible design, the page table includes a read-write operation attribute identifier, and the operating system records that the read-write operation attribute of the APP to the first pbuf memory is read-only through the read-write operation attribute identifier on the page table. Therefore, the mprotect memory read and write operation management mechanism based on page table management can independently control the first pbuf memory.

In a third aspect, an embodiment of the present invention provides an application program APP, which has a function of implementing the method in the first aspect above, and the function may be implemented by hardware, or may be implemented by executing corresponding software on the hardware. The hardware or software includes one or more modules corresponding to the above functions.

In a fourth aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions for the above-mentioned application program APP described in the third aspect, which includes a program for executing the method of the first aspect above .

In a fifth aspect, an embodiment of the present invention provides an operating system. The operating system has the function of implementing the method of the second aspect above. The function may be implemented by hardware, or by executing corresponding software on the hardware. The hardware or software includes one or more modules corresponding to the above functions.

In a sixth aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions for the above-mentioned operating system in the fifth aspect, which includes a program for executing the method in the second aspect above.

In a seventh aspect, an embodiment of the present invention provides a shared memory management device, the shared memory management device includes a memory storing executable program codes, and a processor coupled to the memory; an application program runs on the processor APP and operating system, the operating system has a message zero-copy system running on it, and the message zero-copy system includes at least two application programs APPs, and the APPs share the first packet cache pbuf memory, and the APP is the Any APP among APPs, the APP is used to execute the method flow of the first aspect of the present invention.

In an eighth aspect, an embodiment of the present invention provides a shared memory management device, the shared memory management device includes a memory storing executable program codes, and a processor coupled to the memory; an application program runs on the processor APP and an operating system, the operating system runs a message zero-copy system, and the message zero-copy system includes at least two application programs APPs, and the APPs share the first message cache pbuf memory, and the APP is all Any one of the above APPs, the operating system is used to execute the method flow of the second aspect of the present invention.

In a ninth aspect, an embodiment of the present invention provides a shared memory management device, where the shared memory management device includes a processor and a memory. The application program APP of the third aspect and the operating system of the fifth aspect run on the processor, and the processor is configured to support the application program APP and the operating system to execute the shared memory management method provided by the embodiment of the present invention. The memory is used for coupling with the processor, for storing necessary program codes and data of the application program APP, and for storing necessary program codes and data of the operating system.

Compared with the prior art, in the solution of the embodiment of the present invention, when multiple APPs share the same pbuf memory, by setting the read-write operation attribute of the APP to the first pbuf memory as read-only, the APP can be monitored by the operating system. When performing a write operation on the first pbuf, the operating system sends a pbuf memory misoperation notification message to the APP, so that the APP can quickly and accurately locate the APP and the specific location that caused the pbuf memory misoperation based on the pbuf memory misoperation notification message, that is, Determine the pbuf memory misuse site to ensure system reliability.

Description of drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings that are required in the description of the embodiments or the prior art.

FIG. 1 is a schematic diagram of the architecture of a network function virtualization system provided by an embodiment of the present invention;

FIG. 2 is a schematic structural diagram of another NFV system provided by an embodiment of the present invention;

FIG. 3 is a schematic diagram of the architecture of another NFV system provided by an embodiment of the present invention;

FIG. 4 is a schematic diagram of the architecture of a message zero-copy system provided by an embodiment of the present invention;

FIG. 5 is a schematic flowchart of a shared memory management method provided by an embodiment of the present invention;

FIG. 6 is a schematic diagram of a first pbuf memory management process between APP processes provided by an embodiment of the present invention;

7 is a schematic diagram of a message zero-copy process and a first pbuf memory management process provided by an embodiment of the present invention;

Fig. 8-a is a schematic diagram of another message zero-copy system provided by an embodiment of the present invention;

Figure 8-b is a schematic diagram of another message zero-copy process and pbuf memory management process provided by the embodiment of the present invention;

FIG. 9 is a schematic structural diagram of an application program APP provided by an embodiment of the present invention;

FIG. 10 is a schematic structural diagram of an operating system provided by an embodiment of the present invention;

FIG. 11 is a schematic structural diagram of a shared memory management device provided by an embodiment of the present invention;

FIG. 12 is a schematic structural diagram of another shared memory management device provided by an embodiment of the present invention;

FIG. 13 is a schematic structural diagram of a shared memory management device provided by an embodiment of the present invention.

detailed description

In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention.

In order to better understand the technical solutions of the present invention, the application scenarios based on the embodiments of the present invention will be firstly described below.

Referring first to FIG. 1 , FIG. 1 is a schematic diagram of an architecture of a network function virtualization system NFV100 provided by an embodiment of the present invention. As shown in Figure 1, the NFV system includes a hardware layer 110, a management program (English: Hyperviser) layer 120, an operating system (English: OperSystem, OS) layer 130, and an application program (English: application, APP) layer 140, wherein, The operating system layer 130 and various application programs constitute a virtual machine (English: Virtual Machine, VM).

Among them, the hardware layer 110 is a hardware platform running in a virtualized environment, and the hardware layer 110 can be composed of one or more servers; the hypervisor 120 is directly installed on the hardware computing resources, and is used to manage and invoke hardware resources, without the need for a bottom layer Operating system, that is, it can be understood that the hypervisor is a very thin operating system; the operating system layer 130 includes one or more operating systems, which are access operating systems (English: Guest OS) running on the hypervisor. In an example, the operating system may be a Linux operating system or other operating systems; the application layer 140 includes one or more application program modules, which are applications running on the access operating system to provide services for clients.

Referring to FIG. 2, FIG. 2 is a schematic structural diagram of another NFV system provided by an embodiment of the present invention. As shown in FIG. 2 , the NFV system includes a hardware layer 210 , a host (English: host) layer 220 , a hypervisor layer 230 , an access operating system (English: guest) 240 , and an APP layer 250 . Wherein, the difference between the NFV system architecture shown in FIG. 2 and the network function virtualization system architecture shown in FIG. 1 is that, in the network function virtualization system architecture shown in FIG. It can be used to install the basic operating system, so that the hypervisor layer 230 runs on the basic operating system and builds a complete set of virtual hardware platform. Users can install new operating systems and application software, host layer and guest layer on the guest layer as needed. The operating system on can be completely irrelevant. In the embodiment of the present invention, the operating system of the host layer may be Windows, and the operating system of the guest layer may be a Linux operating system.

Referring to FIG. 3 , FIG. 3 is a schematic structural diagram of another NFV system provided by an embodiment of the present invention. The network function virtualization system shown in FIG. 3 includes a network function virtualization infrastructure layer (English: NFV Infrastructure, NFVI) 310, a virtual network function (English: Virtual Network Functions, VNFS) 320, and an operation/service support system (English: Operation Support System/Business Support System, OSS/BSS) 330 and network function virtualization management and orchestration system (English: NFV Management and Orchestration, NFV MANO) 340 .

Among them, the virtualization infrastructure layer 310 includes a hardware resource layer, a virtualization layer, and a virtual resource layer, and the VNFS 320 includes multiple VNFs and multiple network element managers (English: Element Manager, EM), which can provide users with different virtual network Function. Compared with the architecture shown in FIG. 1 or FIG. 2 , it can be considered that the APP in FIG. 1 or FIG. 2 is deployed on the VNF in FIG. 3 .

Among them, NFV MANO includes a network function virtualization orchestrator (English: NFV Orchestrator, NFVO), one or more virtualized network function managers (English: VNF Manager, VNFM) and a virtualized infrastructure manager (English: Virtualized Infrastructure Manager). Manager, VIM), Network Service Catalog (English: Network Service Catalog, NS Catalog), which is responsible for the management and arrangement of the entire NFVI resources, responsible for the mapping and association of business networks and NFVI resources, and responsible for the implementation of OSS business resource processes, etc. MANO implements virtual machine creation, network element installation, affinity and anti-affinity configuration, and system expansion and contraction by analyzing the virtual network function descriptor (English: VNF Descriptor, VNFD) file provided by the product.

Referring to FIG. 4, FIG. 4 is a schematic diagram of the architecture of a message zero-copy system 400 provided by an embodiment of the present invention. As shown in FIG. 4, the message zero-copy system 400 includes N APPs, that is, APPs, respectively APP1, APP2, ... APPn, the first network card and the first network card queue, the second network card and the second network card queue, and a message cache pbuf memory. Wherein, different APPs belong to different business processes, and the pbuf memory is shared by N APPs.

In the embodiment of the present invention, the N APPs can be the APPs running on the same VM in FIG. 1 and FIG. 2 , or they can be the VNFs in FIG. 3 , or they can be different application programs running on the physical computer.

In the embodiment of the present invention, the message zero-copy system may run on an operating system on a physical computer, or on an operating system in an NFV system.

It is worth noting that the APP can be an independent functional module for performing characteristic functions, for example, it can be an APP for performing transport layer processing functions, or an APP for performing application layer processing functions, or it can also be A function module written for a single function.

Optionally, in an embodiment of the present invention, the multiple APPs may be different processes; they may also be different threads in the same process. Regardless of whether the multiple APPs are in different processes or different threads in the same process, as long as the multiple APPs share the same pbuf memory and use the pbuf memory to forward packets among the multiple APPs, The application scenarios provided by the embodiments of the present invention.

In the embodiment of the present invention, the above-mentioned first network card and the second network card may be virtual network cards (English: virtual network card, VNIC), or may be physical network cards.

In the embodiment of the present invention, when the message zero-copy system is used for zero-copy message forwarding, first the APP1 process fills the direct memory storage (English: Direct Memory Access, DMA) address of the pbuf memory in the first network card queue , the first network card fills the message into the pbuf memory address, then APP1 receives the message from the queue of the first network card to the pbuf memory, and processes the message through multiple APP processes in turn, and finally APPn finishes processing , the second network card fills the pbuf memory address in the second network card queue, APPn fills the message into the pbuf memory address of the second network card queue, and then the second network card retrieves the message from the second network card queue and sends it go out. After the second network card sends the message, APPn reclaims the pbuf memory to the memory pool. It can be seen that the message zero-copy system realizes message forwarding between different APPs through pbuf memory shared memory, thereby realizing message zero-copy.

But at the same time, based on the message zero-copy system, since different APPs share the same pbuf memory, the isolation between different APP processes is destroyed. When pbuf memory problems occur during cross-process operations, pbuf memory problems cannot be found. The APP and the specific location (for example, when there is a problem with the pbuf memory, it is impossible to determine which APP among the n APPs has the misoperation problem), that is, it is impossible to locate the first site of the problem, resulting in a long service recovery period.

In order to solve the above problems, the embodiment of the present invention proposes a shared memory management method. By setting the read and write operation attributes of the pbuf memory, when a misoperation occurs in the pbuf memory, the memory misoperation site where the pbuf memory misoperation occurs can be obtained. , to enhance the reliability of the message zero-copy system.

The embodiments of the present invention will be described in detail below. Referring to FIG. 5, FIG. 5 is a schematic flowchart of a shared memory management method provided by an embodiment of the present invention. The shared memory management method is applied to the zero-copy system shown in FIG. 4, and the message zero-copy system runs on the operating system. As shown in Figure 5, the method may include the following steps:

S501, any application program APP in the APPs sets the read and write operation attribute of the APP to the first pbuf memory to be read-only at the current moment, and the operating system records the reading of the APP to the first pbuf memory Write operation attributes.

In the embodiment of the present invention, the at least two application programs are APPs shown in FIG. 4 , and any application program APP in the at least two application programs can be any application program between APP1 to APPn, for example, APP1, APP2, APPn.

Among them, the read and write operation attribute of the first pbuf memory means that in order to manage the first pbuf of the shared memory and prevent multiple applications from writing the first pbuf at the same time to cause memory problems, the APP set by each APP The read and write operations that the first pbuf should perform at a certain moment, so when the APP performs operations other than the read and write operation attributes on the first pbuf memory, the operating system considers it a memory misoperation.

In the embodiment of the present invention, the read and write operation attributes include read only, read and write, and write only. When the read and write operation attribute of the APP to the first pbuf memory is set to read-only, and the APP performs a write operation on the first pbuf memory at this time, the operating system thinks that the APP misoperated the first pbuf memory; when setting the APP to the first pbuf memory When the first pbuf memory is read and written, that is, the APP performs a read or write operation on the first pbuf memory at this time, the operating system will not monitor it as a memory misoperation; when setting the APP to the first pbuf memory as write-only, Therefore, at this time, when the APP performs a read operation on the first pbuf memory, the operating system thinks that the APP misoperated on the first pbuf memory. It is worth noting that when the attribute of the read and write operation is read and write, it can also be determined that the attribute of the read and write operation at this time is read-only when the APP performs a read operation on the first pbuf memory. When the memory performs a write operation, it is determined that the attribute of the read and write operation at this time is write-only.

Optionally, in one embodiment of the present invention, when the APP receives and processes the message through the first pbuf memory, the APP sets the read and write operation attribute of the first pbuf memory to read and write, and in At other times, the APP's read and write operation attribute of the first pbuf memory is read-only. The attributes of read and write operations of the memory are read-only.

Specifically, in one embodiment of the present invention, when the APP receives and processes the preset message through the first pbuf memory, the APP sets the read and write operation attribute of the first pbuf memory to read and write. However, the read and write operation attribute of other APPs to the first pbuf memory is read-only. When the APP sends the preset message to other APPs, the write operation attribute will be withdrawn at this time, that is, the APP will take back the preset message at this time. The read and write operation attribute of the message will be reset to read only. After each APP has set the read and write operation attributes for the first pbuf memory, and the operating system running on the zero-copy system monitors the misoperation of the first pbuf memory by the APP, it will send a pbuf memory misuse notification message. To prompt the user that there is a problem with the first pbuf memory, so that the management of the first pbuf memory can be realized in this way.

For example, in an example of the present invention, please refer to FIG. 6 for details. FIG. 6 is a schematic diagram of a first pbuf memory management process between APP processes provided by an embodiment of the present invention. In the case that the message is forwarded between APP1, APP2 and APP3, when APP1 receives the message through the first pbuf memory at time 1 and processes it, the read and write operation attribute of APP1 to the first pbuf memory is set to Read and write; when APP1 sends the message to the APP2 process, APP2 receives the message at time 2, at this time APP2 will set the read and write operation attribute of the first pbuf memory to read and write, and at this time APP1 will withdraw the first pbuf memory A write operation of the pbuf memory, that is, at this time, the read and write operation attribute of APP1 to the first pbuf memory will be read-only. At these two moments, APP3 does not process the message, so APP3 always sets the read and write operation attribute of the first pbuf memory as read-only.

Further, referring to FIG. 7 , FIG. 7 is a schematic diagram of a message zero-copy process and a first pbuf memory management process provided by an embodiment of the present invention. When the message zero-copy system is used for zero-copy message forwarding, first APP1, APP2 and APP3 set the read and write operation attributes of the first pbuf memory as read-only. APP1 fills the DMA address to the first network card queue, that is, the first pbuf memory address, and the first network card writes the message into the first network card queue after receiving the packet, and then APP1 uses the first pbuf memory from the first network card The message is received in the queue, at this time APP1 will set the read and write operation attribute of the first pbuf memory to read and write; when APP1 finishes processing the message in the first pbuf memory, send the message to APP2 At this time, APP1 takes back the write operation attribute of the first pbuf memory, that is, the read and write operation attribute of the APP1 process to the first pbuf memory is read-only at this time, and at this time APP2 will set the read and write operation attribute of the first pbuf memory The write operation attribute is read and write; after APP2 finishes processing the message, it will send it to the next APP in turn, and the setting method of the read and write operation attribute of the first pbuf memory of each APP is the same as the above steps. After the message is forwarded to APPn, the read and write operation attribute of APPn to the first pbuf memory is read and write. After APPn processes the message, APPn sends the message to APP1 and withdraws the write operation attribute. At this time, after APP1 receives the message, APP1 resets the read and write operation attribute of the first pbuf memory to read and write, and finally APP1 sends the message to the second network card queue, and then the second network card sends the message to the second network card queue Take it out to complete the entire network card sending and receiving packet process. It should be noted that, in the process shown in FIG. 7 , APP1 uniformly manages sending and receiving packets of the network card.

Specifically, in one embodiment of the present invention, when each APP runs on the Linux operating system, the Linux operating system includes an mprotect memory management interface, and the mprotect memory management interface is used to set the read and write operation attributes of the first pbuf memory , that is, when the APP is processing the first pbuf memory message, the APP sets the read and write operation attribute of the APP to the first pbuf memory as read and write by calling the mprotect memory management interface, and other APPs call the mprotect memory management interface to set the right The read and write operation attribute of the first pbuf is read-only, and at this time, the Linux operating system will record the read and write operation attribute of the APP to the memory of the first pbuf. Once an APP whose read-write operation attribute is read-only writes to the first pbuf memory, the Linux system can immediately detect the misoperation of the memory, and then the Linux operating system generates a segment fault signal segmentfault, which is used to prompt the APP to write to the first pbuf If the memory of the device is misoperated, then the APP can prompt and print out the call stack information through the error message to determine the first scene of the abnormal context. It can be understood that by calling the mprotect memory management interface of the Linux operating system, the read and write operation attributes of the first pbuf memory can be conveniently set under the Linux operating system.

Optionally, in one embodiment of the present invention, since the mprotect memory management interface is managed based on the page table, that is, the read and write operation attributes of the corresponding memory on the same page table will be set at the same time, specifically, each page The table includes the read and write operation attribute identification, so that when the operating system records that the APP's read and write operation attribute of the first pbuf memory is read-only, it can record the APP's operation of the first pbuf memory on the read and write operation attribute identification on the page table. The read and write operation attribute is read-only. Since each page table corresponds to a read and write operation attribute identifier, that is, each page table uniformly sets the read and write operation attributes of the pbuf memory corresponding to the page table through the read and write operation attribute identifier. Therefore, when the memory read and write operation management is performed based on the mprotect memory read and write operation management mechanism, in order not to interfere with the page table when the mprotect memory read and write operation management mechanism sets the read and write operation attributes of the first pbuf memory The read and write operation attributes of other memory on the network, so it is necessary to have a unique correspondence between the page table and the first pbuf memory, that is, a page table or multiple page tables corresponding to the first pbuf memory are read and written by mprotect memory The management mechanism controls independently. At this time, the read and write operation attribute identifiers of one or more page tables corresponding to the first pbuf memory will be set to read-only or read-write at the same time.

Optionally, in one embodiment of the present invention, the page table can be a common 4K-bit page table. For example, when the size of the first pbuf memory is within 4K bits, the first pbuf memory corresponds to a page table. When the mprotect memory read and write operation management mechanism independently controls the page table to independently control the read and write operation attributes of the first pbuf memory, specifically, each APP pair can be set by setting the read and write operation attribute identifier of the page table. The read and write operation attributes of the first pbuf, or if the size of the first pbuf memory is 8K bits, the first pbuf memory corresponds to two consecutive page tables. At this time, the mprotect memory read and write operation management mechanism can control the two pages at the same time. The page table is used to independently control the read and write operation attributes of the first pbuf memory. Specifically, the read and write operation attributes of the two page tables can be marked as the same (read-only or read-write at the same time) to independently control the two page tables. Controls the read and write operation properties of the first pbuf memory. It can be understood that by making the first pbuf memory independent from other pbuf memories and uniquely corresponding to the page table, the mprotect memory read and write operation management mechanism based on page table management can independently control the first pbuf memory.

Optionally, in one embodiment of the present invention, the message zero-copy system also includes a second pbuf memory, and the shared memory of APPs also includes a second pbuf memory, and the message zero-copy system uses the shared memory to perform In the case of zero copy, the APP may determine the first pbuf memory as the shared memory of the APPs at a preset time, and the APP determines the second pbuf memory as the shared memory of the APPs outside the preset time , the first pbuf memory is a small page memory, the second pbuf memory is a large page memory, and there is a unique correspondence between the first pbuf memory and the one or more page tables.

Among them, large page memory refers to reducing the number of page tables and improving system performance by increasing the size of page tables. Under large page memory, the size of each page table can be 1G bits or larger, and if the shared memory size of APPs is only 4K bits At this time, each page table will correspond to multiple pbuf memories. Small page memory is a concept opposite to large page memory. Under small page memory, the size of each page table can be a normal 4K-bit page table or an 8K-bit page table.

Optionally, in one embodiment of the present invention, the preset time means that the APP determines based on a preset rule, for example, it may be determined based on a preset sampling period, so that the APP at the preset time corresponding to the preset sampling period Use the first pbuf memory, and use the second pbuf memory at a time other than the preset sampling period; for another example, when the type of the message to be processed by the message zero-copy system is the preset type, use the first pbuf The memory saves the message (that is, it is determined that the current time is the preset time), and when the type of the message to be processed by the message zero-copy system is other types, the second pbuf memory is used to save the message (that is, it is determined that the current time is the preset time). In addition to setting the time), the preset time can be determined based on the type of message that the message zero-copy system will currently process.

Specifically, in one embodiment of the present invention, since the system performance is relatively low under the 4K-bit page table, if the pbuf memory is set as a large page memory, there will be multiple pbuf memories corresponding to the same page table In some cases, if the read and write operations of the current pbuf memory are managed, other pbuf memories in the same page table will be managed by mistake, resulting in abnormal system functions. Therefore, in the case of ensuring system performance and preventing abnormal system functions, you can increase the second pbuf memory and set the second pbuf memory as large page memory, so that APP can receive and process through the first pbuf memory or the second pbuf memory Preset messages to improve system performance. For example, refer to FIG. 8-a, which is a schematic structural diagram of another packet zero-copy system provided by an embodiment of the present invention. However, since the second pbuf memory is a large page memory, the Linux operating system does not manage read and write operations on the second pbuf memory, but only manages read and write operations on the first pbuf memory. The preset sampling period of the first pbuf memory can be set, and the APP process fills the first pbuf memory at the sampling time corresponding to the preset sampling period, and then manages the read and write operations of the first pbuf memory to ensure system reliability. For example, when the preset sampling period of the first pbuf memory is set to 1000, every time 999 second pbuf memories are filled, one first pbuf memory is filled, and Linux performs read and write operation management on the first pbuf memory to ensure that the system Reliability, at the same time, because 999 of the 1000 pbuf memories use the second pbuf memory of the large page memory, the high performance of the system can be guaranteed.

It is worth noting that by setting the preset time when the APP uses the first pbuf memory, the lower the frequency of the preset time is, the lower the frequency of pbuf memory monitoring is, so the system reliability is relatively low at this time, and At this time, the relative frequency of using the large page memory and the second pbuf memory for filling is relatively large, and the performance of the system is greatly improved; and the higher the frequency of the preset time, the greater the frequency of pbuf memory monitoring, so the reliability of the system at this time The performance is relatively large, and at this time, the relative times of filling with the second pbuf memory of the huge page memory is small, and the performance improvement of the system is small. Therefore, the preset time can be set according to the requirements and by weighing the performance improvement and reliability of the system.

Further, referring to FIG. 8-b, FIG. 8-b is a schematic diagram of another packet zero-copy process and pbuf memory management process provided by the embodiment of the present invention. The process shown in Figure 8-b is executed based on the zero packet copy system shown in Figure 8-a, that is, it includes two pbuf memories: the first pbuf memory and the second pbuf memory. Since the first pbuf memory has a one-to-one correspondence with the page table, and the second pbuf memory is a large page memory, the preset sampling cycle is set to sample and fill the first pbuf memory, and only the mprotect memory read and write operation management mechanism is used to control the first pbuf The memory performs read and write operation management, and the second pbuf memory does not perform memory read and write operation management. And in the process shown in Figure 8-b, APP1 uniformly manages sending and receiving packets of the network card. As shown in Figure 8-b, first APP1, APP2 and APP3 set the read and write operation attributes of the first pbuf memory to read-only. When APP1 fills the DAM address in the first network card queue, when it is not the preset sampling period, use the DMA address of the second pbuf memory to fill the first network card queue, so that subsequent APP1 reads from the first network card queue through the second pbuf memory Messages are processed together; when the sampling period is preset, use the DMA address of the first pbuf memory to fill the first network card queue, so that when APP1 reads the message from the first network card queue through the first pbuf memory, due to the first pbuf The memory is the sampling pbuf memory that needs to be set for read and write operation attributes, so APP1 sets the read and write operation attribute of the first pbuf memory to read and write, and processes the message. After processing the message, APP1 takes back the write of the first pbuf memory Manipulate the attributes and send the message to APP2.

When APP2 receives the message sent by APP1, it judges whether the pbuf memory is the first pbuf memory for sampling. The read and write operation attribute of the first pbuf memory is read and write, and the message is processed. After the message is processed, APP2 takes back the write operation attribute of the first pbuf memory, and sends the message to APP3.

When APP3 receives the message sent by APP2, it judges whether the pbuf memory is the first pbuf memory for sampling. The read and write operation attribute of the first pbuf memory is read and write, and the message is processed. After processing the message, APP3 takes back the read operation attribute of the first pbuf memory, and sends the message to APP1.

After APP1 receives the message, if it is judged to be the second pbuf memory, it does not set the read and write operation attributes at this time. After processing the message, it sends the message to the second network card queue and reclaims the second pbuf memory To the pbuf memory pool. In the case of judging that it is the first pbuf memory, set the read and write operation attribute of the first pbuf memory to read and write at this time, and process the message, and then send the message to the second network card queue, and from the second network card Reclaim the first pbuf memory in the queue to the pbuf memory pool, and reclaim the write operation attribute of the first pbuf memory at the same time. In this way, the entire message zero-copy process is completed.

S502. When the operating system monitors that the APP performs a write operation on the first pbuf memory, the operating system sends a pbuf memory misoperation notification message to the APP. At this time, the APP receives the pbuf memory misoperation notification message sent by the operating system, and obtains The pbuf memory misoperation site information in the pbuf memory misoperation notification message, the pbuf memory misoperation notification message is used to instruct the APP to perform a write operation on the first pbuf memory and the specific location of the write operation.

Optionally, in an embodiment of the present invention, the pbuf memory misoperation context information includes call stack information.

Specifically, in one embodiment of the present invention, when the operating system detects that the first pbuf memory is read-only, the APP writes to the first pbuf memory, and then the operating system will send a pbuf memory misoperation to the APP Notification message, for example, the pbuf memory misoperation notification message can be a segment fault signal segment fault, and then the APP prints out the call stack information through the segment fault signal segment fault, so that further, the APP can determine that the memory error is caused according to the call stack information The specific location, and the APP can fix the problem that causes the memory error according to the specific location.

Optionally, in an embodiment of the present invention, the first pbuf memory is also used to cache the trace identifier, and after the APP receives the pbuf memory misoperation notification message, the APP can also pass the trace of the first pbuf memory Identify and record the track point information of the first pbuf memory, the track point information includes the application program APP identification, the application program current process identification and the current time, wherein the APP identification is used to indicate the APP that uses the first pbuf memory at a certain time, The current process identifier of the application program indicates the APP process using the first pbuf memory at a certain moment.

In the embodiment of the present invention, the track point information refers to the relevant information of the APP using the first pbuf memory, so that the relevant information of the APP using the first pbuf is connected in chronological order to form the track point information of the first pbuf memory .

Specifically, in the embodiment of the present invention, the track point information can be recorded through the track mark, wherein the track mark can refer to the memory space used to save the message in the first pbuf memory, so that the remaining memory space can be used to Record the track point information of the first pbuf.

For illustration, see FIG. 4 in one example of the present invention. When the APP1 process receives and processes the first pbuf memory message at the first moment, the APP1 process records the track point information at this time in the remaining memory space of the first pbuf memory, that is, the APP1 ID, the APP2 process ID, and the first moment ; Then after APP1 sends the first memory message to APP2, when the APP2 process receives and processes the first pbuf memory message at the second moment, the APP2 process takes another step to record this time in the remaining space of the first pbuf memory track point information, that is, APP2 ID, APP2 process ID, and the second moment; record all the track point information of the first pbuf memory in turn, so that all tracks of the first pbuf memory from APP1 to APPn will be included in APPn Point information, all the track point information can be obtained according to the time sequence of the track of the first pbuf memory. Furthermore, the track of the first pbuf memory passing through the first network card queue and the second network card queue in the zero-copy system can also be recorded.

It can be understood that after the track point information of the first pbuf is recorded, when a write operation is misused in an APP, the track of the first pbuf determined by the track point information of the first pbuf can be further determined The upstream APP that the first pbuf passes through to further improve system reliability.

S503. The APP determines a memory misoperation site where the APP performs a write operation on the pbuf memory based on the pbuf memory misoperation site information.

Furthermore, in an embodiment of the present invention, service recovery can be performed on-site based on the memory misoperation.

For example, in an example of the present invention, when the message zero-copy system is working, and the first pbuf memory is sent to APP3, at this time APP2 sets the read and write operation attributes of APP2 to the first pbuf memory by calling the mprotect memory management interface It is read-only, APP2 will receive the pbuf memory misoperation notification message sent by the system, such as a segment error signal, and then APP2 will print the call stack information based on the segment error signal, and APP2 will determine the first pbuf based on the call stack information. The location of the write operation, that is, the code location where the erroneous write operation occurs, so that the APP can repair the problem based on this location, and prevent the subsequent APP2 from performing an erroneous write operation on the first pbuf memory. By setting the read and write operation attributes of each APP to the first pbuf memory, when the first pbuf memory runs to APP3, in the case that APP2 performs a write operation on the first pbuf memory, the system can notify through pbuf memory misoperation The message reminds APP2 so that APP2 can locate and modify the first pbuf memory problem in time to ensure system reliability, and also prevent APP3, which is operating the first pbuf memory at the moment, from wasting resources to troubleshoot pbuf memory problems, and further improve system performance.

Furthermore, when the APP performs a wrong write operation on the first pbuf memory, it can record the value stored in the corresponding position of the first pbuf memory before the APP writes to the first pbuf memory, so that when the APP writes to the first pbuf memory When writing by mistake, the value of the corresponding position of the first pbuf memory can be restored to the value before the wrong write, so as to further improve system reliability and system performance, and also improve system robustness.

Furthermore, by recording the track point information of the first pbuf memory, after determining the memory misoperation site where the APP writes to the first pbuf memory, you can further troubleshoot the pbuf memory problem through the upstream APP of the APP to further improve System reliability.

It is worth noting that the above method embodiment can not only be used to monitor the memory misoperation of the first pbuf memory when the read and write operation attribute of the APP to the first pbuf memory is set to read-only. When the APP's read and write operation attribute of the first pbuf memory is set to write-only, and when the APP's read and write operation attribute of the first pbuf memory is set to the read state and write state when reading and writing, the above method can also be used for the first pbuf memory A pbuf memory is used to monitor memory misoperations. Specifically, the use of the above method can be adapted and adjusted according to the operation range corresponding to the read and write operation attributes.

It is worth noting that the above step S501, step S502 and step S503 may also be executed synchronously and in parallel during actual execution, and the embodiment of the present invention does not strictly limit the execution order thereof.

It can be seen that, in the solution of the embodiment of the present invention, when the first pbuf memory is shared by APPs in the zero-copy system running on the operating system, any APP in the APPs sets the APP to read and write operations to the first pbuf memory When the attribute is read-only at the current moment, the operating system records the read and write operation attributes of the APP to the first pbuf memory; then when the operating system monitors that the APP performs a write operation on the first pbuf memory, the operating system sends the pbuf to the APP Memory misoperation notification message. After receiving the pbuf memory misoperation notification message sent by the operating system, the APP obtains the pbuf memory misoperation site information in the pbuf memory misoperation notification message. The pbuf memory misoperation notification message is used to remind all The APP performs a write operation on the first pbuf memory, the write operation, and the specific location of the write operation; finally, the APP determines the memory error of the APP’s write operation on the first pbuf memory based on the site information of the pbuf memory misoperation. Operation site. In this way, when multiple APPs share the same pbuf memory, when a memory misoperation occurs in the shared pbuf memory, the APP and the specific location that caused the pbuf memory misoperation can be quickly and accurately located, that is, the pbuf memory misoperation site can be determined , to improve system performance while ensuring system reliability.

Furthermore, service recovery can be performed on-site based on the misoperation of the pbuf memory, further ensuring system reliability.

Referring to FIG. 9 , FIG. 9 is a schematic structural diagram of an application program APP provided by an embodiment of the present invention, which is used to implement the shared memory management method disclosed in the embodiment of the present invention. Wherein, the APP is applied in a message zero-copy system, and the message zero-copy system runs on an operating system, and the message zero-copy system includes at least two application programs APPs, and the APPs share the first packet cache pbuf Memory, the APP is any APP in the APPs. As shown in Figure 9, an APP provided by an embodiment of the present invention includes:

A setting module 910 , an obtaining module 920 and a determining module 930 .

The setting module 910 is configured to set the read-write operation attribute of the APP to the first pbuf memory as read-only at the current moment.

The acquiring module 920 is configured to acquire the pbuf memory misuse site information in the pbuf memory misuse notification message in the case of receiving the pbuf memory misuse notification message sent by the operating system, the pbuf memory misuse notification message The message is used to remind the APP to perform a write operation on the first pbuf memory and a specific location of the write operation.

The determining module 930 is configured to determine a memory misoperation site where the APP performs a write operation on the first pbuf memory based on the pbuf memory misuse site information.

Optionally, in an embodiment of the present invention, the operating system includes a Linux operating system, and the Linux operating system includes an mprotect memory management interface, and the mprotect memory management interface is used to be called to set the first pbuf The read and write operation attributes of the memory; the setting module 910 is specifically used for:

Setting the read-write operation attribute of the APP to the first pbuf memory as read-only at the current moment by calling the mprotect memory management interface.

Optionally, in an embodiment of the present invention, the mprotect memory management interface is used to be called by the APP to set the read and write operation attributes of the APP to the first pbuf memory based on one or more page tables .

Optionally, in an embodiment of the present invention, the message zero-copy system further includes a second pbuf memory, the APPs share the second pbuf memory, and the APP is configured to correspond to the preset sampling period The first pbuf memory is sampled at a sampling time, and the APP is configured to sample the second pbuf memory outside of the sampling time.

Optionally, in an embodiment of the present invention, the message zero-copy system further includes a second pbuf memory, the shared memory of APPs includes the second pbuf memory, and the determination module 930 is also used for all Before any application program APP in the APPs sets the read and write operation attribute of the APP to the first pbuf memory as read-only information at the current moment, determine the first pbuf memory as the APPs at the preset time The shared memory, the APP determines that the second pbuf memory is the shared memory of the APPs outside the preset time, the first pbuf memory is a small page memory, and the second pbuf memory is a large page memory , there is a unique correspondence between the first pbuf memory and the one or more page tables.

Optionally, in one embodiment of the present invention, the APP900 further includes a recording module 940, configured to record the track point information of the first pbuf memory through the track ID, the track point information including the application program ID , the current process identifier of the application program and the current time.

It can be seen that, in the solution of the embodiment of the present invention, when the first pbuf memory is shared by APPs in the zero-copy system running on the operating system, any APP in the APPs sets the APP to read and write operations to the first pbuf memory When the attribute is read-only at the current moment, the operating system records the read and write operation attributes of the APP to the first pbuf memory; then when the operating system monitors that the APP performs a write operation on the first pbuf memory, the operating system sends the pbuf to the APP Memory misoperation notification message. After receiving the pbuf memory misoperation notification message sent by the operating system, the APP obtains the pbuf memory misoperation site information in the pbuf memory misoperation notification message. The pbuf memory misoperation notification message is used to remind all The APP performs a write operation on the first pbuf memory, the write operation, and the specific location of the write operation; finally, the APP determines the memory error of the APP’s write operation on the first pbuf memory based on the site information of the pbuf memory misoperation. Operation site. In this way, when multiple APPs share the same pbuf memory, when a memory misoperation occurs in the shared pbuf memory, the APP and the specific location that caused the pbuf memory misoperation can be quickly and accurately located, that is, the pbuf memory misoperation site can be determined , to improve system performance while ensuring system reliability.

Furthermore, service recovery can be performed on-site based on the misoperation of the pbuf memory, further ensuring system reliability.

In this embodiment, the application program APP900 is presented in the form of modules. The "module" here may refer to an application-specific integrated circuit (ASIC), a processor and memory executing one or more software or firmware programs, an integrated logic circuit, and/or other devices that can provide the above functions .

It can be understood that the functions of each functional unit of the application program APP900 in this embodiment can be specifically implemented according to the method in the above method embodiment, and the specific implementation process can refer to the relevant description of the above method embodiment, and will not be repeated here.

Referring to FIG. 10 , FIG. 10 is a schematic structural diagram of an operating system provided by an embodiment of the present invention, which is used to implement the shared memory management method disclosed in the embodiment of the present invention. Wherein, a message zero-copy system runs on the operating system, and the message zero-copy system includes at least two application programs APPs, and the APPs share the first message cache pbuf memory, as shown in Figure 10, the present invention An operating system 1000 provided in an embodiment includes:

A recording module 1010 and a sending module 1020 .

Wherein, the recording module 1010 is used to set an instruction to record the read and write operation attribute of the APP to the first pbuf memory according to any application program APP in the APPs to the read and write operation attribute of the first pbuf memory. read only;

The sending module 1020 is configured to send a pbuf memory misoperation notification message to the APP when the operating system monitors that the APP performs a write operation on the first pbuf memory, and the pbuf memory The misoperation notification message is used to remind the APP to perform a write operation on the first pbuf memory and a specific location of the write operation.

Optionally, in an embodiment of the present invention, the operating system includes a Linux operating system, and the Linux operating system includes an mprotect memory management interface, and the mprotect memory management interface is used to be called by the APP to set the The attributes of the APP's read and write operations on the first pbuf memory.

Optionally, in an embodiment of the present invention, the mprotect memory management interface is used to be called by the APP to set the read and write operation attributes of the APP to the first pbuf memory based on one or more page tables .

Optionally, in an embodiment of the present invention, the page table includes a read-write operation attribute identifier, and the recording module 1010 records that the APP's read-write operation attribute of the first pbuf memory is read-only includes:

The read-write operation attribute of the APP to the first pbuf memory is read-only recorded through the read-write operation attribute identification.

It can be seen that, in the solution of the embodiment of the present invention, when the first pbuf memory is shared by APPs in the zero-copy system running on the operating system, any APP in the APPs sets the APP to read and write operations to the first pbuf memory When the attribute is read-only at the current moment, the operating system records the read and write operation attributes of the APP to the first pbuf memory; then when the operating system monitors that the APP performs a write operation on the first pbuf memory, the operating system sends the pbuf to the APP Memory misoperation notification message. After receiving the pbuf memory misoperation notification message sent by the operating system, the APP obtains the pbuf memory misoperation site information in the pbuf memory misoperation notification message. The pbuf memory misoperation notification message is used to remind all The APP performs a write operation on the first pbuf memory, the write operation, and the specific location of the write operation; finally, the APP determines the memory error of the APP’s write operation on the first pbuf memory based on the site information of the pbuf memory misoperation. Operation site. In this way, when multiple APPs share the same pbuf memory, when a memory misoperation occurs in the shared pbuf memory, the APP and the specific location that caused the pbuf memory misoperation can be quickly and accurately located, that is, the pbuf memory misoperation site can be determined , to improve system performance while ensuring system reliability.

Furthermore, service recovery can be performed on-site based on the misoperation of the pbuf memory, further ensuring system reliability.

In this embodiment, the operating system 1000 is presented in the form of modules. The "module" here may refer to an application-specific integrated circuit (ASIC), a processor and memory executing one or more software or firmware programs, an integrated logic circuit, and/or other devices that can provide the above functions .

It can be understood that the functions of each functional unit of the operating system 1000 in this embodiment can be specifically implemented according to the method in the above method embodiment, and the specific implementation process can refer to the relevant description of the above method embodiment, and will not be repeated here.

Referring to FIG. 11, FIG. 11 is a schematic structural diagram of a shared memory management device provided by an embodiment of the present invention. As shown in FIG. 11, the shared memory management device 1100 includes:

A memory 1101 storing executable program codes and a processor 1102 coupled to the memory. The memory 1101 may exist independently and be connected to the processor 1102 through a bus. The memory 1101 may also be integrated with the processor 1102 . Wherein, the processor 1102 may be a central processing unit (Central Processing Unit, CPU), and an application program APP and an operating system run on the processor 1102, and a message zero-copy system runs on the operating system, and the The message zero-copy system includes at least two application programs APPs, the APPs share the memory of the first packet cache pbuf, and the APPs are any APPs in the APPs.

The APP is used to: set the read-write operation attribute of the APP to the first pbuf memory to be read-only at the current moment; when the APP receives the pbuf memory misoperation notification message sent by the operating system Obtaining the pbuf memory misoperation site information in the pbuf memory misoperation notification message, the pbuf memory misoperation notification message is used to remind the APP to perform a write operation on the first pbuf memory and the details of the write operation Location: determine the memory misuse site where the APP performs a write operation on the first pbuf memory based on the pbuf memory misuse site information.

Optionally, in an embodiment of the present invention, the operating system includes a Linux operating system, and the Linux operating system includes an mprotect memory management interface, and the mprotect memory management interface is used to be called to set the first pbuf The read and write operation properties of the memory;

The setting of the read-write operation attribute of the APP to the first pbuf memory is read-only at the current moment, including:

Setting the read-write operation attribute of the APP to the first pbuf memory as read-only at the current moment by calling the mprotect memory management interface.

Optionally, in an embodiment of the present invention, the mprotect memory management interface is used to be called by the APP to set the read and write operation attributes of the APP to the first pbuf memory based on one or more page tables .

Optionally, in an embodiment of the present invention, before setting the read-write operation attribute of the APP to the first pbuf memory as read-only at the current moment, the APP is further used to:

Determine that the first pbuf memory is the shared memory of the APPs at a preset time, determine that the second pbuf memory is a shared memory of the APPs outside the preset time, and the first pbuf memory is small page memory, the second pbuf memory is a large page memory, and there is a unique correspondence between the first pbuf memory and the one or more page tables.

Optionally, in an embodiment of the present invention, the first pbuf memory is also used for caching track identifiers, and the APP is also used for: recording track point information of the first pbuf memory through the track identifiers, The track point information includes the application identifier, the current process identifier of the application, and the current time.

It should be noted that FIG. 11 only shows a simplified design of the shared memory management device 1100 . In practical applications, the shared memory management device 1100 may include any number of processors and memories, and all shared memory management devices that can implement the embodiments of the present invention are within the protection scope of the embodiments of the present invention.

Referring to FIG. 12, FIG. 12 is a schematic structural diagram of another shared memory management device provided by an embodiment of the present invention. As shown in FIG. 12, the shared memory management device 1200 includes:

A memory 1201 storing executable program codes and a processor 1202 coupled to the memory. The memory 1201 can exist independently, and is connected to the processor 1202 through a bus. The memory 1201 can also be integrated with the processor 1202 . Wherein, the processor 1202 can be a central processing unit CPU, an application program APP and an operating system run on the processor 1202, a message zero-copy system runs on the operating system, and the message zero-copy system includes At least two application programs APPs, the APPs share the first packet cache pbuf memory, and the APP is any APP in the APPs.

The operating system is used for: according to any application program APP in the APPs, the read and write operation attribute of the first pbuf memory is set to indicate that the read and write operation attribute of the APP to the first pbuf memory is set as only Read; when the operating system monitors that the APP performs a write operation on the first pbuf memory, send a pbuf memory misuse notification message to the APP, and the pbuf memory misuse notification message is used to remind all The APP performs a write operation on the first pbuf memory and the specific location of the write operation.

Optionally, in an embodiment of the present invention, the operating system includes a Linux operating system, and the Linux operating system includes an mprotect memory management interface, and the mprotect memory management interface is used to be called by the APP to set the The attributes of the APP's read and write operations on the first pbuf memory.

Optionally, in an embodiment of the present invention, the mprotect memory management interface is used to be called by the APP to set the read and write operation attributes of the first pbuf memory based on one or more page tables.

Optionally, in an embodiment of the present invention, the page table includes a read-write operation attribute identifier, and the recording module records that the APP's read-write operation attribute of the first pbuf memory is read-only includes:

The read-write operation attribute of the APP to the first pbuf memory is marked and recorded as read-only.

It should be noted that FIG. 12 only shows a simplified design of the shared memory management device 1200 . In practical applications, the shared memory management device 1200 may include any number of processors and memories, and all shared memory management devices that can implement the embodiments of the present invention are within the protection scope of the embodiments of the present invention.

Referring to FIG. 13, FIG. 13 is a schematic structural diagram of a shared memory management device provided by an embodiment of the present invention. As shown in FIG. 13, the shared memory management device 1300 includes:

A memory 1301 storing executable program codes and a processor 1302 coupled to the memory. Wherein, the processor 1101 may be a central processing unit (Central Processing Unit, CPU), and the APP and the operating system in the method embodiment shown in FIG. 5 may be run on the processor, or the APP and the operating system in the device embodiment shown in FIG. The APP and the operating system in the device embodiment shown in FIG. 10, or the APP in the device embodiment shown in FIG. 11 and the operating system in the device embodiment shown in FIG. 12 are used to execute the Shared memory management method. Wherein, a message zero-copy system runs on the operating system, and the message zero-copy system includes at least two application programs APPs, and the APPs share the first packet cache pbuf memory, and the APPs are the ones in the APPs Any APP. The memory 1301 is used for storing APP program codes and data, and for storing operating system program codes and data. The memory 1301 may exist independently and be connected to the processor 1302 through a bus. The memory 1301 can also be integrated with the processor 1302 .

It can be understood that FIG. 13 only shows a simplified design of the shared memory management device 1300 . In practical applications, the shared memory management device 1300 may include any number of processors and memories, and all shared memory management devices that can implement the embodiments of the present invention are within the protection scope of the embodiments of the present invention.

An embodiment of the present invention also provides a computer storage medium, wherein the computer storage medium can store a program, and when the program is executed, some or all steps including any shared memory management method described in the above method embodiments can be implemented. The aforementioned storage medium includes: U disk, read-only memory (English: read-only memory), random access memory (English: random access memory, RAM), mobile hard disk, magnetic disk or optical disk, etc., which can store program codes. medium.

It should be noted that for the foregoing method embodiments, for the sake of simple description, they are expressed as a series of action combinations, but those skilled in the art should know that the present invention is not limited by the described action sequence. Because of the present invention, certain steps may be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification belong to preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.

In the foregoing embodiments, the descriptions of each embodiment have their own emphases, and for parts not described in detail in a certain embodiment, reference may be made to relevant descriptions of other embodiments.

In the several embodiments provided in this application, it should be understood that the disclosed device can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or can be Integrate into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical or other forms.

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 may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

As mentioned above, the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: it can still understand the foregoing The technical solutions recorded in each embodiment are modified, or some of the technical features are replaced equivalently; and these modifications or replacements do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.

Claims (19)

1. A shared memory management method, characterized in that, the method is applied in a message zero-copy system, the message zero-copy system runs on an operating system, and the message zero-copy system includes at least two applications Program APPs, the shared memory of the APPs includes the first packet cache pbuf memory, and the method includes: Any application program APP in the APPs sets the read-write operation attribute of the APP to the first pbuf memory to be read-only at the current moment; When the APP receives the pbuf memory misoperation notification message sent by the operating system, it obtains the pbuf memory misoperation site information in the pbuf memory misoperation notification message, and the pbuf memory misoperation notification message is used for Reminding the APP to perform a write operation on the first pbuf memory and the specific location of the write operation; Based on the pbuf memory misoperation site information, determine a memory misoperation site where the APP performs a write operation on the first pbuf memory. 2. The method according to claim 1, wherein the operating system includes a Linux operating system, and the Linux operating system includes an mprotect memory management interface, and the mprotect memory management interface is used to be called to set the first A read and write operation attribute of pbuf memory; Any application program APP in the APPs sets the read-write operation attribute of the APP to the first pbuf memory as read-only at the current moment, including: The APP sets the read-write operation attribute of the APP to the first pbuf memory as read-only at the current moment by calling the mprotect memory management interface. 3. The method according to claim 2, wherein the mprotect memory management interface is used to be called by the APP to set the reading and writing of the first pbuf memory by the APP based on one or more page tables Action properties. 4. The method according to claim 3, wherein the message zero-copy system also includes a second pbuf memory, and the shared memory of the APPs includes the second pbuf memory, any of the APPs Before an application program APP sets the read and write operation attribute of the APP to the first pbuf memory as read-only at the current moment, the method also includes: The APP determines that the first pbuf memory is the shared memory of the APPs at a preset time, and the APP determines that the second pbuf memory is the shared memory of the APPs outside the preset time, and the APP determines that the second pbuf memory is the shared memory of the APPs. The first pbuf memory is a small page memory, the second pbuf memory is a large page memory, and there is a unique correspondence between the first pbuf memory and the one or more page tables. 5. The method according to any one of claims 1 to 4, wherein the first pbuf memory is also used to cache track identification, and the method further comprises: The APP records track point information in the first pbuf memory through the track ID, and the track point information includes the application ID, the current process ID of the application, and the current time. 6. A shared memory management method, characterized in that, the method is applied to an operating system, and a message zero-copy system runs on the operating system, and the message zero-copy system includes at least two application programs APPs, so The shared memory of APPs includes the first packet cache pbuf memory, and the method includes: The operating system sets an instruction to record the APP's read-write operation attribute to the first pbuf memory according to any application program APP in the APPs to the read-write operation attribute of the first pbuf memory; When the operating system monitors that the APP performs a write operation on the first pbuf memory, the operating system sends a pbuf memory misoperation notification message to the APP, and the pbuf memory misoperation notification message is used for Reminding the APP to perform a write operation on the first pbuf memory and a specific location of the write operation. 7. The method according to claim 6, wherein the operating system includes a Linux operating system, the Linux operating system includes an mprotect memory management interface, and the mprotect memory management interface is used to be called by the APP to set The attributes of the APP's read and write operations on the first pbuf memory. 8. The method according to claim 7, wherein the mprotect memory management interface is used to be called by the APP to set the reading and writing of the first pbuf memory by the APP based on one or more page tables Action properties. 9. The method according to claim 8, wherein the page table includes a read-write operation attribute identifier, and the operating system records that the APP read-write operation attribute of the first pbuf memory is read-only and includes : The operating system marks and records the read-write operation attribute of the APP on the first pbuf memory as read-only through the read-write operation attribute. 10. A shared memory management device, characterized in that the device comprises: a memory storing executable program code; a processor coupled to the memory; An application program APP and an operating system run on the processor, a message zero-copy system runs on the operating system, and the message zero-copy system includes at least two application programs APPs, and the APPs share the first packet cache pbuf memory, the APP is any APP in the APPs, and the APP is used for: Setting the read and write operation attribute of the APP to the first pbuf memory is read-only at the current moment; When the APP receives the pbuf memory misoperation notification message sent by the operating system, it obtains the pbuf memory misoperation site information in the pbuf memory misoperation notification message, and the pbuf memory misoperation notification message is used for Reminding the APP to perform a write operation on the first pbuf memory and the specific location of the write operation; Based on the pbuf memory misoperation site information, determine a memory misoperation site where the APP performs a write operation on the first pbuf memory. 11. The shared memory management device according to claim 10, wherein the operating system includes a Linux operating system, the Linux operating system includes an mprotect memory management interface, and the mprotect memory management interface is used to be called to set The read and write operation attributes of the first pbuf memory; The setting of the read-write operation attribute of the APP to the first pbuf memory is read-only at the current moment, including: Setting the read-write operation attribute of the APP to the first pbuf memory as read-only at the current moment by calling the mprotect memory management interface. 12. The shared memory management device according to claim 11, wherein the mprotect memory management interface is used to be called by the APP to set the first pbuf memory of the APP based on one or more page tables The read and write operation properties. 13. The shared memory management device according to claim 12, wherein, before the setting of the read-write operation attribute of the APP to the first pbuf memory is read-only at the current moment, the APP also uses At: Determine that the first pbuf memory is the shared memory of the APPs at a preset time, determine that the second pbuf memory is a shared memory of the APPs outside the preset time, and the first pbuf memory is small page memory, the second pbuf memory is a large page memory, and there is a unique correspondence between the first pbuf memory and the one or more page tables. 14. The shared memory management device according to any one of claims 10 to 13, wherein the first pbuf memory is also used for caching trace identification, and the APP is also used for: The track point information of the first pbuf memory is recorded through the track ID, and the track point information includes the application program ID, the current process ID of the application program, and the current time. 15. A shared memory management device, characterized in that the device comprises: a memory storing executable program code; a processor coupled to the memory; An application program APP and an operating system run on the processor, a message zero-copy system runs on the operating system, and the message zero-copy system includes at least two application programs APPs, and the APPs share the first message Cache the pbuf memory, the APP is any APP in the APPs, and the operating system is used for: According to any application program APP in the APPs, the read-write operation attribute of the first pbuf memory is set to indicate that the APP is read-only to the read-write operation attribute of the first pbuf memory; When the operating system monitors that the APP performs a write operation on the first pbuf memory, it sends a pbuf memory misoperation notification message to the APP, and the pbuf memory misoperation notification message is used to remind the APP Perform a write operation on the first pbuf memory and a specific location of the write operation. 16. The shared memory management device according to claim 15, wherein the operating system includes a Linux operating system, the Linux operating system includes an mprotect memory management interface, and the mprotect memory management interface is used to be used by the APP Called to set the attributes of the APP's read and write operations on the first pbuf memory. 17. The shared memory management device according to claim 16, wherein the mprotect memory management interface is used to be called by the APP to set the read and write operations of the first pbuf memory based on one or more page tables Attributes. 18. The shared memory management device according to claim 17, wherein the page table includes a read-write operation attribute identifier, and the recording module records the read-write operation attribute of the APP to the first pbuf memory as Read-only includes: The read-write operation attribute of the APP to the first pbuf memory is marked and recorded as read-only. 19. A shared memory management device, characterized in that the shared memory management device comprises: a memory storing executable program code; a processor coupled to the memory; An application program APP and an operating system run on the processor, a message zero-copy system runs on the operating system, and the message zero-copy system includes at least two application programs APPs, and the APPs share the first message Cache the pbuf memory, and the APP is any APP in the APPs; The APP is used to execute the shared memory management method described in any one of claims 1 to 5; The operating system is used to execute the shared memory management method described in any one of claims 6-9.