CN107454018B - Method and device for processing exception of message cache manager - Google Patents
Method and device for processing exception of message cache manager Download PDFInfo
- Publication number
- CN107454018B CN107454018B CN201710740504.0A CN201710740504A CN107454018B CN 107454018 B CN107454018 B CN 107454018B CN 201710740504 A CN201710740504 A CN 201710740504A CN 107454018 B CN107454018 B CN 107454018B
- Authority
- CN
- China
- Prior art keywords
- cache
- message
- address
- unit
- message cache
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/90—Buffering arrangements
- H04L49/9015—Buffering arrangements for supporting a linked list
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a method and a device for processing message cache manager exception, wherein the method comprises the following steps: if detecting that a first message cache unit of a message cache manager is released repeatedly and determining that the first message cache unit is a management cache, forbidding the message cache manager; deleting the address of the first message cache unit and the address of the management cache in the first message cache unit from a management cache address linked list of the message cache manager; establishing a second message cache unit according to the address of the data cache in the first message cache unit, and adding the address of the second message cache unit into the management cache address linked list; and starting the message cache manager. The scheme eliminates the abnormity of the message cache manager caused by the repeated release of the first message cache unit, and avoids the message cache manager from being crashed due to the rewriting of the information in the management cache.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for processing an exception of a message cache manager.
Background
At present, a Central Processing Unit (CPU) is usually adopted in a network device, and a message cache manager (FPA) may be integrated on the CPU to provide a management service of message cache for a network acceleration module and a software module on the CPU. The message cache manager comprises a plurality of message cache units, the message cache units can be divided into a management cache and a data cache, if the message cache units are management caches, the first 128 bytes of the message cache units can store 32 addresses, the first 31 bytes are addresses of the data cache, and the 32 th byte is an address of the next management cache.
The software module can apply for the message cache unit from the message cache manager, and can also release the message cache unit to the message cache manager, when the software module has an error, the phenomenon that the message cache unit is repeatedly released can occur: after the message cache unit A is released, the message cache unit A is applied to be used as a management cache, the message cache unit A is released again due to the error of the software module, if the message cache unit A is applied again, the information in the message cache unit A is rewritten, and once the information in the message cache unit A is rewritten, the message cache manager is crashed. However, currently, there is no method for handling the exception of the message cache manager.
Disclosure of Invention
The embodiment of the invention provides a method and a device for processing an exception of a message cache manager, which are used for processing the exception of the message cache manager.
According to an embodiment of the present invention, a method for handling an exception of a message cache manager is provided, including:
if detecting that a first message cache unit of a message cache manager is released repeatedly and determining that the first message cache unit is a management cache, forbidding the message cache manager;
deleting the address of the first message cache unit and the address of the management cache in the first message cache unit from a management cache address linked list of the message cache manager;
establishing a second message cache unit according to the address of the data cache in the first message cache unit, and adding the address of the second message cache unit into the management cache address linked list;
and starting the message cache manager.
Specifically, deleting the address of the first packet cache unit from the management cache address linked list of the packet cache manager specifically includes:
finding a third message cache unit and a fourth message cache unit according to a management cache address linked list of the message cache, wherein the address of the management cache in the third cache unit is the address of the first message cache unit, and the address of the management cache in the first message cache unit is the address of the fourth message cache unit;
and updating the address of the management cache in the third message cache unit to the address of the fourth message cache unit.
Specifically, establishing a second packet cache unit according to the address of the data cache in the first packet cache unit, and adding the address of the second packet cache unit to the management cache address linked list includes:
reserving the address of the data cache in the first message cache unit, and clearing the address of the management cache in the first message cache unit to obtain a second message cache unit;
and updating the address of the management cache in the last message cache unit in the management cache address linked list to the address of the second message cache unit.
Optionally, the method further includes:
determining whether the first message cache unit contains a data cache identifier;
if the first message cache unit is determined to contain the data cache identification, determining that the first message cache unit is a data cache;
and if the first message cache unit is determined not to contain the data cache identification, determining that the first message cache unit is a management cache.
Optionally, the method further includes:
if the first message cache unit is repeatedly released and the first message cache unit is determined to be a data cache, searching a fifth message cache unit containing the address of the first message cache unit, wherein the fifth message cache unit is a management cache;
deleting the address of the first message cache unit from the fifth message cache unit;
and acquiring a sixth message cache unit, and storing the address of the first message cache unit in the sixth message cache unit, wherein the sixth message cache unit is a management cache.
According to an embodiment of the present invention, there is also provided a device for handling an exception of a packet cache manager, including:
the disabling module is used for disabling the message cache manager if detecting that a first message cache unit of the message cache manager is released repeatedly and determining that the first message cache unit is a management cache;
a first deleting module, configured to delete the address of the first packet caching unit and the address of the management cache in the first packet caching unit from a management cache address linked list of the packet caching manager;
the establishing module is used for establishing a second message cache unit according to the address of the data cache in the first message cache unit and adding the address of the second message cache unit into the management cache address linked list;
and the starting module is used for starting the message cache manager.
Specifically, the first deleting module is specifically configured to:
finding a third message cache unit and a fourth message cache unit according to a management cache address linked list of the message cache, wherein the address of the management cache in the third cache unit is the address of the first message cache unit, and the address of the management cache in the first message cache unit is the address of the fourth message cache unit;
and updating the address of the management cache in the third message cache unit to the address of the fourth message cache unit.
Specifically, the establishing module is specifically configured to:
reserving the address of the data cache in the first message cache unit, and clearing the address of the management cache in the first message cache unit to obtain a second message cache unit;
and updating the address of the management cache in the last message cache unit in the management cache address linked list to the address of the second message cache unit.
Optionally, the method further includes a determining module, configured to:
determining whether the first message cache unit contains a data cache identifier;
if the first message cache unit is determined to contain the data cache identification, determining that the first message cache unit is a data cache;
and if the first message cache unit is determined not to contain the data cache identification, determining that the first message cache unit is a management cache.
Optionally, the method further includes:
a searching module, configured to search a fifth packet cache unit including an address of the first packet cache unit if it is detected that the first packet cache unit is repeatedly released and it is determined that the first packet cache unit is a data cache, where the fifth packet cache unit is a management cache;
a second deleting module, configured to delete the address of the first packet caching unit from the fifth packet caching unit;
the acquisition module is used for acquiring a sixth message cache unit, and storing the address of the first message cache unit in the sixth message cache unit, wherein the sixth message cache unit is a management cache.
The invention has the following beneficial effects:
the embodiment of the invention provides a method and a device for processing abnormity of a message cache manager, wherein if a first message cache unit of the message cache manager is repeatedly released and the first message cache unit is determined to be a management cache, the message cache manager is forbidden; deleting the address of the first message cache unit and the address of the management cache in the first message cache unit from a management cache address linked list of the message cache manager; establishing a second message cache unit according to the address of the data cache in the first message cache unit, and adding the address of the second message cache unit into the management cache address linked list; and starting the message cache manager. In the scheme, whether the message cache unit in the message cache manager is repeatedly released can be monitored in real time, if the first message cache unit is repeatedly released is detected, whether the first message cache unit is a management cache is determined, if the first message cache unit is the management cache, the abnormal condition that the management cache in the message cache manager is repeatedly released is determined, in order to avoid the message cache manager from being crashed, the message cache manager is forbidden, the address of the first message cache unit and the address of the management cache in the first message cache unit are deleted from the management cache address chain table of the message cache manager, and after the second message cache unit is reestablished according to the address of the data cache in the first message cache unit and the management cache address chain table is updated, the message cache manager is started again, so that the abnormal condition of the message cache manager caused by the repeated release of the first message cache unit is eliminated, the message cache manager is prevented from being crashed due to the fact that information in the management cache is rewritten.
Drawings
FIG. 1 is a flowchart of a method for handling exceptions in a message cache manager according to an embodiment of the present invention;
FIG. 2 is a flowchart of S12 in an embodiment of the present invention;
FIG. 3 is a flowchart of S13 in an embodiment of the present invention;
FIG. 4 is a flowchart of another method for handling exceptions in a message cache manager according to an embodiment of the present invention;
FIG. 5 is a flowchart of a method for handling exceptions in a message cache manager according to another embodiment of the present invention;
fig. 6 is a schematic structural diagram of a device for handling an exception of a message cache manager according to an embodiment of the present invention.
Detailed Description
In order to implement processing of an exception of a message cache manager, an embodiment of the present invention provides a method for processing an exception of a message cache manager, which may be implemented in a software manner or a hardware manner, where a flow of the method is shown in fig. 1, and the method includes the following steps:
s11: and if the first message cache unit of the message cache manager is detected to be released repeatedly and the first message cache unit is determined to be the management cache, the message cache manager is forbidden.
The method can monitor whether each message cache unit in the message cache manager is repeatedly released or not in real time, if the message cache unit is detected to be repeatedly released, the message cache unit can be defined as a first message cache unit, whether the first message cache unit is a management cache or not can be further determined, and if the first message cache unit is the management cache is monitored, the message cache manager is forbidden firstly to avoid the first message cache manager from being broken down.
The process of determining whether the first message cache unit is a management cache is as follows: determining whether the first message cache unit contains a data cache identifier; and if the first message cache unit is determined not to contain the data cache identification, determining that the first message cache unit is a management cache. The data cache identification can be set according to actual needs.
S12: and deleting the address of the first message cache unit and the address of the management cache in the first message cache unit from the management cache address linked list of the message cache manager.
Because the message cache units in the message cache manager can be used as a management cache or a data cache, the first 128 bytes of the message cache units used as the management cache can store 32 addresses, the first 31 addresses are addresses of the data cache, and the 32 th address is the address of the next management cache, so that the management caches can form a management cache address linked list, the address of each message cache unit and the address of the management cache in the message cache unit are recorded in the management cache address list, and the address of the management cache in the message cache unit is the address of the next message cache unit used as the management cache.
Since the first packet cache unit has been released repeatedly and is a management cache, the address in the first packet cache unit is at risk of being rewritten again, and after the packet cache manager is disabled, the address of the first packet cache unit and the address of the management cache in the first packet cache unit need to be deleted from the management cache address linked list.
S13: and establishing a second message cache unit according to the address of the data cache in the first message cache unit, and adding the address of the second message cache unit into the management cache address linked list.
In order to store the address of the data cache in the first packet cache unit, after deleting the address of the first packet cache unit and the address of the management cache in the first packet cache unit from the management cache address linked list, a new packet cache unit needs to be established according to the address of the data cache in the first packet cache unit, where the packet cache unit is defined as a second packet cache unit, and the management cache address linked list is further updated.
S14: the message cache manager is enabled.
The address of the first message cache unit and the address of the management cache in the first message cache unit are deleted from the management cache address linked list of the message cache manager, and after the second message cache unit is established according to the address of the data cache in the first message cache unit and the management cache address linked list is updated, the risk of the message cache manager crash caused by the fact that the first message cache unit is released again can be eliminated, and therefore the message cache manager can be started.
In the scheme, whether the message cache unit in the message cache manager is repeatedly released can be monitored in real time, if the first message cache unit is repeatedly released is detected, whether the first message cache unit is a management cache is determined, if the first message cache unit is the management cache, the abnormal condition that the management cache in the message cache manager is repeatedly released is determined, in order to avoid the message cache manager from being crashed, the message cache manager is forbidden, the address of the first message cache unit and the address of the management cache in the first message cache unit are deleted from the management cache address chain table of the message cache manager, and after the second message cache unit is reestablished according to the address of the data cache in the first message cache unit and the management cache address chain table is updated, the message cache manager is started again, so that the abnormal condition of the message cache manager caused by the repeated release of the first message cache unit is eliminated, the message cache manager is prevented from being crashed due to the fact that information in the management cache is rewritten.
Specifically, the deleting the address of the first packet caching unit from the management caching address linked list of the packet caching manager in S12, where the implementation process is as shown in fig. 2, and specifically includes:
s121: and finding out a third message cache unit and a fourth message cache unit according to the management cache address linked list of the message cache.
S122: and updating the address of the management cache in the third message cache unit to the address in the fourth message cache unit.
Because the message cache unit in the message cache manager can be used as a management cache or a data cache, 32 addresses can be stored in the first 128 bytes of the message cache unit used as the management cache, the first 31 addresses are addresses of the data cache, and the 32 th address is the address of the next management cache, a third message cache unit and a fourth message cache unit can be found from a management cache address chain table of the message cache manager, wherein the address of the management cache in the third cache unit is the address of the first message cache unit, and the address of the management cache in the first message cache unit is the address of the fourth message cache unit; then, the address of the management cache in the third message cache unit is updated to the address in the fourth message cache unit, and the address of the first message cache unit and the address of the management cache in the first message cache unit do not exist in the management cache address linked list.
Specifically, in the above S13, establishing the second packet caching unit according to the address of the data cache in the first packet caching unit, and adding the address of the second packet caching unit to the management cache address linked list, where the implementation process is as shown in fig. 3, specifically including:
s131: and reserving the address of the data cache in the first message cache unit, and clearing the address of the management cache in the first message cache unit to obtain a second message cache unit.
S132: and updating the address of the management cache in the last message cache unit in the management cache address linked list into the address of the second message cache unit.
Because the address of the first message buffer unit and the address of the management buffer in the first message buffer unit are deleted from the management buffer address linked list, the address of the data buffer in the first message buffer unit can be directly reserved, the address of the management buffer in the first message buffer unit is emptied, the second message buffer unit is obtained, then the address of the management buffer in the last message buffer in the management buffer address linked list is updated to the address of the second message buffer unit, because the address of the management buffer in the second message buffer unit becomes the address of the management buffer in the last message buffer in the management buffer address linked list, the address of the management buffer in the second message buffer unit is empty, and when the address of the management buffer in other message buffer units becomes the address of the management buffer in the last message buffer in the management buffer address linked list, and updating the address of the management cache in the second message cache unit.
In the above description, the processing method that the first packet caching unit is a management cache is described, and the processing method that the first packet caching unit is a data cache is described below, as shown in fig. 4, the following steps are executed:
s41: and if the first message cache unit is detected to be released repeatedly and the first message cache unit is determined to be the data cache, searching a fifth message cache unit containing the address of the first message cache unit, wherein the fifth message cache unit is a management cache.
The method can monitor whether each message cache unit in the message cache manager is repeatedly released or not in real time, if the message cache unit in the message cache manager is detected to be repeatedly released, the message cache unit can be defined as a first message cache unit, whether the first message cache unit is a data cache or not can be further determined, if the first message cache unit is monitored to be the data cache, the message cache manager does not need to be forbidden, a management cache containing the address of the first message cache unit is searched, and the management cache is defined as a fifth message cache unit.
The process of determining whether the first message cache unit is a management cache is as follows: determining whether the first message cache unit contains a data cache identifier; and if the first message cache unit is determined to contain the data cache identification, determining that the first message cache unit is a data cache. The data cache identification can be set according to actual needs.
S42: and deleting the address of the first message cache unit from the fifth message cache unit.
S43: and acquiring a sixth message cache unit, and storing the address of the first message cache unit in the sixth message cache unit, wherein the sixth message cache unit is a management cache.
Since the first packet cache unit is repeatedly released and is a data cache, the first packet cache unit has a risk of being rewritten, and the address of the first packet cache unit may be deleted from the fifth packet cache unit, and then the address of the first packet cache unit is stored in a new management cache defined as a sixth packet cache unit.
The processing method of the exception of the message cache manager when the first message cache unit is the data cache can be realized through S41-S43.
The following describes the method for handling the exception of the message cache manager in a specific embodiment, as shown in fig. 5, the following steps are executed:
s51: the process begins.
S52: detecting whether the message cache unit in the message cache manager is released repeatedly, and if detecting that the first message cache unit is released repeatedly, executing S53; if it is not detected that the message cache unit in the message cache manager is released repeatedly, S52 is executed.
S53: determining whether the first message cache unit contains a data cache identifier; if the first message cache unit is determined to contain the data cache identifier, executing S61; if it is determined that the first packet buffer unit does not include the data buffer identifier, S54 is executed.
S54: and determining that the first message cache unit is a data cache.
S55: the message cache manager is disabled.
S56: and finding out a third message cache unit and a fourth message cache unit according to the management cache address linked list of the message cache.
The address of the management cache in the third cache unit is the address of the first message cache unit, and the address of the management cache in the first message cache unit is the address of the fourth message cache unit.
S57: and updating the address of the management cache in the third message cache unit to the address in the fourth message cache unit.
S58: and reserving the address of the data cache in the first message cache unit, and clearing the address of the management cache in the first message cache unit to obtain a second message cache unit.
S59: and updating the address of the management cache in the last message cache unit in the management cache address linked list into the address of the second message cache unit.
S60: the message cache manager is enabled.
S61: and determining that the first message cache unit is a management cache.
S62: and searching a fifth message cache unit containing the address of the first message cache unit, wherein the fifth message cache unit is a management cache.
S63: and deleting the address of the first message cache unit from the fifth message cache unit.
S64: and acquiring a sixth message cache unit, and storing the address of the first message cache unit in the sixth message cache unit, wherein the sixth message cache unit is a management cache.
Through S51-S64, the abnormal condition when the first message cache unit manages the cache can be processed, and the abnormal condition when the first message cache unit manages the cache can also be processed, so that the abnormal condition of the message cache manager caused by repeated release of the first message cache unit is eliminated, and the message cache manager can be effectively prevented from being crashed due to the fact that information in the management cache is rewritten.
Based on the same inventive concept, an embodiment of the present invention provides an apparatus for handling an exception of a packet cache manager, where the apparatus has a structure as shown in fig. 6, and includes:
a disabling module 61, configured to disable the message cache manager if it is detected that the first message cache unit of the message cache manager is repeatedly released and it is determined that the first message cache unit is a management cache;
a first deleting module 62, configured to delete the address of the first packet caching unit and the address of the management cache in the first packet caching unit from the management cache address linked list of the packet caching manager;
the establishing module 63 is configured to establish a second packet caching unit according to the address of the data cache in the first packet caching unit, and add the address of the second packet caching unit to the management cache address linked list;
and an enabling module 64, configured to enable the message cache manager.
In the scheme, whether the message cache unit in the message cache manager is repeatedly released can be monitored in real time, if the first message cache unit is repeatedly released is detected, whether the first message cache unit is a management cache is determined, if the first message cache unit is the management cache, the abnormal condition that the management cache in the message cache manager is repeatedly released is determined, in order to avoid the message cache manager from being crashed, the message cache manager is forbidden, the address of the first message cache unit and the address of the management cache in the first message cache unit are deleted from the management cache address chain table of the message cache manager, and after the second message cache unit is reestablished according to the address of the data cache in the first message cache unit and the management cache address chain table is updated, the message cache manager is started again, so that the abnormal condition of the message cache manager caused by the repeated release of the first message cache unit is eliminated, the message cache manager is prevented from being crashed due to the fact that information in the management cache is rewritten.
Specifically, the first deleting module 62 is specifically configured to:
finding a third message cache unit and a fourth message cache unit according to a management cache address linked list of the message cache, wherein the management cache address in the third cache unit is the address of the first message cache unit, and the management cache address in the first message cache unit is the address of the fourth message cache unit;
and updating the address of the management cache in the third message cache unit to the address of the fourth message cache unit.
Specifically, the establishing module 63 is specifically configured to:
reserving the address of the data cache in the first message cache unit, and clearing the address of the management cache in the first message cache unit to obtain a second message cache unit;
and updating the address of the management cache in the last message cache unit in the management cache address linked list into the address of the second message cache unit.
Optionally, the method further includes a determining module, configured to:
determining whether the first message cache unit contains a data cache identifier;
if the first message cache unit is determined to contain the data cache identification, determining that the first message cache unit is a data cache;
and if the first message cache unit is determined not to contain the data cache identification, determining that the first message cache unit is a management cache.
Optionally, the method further includes:
the searching module is used for searching a fifth message cache unit containing the address of the first message cache unit if the first message cache unit is detected to be released repeatedly and the first message cache unit is determined to be a data cache, wherein the fifth message cache unit is a management cache;
the second deleting module is used for deleting the address of the first message cache unit from the fifth message cache unit;
and the acquisition module is used for acquiring a sixth message cache unit, storing the address of the first message cache unit in the sixth message cache unit, and the sixth message cache unit is a management cache.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While alternative embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following appended claims be interpreted as including alternative embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various modifications and variations can be made in the embodiments of the present invention without departing from the spirit or scope of the embodiments of the invention. Thus, if such modifications and variations of the embodiments of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to encompass such modifications and variations.
Claims (8)
1. A method for processing exception of message buffer manager is characterized in that the method comprises the following steps:
if detecting that a first message cache unit of a message cache manager is released repeatedly and determining that the first message cache unit is a management cache, forbidding the message cache manager;
deleting the address of the first message cache unit and the address of the management cache in the first message cache unit from a management cache address linked list of the message cache manager;
establishing a second message cache unit according to the address of the data cache in the first message cache unit, and adding the address of the second message cache unit into the management cache address linked list;
enabling the message cache manager;
wherein, deleting the address of the first packet cache unit from the management cache address linked list of the packet cache manager specifically includes:
finding a third message cache unit and a fourth message cache unit according to a management cache address linked list of the message cache, wherein the address of the management cache in the third message cache unit is the address of the first message cache unit, and the address of the management cache in the first message cache unit is the address of the fourth message cache unit;
and updating the address of the management cache in the third message cache unit to the address of the fourth message cache unit.
2. The method according to claim 1, wherein establishing a second packet buffer unit according to an address of a data buffer in the first packet buffer unit, and adding the address of the second packet buffer unit to the management buffer address linked list specifically includes:
reserving the address of the data cache in the first message cache unit, and clearing the address of the management cache in the first message cache unit to obtain a second message cache unit;
and updating the address of the management cache in the last message cache unit in the management cache address linked list to the address of the second message cache unit.
3. The method of any of claims 1-2, further comprising:
determining whether the first message cache unit contains a data cache identifier;
if the first message cache unit is determined to contain the data cache identification, determining that the first message cache unit is a data cache;
and if the first message cache unit is determined not to contain the data cache identification, determining that the first message cache unit is a management cache.
4. The method of claim 3, further comprising:
if the first message cache unit is repeatedly released and the first message cache unit is determined to be a data cache, searching a fifth message cache unit containing the address of the first message cache unit, wherein the fifth message cache unit is a management cache;
deleting the address of the first message cache unit from the fifth message cache unit;
and acquiring a sixth message cache unit, and storing the address of the first message cache unit in the sixth message cache unit, wherein the sixth message cache unit is a management cache.
5. An apparatus for handling an exception to a message cache manager, comprising:
the disabling module is used for disabling the message cache manager if detecting that a first message cache unit of the message cache manager is released repeatedly and determining that the first message cache unit is a management cache;
a first deleting module, configured to delete the address of the first packet caching unit and the address of the management cache in the first packet caching unit from a management cache address linked list of the packet caching manager;
the establishing module is used for establishing a second message cache unit according to the address of the data cache in the first message cache unit and adding the address of the second message cache unit into the management cache address linked list;
the starting module is used for starting the message cache manager;
the first deleting module is specifically configured to:
finding a third message cache unit and a fourth message cache unit according to a management cache address linked list of the message cache, wherein the address of the management cache in the third message cache unit is the address of the first message cache unit, and the address of the management cache in the first message cache unit is the address of the fourth message cache unit;
and updating the address of the management cache in the third message cache unit to the address of the fourth message cache unit.
6. The apparatus of claim 5, wherein the establishing module is specifically configured to:
reserving the address of the data cache in the first message cache unit, and clearing the address of the management cache in the first message cache unit to obtain a second message cache unit;
and updating the address of the management cache in the last message cache unit in the management cache address linked list to the address of the second message cache unit.
7. The apparatus of any of claims 5-6, further comprising a determination module to:
determining whether the first message cache unit contains a data cache identifier;
if the first message cache unit is determined to contain the data cache identification, determining that the first message cache unit is a data cache;
and if the first message cache unit is determined not to contain the data cache identification, determining that the first message cache unit is a management cache.
8. The apparatus of claim 7, further comprising:
a searching module, configured to search a fifth packet cache unit including an address of the first packet cache unit if it is detected that the first packet cache unit is repeatedly released and it is determined that the first packet cache unit is a data cache, where the fifth packet cache unit is a management cache;
a second deleting module, configured to delete the address of the first packet caching unit from the fifth packet caching unit;
the acquisition module is used for acquiring a sixth message cache unit, and storing the address of the first message cache unit in the sixth message cache unit, wherein the sixth message cache unit is a management cache.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710740504.0A CN107454018B (en) | 2017-08-25 | 2017-08-25 | Method and device for processing exception of message cache manager |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710740504.0A CN107454018B (en) | 2017-08-25 | 2017-08-25 | Method and device for processing exception of message cache manager |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107454018A CN107454018A (en) | 2017-12-08 |
| CN107454018B true CN107454018B (en) | 2020-01-21 |
Family
ID=60493084
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710740504.0A Active CN107454018B (en) | 2017-08-25 | 2017-08-25 | Method and device for processing exception of message cache manager |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107454018B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110297732B (en) * | 2019-06-14 | 2024-01-23 | 杭州迪普科技股份有限公司 | FPGA state detection method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102447610A (en) * | 2010-10-14 | 2012-05-09 | 中兴通讯股份有限公司 | Method and device for realizing message buffer resource sharing |
| CN102595512A (en) * | 2012-03-19 | 2012-07-18 | 福建星网锐捷网络有限公司 | Message caching method and access point |
| JP2012220975A (en) * | 2011-04-04 | 2012-11-12 | Nec Corp | Network management system, management device, management target device, network management method, and computer program |
| CN102932265A (en) * | 2012-11-06 | 2013-02-13 | 福建星网锐捷网络有限公司 | Data caching management device and method |
-
2017
- 2017-08-25 CN CN201710740504.0A patent/CN107454018B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102447610A (en) * | 2010-10-14 | 2012-05-09 | 中兴通讯股份有限公司 | Method and device for realizing message buffer resource sharing |
| JP2012220975A (en) * | 2011-04-04 | 2012-11-12 | Nec Corp | Network management system, management device, management target device, network management method, and computer program |
| CN102595512A (en) * | 2012-03-19 | 2012-07-18 | 福建星网锐捷网络有限公司 | Message caching method and access point |
| CN102932265A (en) * | 2012-11-06 | 2013-02-13 | 福建星网锐捷网络有限公司 | Data caching management device and method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107454018A (en) | 2017-12-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR102074113B1 (en) | Managing object lifetime in a cyclic graph | |
| CN106294206B (en) | Cache data processing method and device | |
| CN108897628A (en) | A kind of implementation method of distributed lock, device and electronic equipment | |
| CN108197160B (en) | Picture loading method and device | |
| CN109213604B (en) | Data source management method and device | |
| CN108984295B (en) | Memory recovery method, computer device and computer readable storage medium | |
| KR20190030728A (en) | Abnormal detection using sequence of system call | |
| CN111198856A (en) | File management method and device, computer equipment and storage medium | |
| CN106685894B (en) | Risk identification method, device and system | |
| CN109213774B (en) | Data storage method and device, storage medium and terminal | |
| US20200242039A1 (en) | User data recovery in a content aware storage system | |
| EP3836513A1 (en) | Method for processing superhot file, load balancing device, and download server | |
| CN109756533B (en) | Mirror image acceleration method and device and server | |
| CN107454018B (en) | Method and device for processing exception of message cache manager | |
| CN109600254B (en) | Method for generating full-link log and related system | |
| CN111158892A (en) | Task queue generating method, device and equipment | |
| US9274946B2 (en) | Pre-leak detection scan to identify non-pointer data to be excluded from a leak detection scan | |
| CN106155790B (en) | Application program management method and device and terminal | |
| CN109246234B (en) | Image file downloading method and device, electronic equipment and storage medium | |
| CN111046106A (en) | Cache data synchronization method, device, equipment and medium | |
| US9954971B1 (en) | Cache eviction in a distributed computing system | |
| CN109857805B (en) | Block chain based data storage method, related equipment and storage medium | |
| US20060112299A1 (en) | Implementing application specific management policies on a content addressed storage device | |
| CN110955460A (en) | Service process starting method and device, electronic equipment and storage medium | |
| JP2021535480A (en) | Resource allocation method, equipment and storage media |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |