CN110727465A - Protocol reconfigurable consistency implementation method based on configuration lookup table - Google Patents
Protocol reconfigurable consistency implementation method based on configuration lookup table Download PDFInfo
- Publication number
- CN110727465A CN110727465A CN201910859911.2A CN201910859911A CN110727465A CN 110727465 A CN110727465 A CN 110727465A CN 201910859911 A CN201910859911 A CN 201910859911A CN 110727465 A CN110727465 A CN 110727465A
- Authority
- CN
- China
- Prior art keywords
- consistency
- lookup table
- protocol
- reconfigurable
- request
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/30—Arrangements for executing machine instructions, e.g. instruction decode
- G06F9/38—Concurrent instruction execution, e.g. pipeline, look ahead
- G06F9/3824—Operand accessing
- G06F9/3834—Maintaining memory consistency
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/30—Arrangements for executing machine instructions, e.g. instruction decode
- G06F9/38—Concurrent instruction execution, e.g. pipeline, look ahead
- G06F9/3867—Concurrent instruction execution, e.g. pipeline, look ahead using instruction pipelines
- G06F9/3869—Implementation aspects, e.g. pipeline latches; pipeline synchronisation and clocking
Abstract
The invention provides a protocol reconfigurable consistency implementation method based on a configuration lookup table, which relates to the technical field of microprocessor design and comprises the following steps: s1: adding a matched consistency state lookup table in the consistency processing logic; s2: judging whether the consistency protocol is modified, if so, writing the parameters into a lookup table, and executing S3; otherwise, directly executing S3; s3: reading hit state information of a current address request in a consistency pipeline processing; s4: the request type and the hit state information of the current request query a lookup table; s5: and performing consistency operation according to the query result, and returning to the step S2. The protocol reconfigurable consistency implementation method based on the configuration lookup table supports the correction or the expansion of a consistency protocol, even different consistency protocols, so as to adapt to different requirements, ensure that the correction or the expansion of the protocol can be realized without changing the hardware design, and even can be corrected into other consistency protocols more suitable for the current subject requirements.
Description
Technical Field
The present invention relates to the field of microprocessor design technology,
in particular, the invention relates to a protocol reconfigurable consistency implementation method based on a configuration lookup table.
Background
With the continuous progress of the processor manufacturing process and the practical application requirements, a multi-core structure has become the development trend of the current high-performance microprocessor, the Cache consistency problem appearing in a multi-core processor system is always the key of research in the current computer system structure, how to solve the Cache consistency problem, that is, how to keep the consistency of multiple copies of data in multiple caches and main memories is the key for realizing a shared storage system, the solution of the Cache consistency problem not only determines the correctness of the system, but also has important influence on the performance of the system, people have proposed a plurality of Cache consistency protocols to solve the Cache consistency problem, the essence of the Cache consistency protocol is a mechanism for spreading the newly written value of one processor to other processors, and in order to realize efficient spreading, the consistency protocol usually needs to consider the following aspects:
1. how to propagate the new value: write invalidate and write update;
2. how to generate the new value: single write protocol and multiple write protocol;
3. when to propagate the new value: timely propagation and delayed propagation;
4. where the new value will propagate: interception protocol and directory protocol;
because the coherence protocol is a complex characteristic of the multi-party protocol, if the scheme design is not considered completely, it is often difficult to correct the design under the condition that the logic design has errors.
Aiming at the access and storage characteristics of different data streams of different application scenes, various consistency protocols based on the directory protocol and consistency protocol families formed by various protocol optimization schemes are provided by the academic community, and the processing capacity or the processing speed of the consistency protocols in the processor is improved from different angles. Generally, a hardware design can only implement a certain coherency protocol.
Therefore, how to design a reasonable protocol reconfigurable consistency implementation method based on a configuration lookup table becomes a problem which needs to be solved urgently at present.
Disclosure of Invention
The invention aims to provide a protocol reconfigurable consistency implementation method based on a configuration lookup table, which can support the correction or the expansion of a consistency protocol, even different consistency protocols, so as to adapt to different requirements of application subjects, can realize the correction or the expansion of the protocol on the premise of ensuring that the hardware design is not changed, and can even be modified into other consistency protocols more suitable for the requirements of the current subject.
In order to achieve the purpose, the invention is realized by adopting the following technical scheme:
a protocol reconfigurable consistency implementation method based on a configuration lookup table comprises the following steps:
s1: adding a matched consistency state lookup table in the consistency processing logic;
s2: judging whether the consistency protocol is modified, if so, converting the consistency protocol to be used into a corresponding lookup table entry value, loading and writing the lookup table entry value into a consistency state lookup table, and executing the step S3; otherwise, directly executing step S3;
s3: reading hit state information of a current address request in a consistency pipeline processing;
s4: directly inquiring a consistency state lookup table by taking the request type and the hit state information of the current request as an inquiry index;
s5: acquiring the resources required to be allocated and the states to be converted, generating required signals and data, performing consistency operation according to the query result, and returning to execute the step S2.
As a preferred embodiment of the present invention, when step S1 is executed, the related actions of each type of request under different hit status information are configured in detail in the consistency status lookup table, including whether to reserve buffer resources, modify the directory and modify the value, whether to send the secondary request and the secondary request type, whether to send the access request and the access request type, and whether to block the subsequent related requests.
Preferably, in step S1, the structure of the coherency state lookup table is designed to be applicable to most common coherency protocols.
Preferably, the step S2 is executed, and the modification of the coherence protocol includes a change and a reconfiguration of the coherence protocol.
Preferably, when step S2 is executed, the manner of modifying the coherency protocol includes modifying and updating the initial value by maintaining a write operation.
Preferably, in step S2, when modifying the consistency protocol, the storage controller and the copy owner need to have supporting hardware logic support for each operation type described by the content of the consistency lookup table.
As a preferred aspect of the present invention, the consistency look-up table needs to have enough reserved resources when performing steps S1 and S2.
As a preferred aspect of the present invention, the consistency state lookup table may not be modified by performing the steps S3 to S5.
The protocol reconfigurable consistency implementation method based on the configuration lookup table has the beneficial effects that: the method can support the correction or the expansion of the consistency protocol, even different consistency protocols to adapt to different requirements of application topics, and can realize the correction or the expansion of the protocol on the premise of ensuring that the hardware design is not changed, even can be modified into other consistency protocols more suitable for the requirements of the current topic.
Drawings
Fig. 1 is a schematic flow chart of a protocol reconfigurable consistency implementation method based on a configuration lookup table according to the present invention.
Detailed Description
The following are specific examples of the present invention and further describe the technical solutions of the present invention, but the present invention is not limited to these examples.
Various exemplary embodiments of the present invention will now be described in detail with reference to the accompanying drawings. It should be noted that: the relative arrangement of the modules and steps set forth in these embodiments and steps do not limit the scope of the invention unless specifically stated otherwise.
Meanwhile, it should be understood that the flows in the drawings are not merely performed individually for convenience of description, but a plurality of steps are performed alternately with each other.
The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the invention, its application, or uses.
Techniques, methods, and systems known to those of ordinary skill in the relevant art may not be discussed in detail, but are intended to be part of the specification where appropriate.
Aiming at the access and storage characteristics of different data streams of different application scenes, various consistency protocols based on a directory protocol and consistency protocol families formed by various protocol optimization schemes are provided by the academic community, and the processing capacity or the processing speed of the consistency protocols in the processor is improved from different angles. Generally, a hardware design can only implement a certain coherency protocol.
Example one
As shown in fig. 1, which is only one embodiment of the present invention, the present invention provides a protocol reconfigurable consistency implementation method based on a configuration lookup table, including the following steps:
a protocol reconfigurable consistency implementation method based on a configuration lookup table comprises the following steps:
s1: adding a matched consistency state lookup table in the consistency processing logic;
because the consistency protocol is a complex characteristic of the multi-party protocol, if the scheme design is not considered completely, the design is often difficult to correct under the condition that the logic design has errors, in order to improve the processing capacity or the processing speed of the consistency protocol in the processor from different angles, the integrity of the consistency processing logic needs to be added from various aspects, and then a matched consistency state lookup table is added in the consistency processing logic.
The consistency state lookup table is configured with the relevant actions of each type of request under different hit state information in detail, including the buffer resource needing to be reserved, whether to modify the directory and the modification value, whether to send the secondary request and the secondary request type, whether to send the access request and the access request type, and whether to block the subsequent relevant request. To ensure the integrity of the coherency handling logic, the associated actions under all hit status information for all types of requests are actually stored.
For example, the storage request types are ReadBlk/ReadBlkI, ReadBlkMod and the like, the hit states are all related actions in the hit state information such as miss, hit clean or hit dirty, each hit state of each request type is stored in one row, all related actions in the hit state of the request type are stored in the row, and each action is recorded as yes or no, so that the administrator can conveniently read and perform consistency operation.
Thus, each Cache can perform a fixed relevant action under a fixed condition (request type determination and hit state determination).
S2: judging whether the consistency protocol is modified, if so, converting the consistency protocol to be used into a corresponding lookup table entry value, loading and writing the lookup table entry value into a consistency state lookup table, and executing the step S3; otherwise, directly executing step S3;
in order to realize configurable attributes, the consistency protocol lookup table supports maintenance of read-write operations, and initial values can be modified or updated through maintenance of write operations, wherein the modification of the consistency protocol comprises change and reconstruction of the consistency protocol, the change refers to the change of a certain related action in a certain hit state of a certain request type, and the reconstruction refers to the change of the request type and the whole initial values of the hit states.
Here, the manner in which the coherency protocol is modified includes modification by maintaining a write operation and updating an initial value. That is, the change of the consistency protocol is modified by the maintenance write operation, and the reconstruction of the consistency protocol is modified by updating the initial value.
S3: reading hit state information of a current address request in a consistency pipeline processing;
s4: directly inquiring a consistency state lookup table by taking the request type and the hit state information of the current request as an inquiry index;
s5: acquiring the resources required to be allocated and the states to be converted, generating required signals and data, performing consistency operation according to the query result, and returning to execute the step S2.
In the process from step S3 to step S5, the way of generating resource demand and control signals in real time in the conventional consistency implementation is changed, after the hit state information of the current address request is read in the consistency pipeline processing, the request type and the hit state information of the current request are used as the query index to directly query the consistency state lookup table, the resources to be allocated, the states to be converted, the signals and data required for generation are found, and the next consistency operation is performed according to the query result.
After the coherency operation is completed, it is necessary to go back to step S2 again, obtain the latest coherency state lookup table, and then perform the coherency operation again for the next set of parameters.
Under the requirement of each different application project, the consistency state lookup table can be queried, and after data is obtained, consistency operation is further executed, so that reusability and application range are increased.
The protocol reconfigurable consistency implementation method based on the configuration lookup table can support the correction or the expansion of the consistency protocol, even different consistency protocols, so as to adapt to different requirements of application topics, ensure that the correction or the expansion of the protocol can be realized on the premise of not changing the hardware design, and even can be corrected into other consistency protocols more suitable for the requirements of the current topic.
Example two
Still referring to fig. 1, still being one embodiment of the present invention, in order to make the protocol reconfigurable consistency implementation method based on the configuration lookup table more convenient in design and higher in applicability of the consistency operation, the present invention further has the following designs:
first, when step S1 is executed, the structure of the coherency state lookup table needs to be designed for most common coherency protocols.
The consistency protocol and the consistency operation which are required by most previous subjects can be executed, and the reusability and the application range of the module are increased.
Then, when step S2 is executed, for each operation content in the configurable consistency look-up table, that is, when the consistency protocol is modified, the storage controller and the copy owner need to have supporting hardware logic support for each operation type described by the content of the consistency look-up table.
Also, the consistency lookup table needs to have enough reserved resources when performing steps S1 and S2.
In order to expand the requirements, the consistency lookup table must have enough reserved resources, so that the consistency lookup table can be modified and re-modified conveniently. For example, if the request type is increased, the index entry is added, and the content of the consistency lookup table under the index entry is newly added, so that the extended support for the new request type can be realized.
Here, the reserved resources reserved by the consistency lookup table are represented in the following specific form:
first, under the premise that the request type is ReadBlk/ReadBlkI, each hit state (whether the hit state is miss, hit clean, hit dirty, etc.) is stored outside a row, at least one row is still left, ensuring the possibility of other hit states that may exist.
And secondly, under the premise that the request type is ReadBlk/ReadBlkI and the hit state is not hit, at least one column is left in each related action in the line except for recording 'yes' or 'no', and the possibility of other hardware or software responses in the state is ensured.
And thirdly, after all the request type records are finished, at least one request type blank item is still reserved, and each item has at least one row for recording all the related actions of the possible request types in different hit states.
Therefore, on the premise of not changing the hardware design, the modification or the extension of the protocol can be realized, and the fault tolerance and the expandability of the hardware design are improved.
Finally, the consistency state lookup table is not modifiable by performing the steps S3 to S5.
That is, the hit state information of the current address request is read in the coherency pipeline processing, the coherency state lookup table is directly queried by using the request type and the hit state information of the current request as query indexes, the resources to be allocated and the states to be converted are obtained, the required signals and data are generated, and the coherency operation is performed according to the query result, wherein the queried coherency state lookup tables are the same, the hit state information of the current address request read in the coherency pipeline processing before modification does not exist, and then the resources to be allocated and the states to be converted are obtained in the coherency state lookup table after modification, the required signals and data are generated, so that the invariability of the coherency state lookup table between the step S3 and the step S5 is ensured, and the finally obtained coherency operation has uniqueness.
If the coherency state lookup table has been modified between performing steps S3 through S5, the current step is terminated, the process returns to step S2, the new coherency state lookup table is repeatedly obtained, and steps S3 through S5 are re-performed.
The protocol reconfigurable consistency implementation method based on the configuration lookup table can support the correction or the expansion of the consistency protocol, even different consistency protocols, so as to adapt to different requirements of application topics, ensure that the correction or the expansion of the protocol can be realized on the premise of not changing the hardware design, and even can be corrected into other consistency protocols more suitable for the requirements of the current topic.
While certain specific embodiments of the present invention have been described in detail by way of illustration, it will be understood by those skilled in the art that the foregoing is illustrative only and is not limiting of the scope of the invention, as various modifications or additions may be made to the specific embodiments described and substituted in a similar manner by those skilled in the art without departing from the scope of the invention as defined in the appending claims. It should be understood by those skilled in the art that any modifications, equivalents, improvements and the like made to the above embodiments in accordance with the technical spirit of the present invention are included in the scope of the present invention.
Claims (8)
1. A protocol reconfigurable consistency implementation method based on a configuration lookup table is characterized by comprising the following steps:
s1: adding a matched consistency state lookup table in the consistency processing logic;
s2: judging whether the consistency protocol is modified, if so, converting the consistency protocol to be used into a corresponding lookup table entry value, loading and writing the lookup table entry value into a consistency state lookup table, and executing the step S3; otherwise, directly executing step S3;
s3: reading hit state information of a current address request in a consistency pipeline processing;
s4: directly inquiring a consistency state lookup table by taking the request type and the hit state information of the current request as an inquiry index;
s5: acquiring the resources required to be allocated and the states to be converted, generating required signals and data, performing consistency operation according to the query result, and returning to execute the step S2.
2. The method for implementing protocol reconfigurable consistency based on the configuration lookup table according to claim 1, wherein:
when step S1 is executed, the coherency state lookup table configures details of the actions of each type of request under different hit state information, including the buffer resource to be reserved, whether to modify the directory and the modification value, whether to send the secondary request and the secondary request type, whether to send the access request and the access request type, and whether to block the subsequent related request.
3. The method for implementing protocol reconfigurable consistency based on the configuration lookup table according to claim 1, wherein:
the structural design of the coherency state lookup table needs to be suitable for most common coherency protocols when step S1 is performed.
4. The method for implementing protocol reconfigurable consistency based on the configuration lookup table according to claim 1, wherein:
the modification of the coherence protocol includes a change and reconfiguration of the coherence protocol when step S2 is performed.
5. The method for implementing protocol reconfigurable consistency based on the configuration lookup table according to claim 4, wherein:
in executing step S2, the manner of modifying the coherency protocol includes modifying and updating the initial value by maintaining a write operation.
6. The method for implementing protocol reconfigurable consistency based on the configuration lookup table according to claim 1, wherein:
in step S2, when modifying the consistency protocol, the storage controller and the copy owner need to have supporting hardware logic support for each operation type described by the content of the consistency lookup table.
7. The method for implementing protocol reconfigurable consistency based on the configuration lookup table according to claim 1, wherein:
when steps S1 and S2 are executed, the consistency lookup table needs to have enough reserved resources.
8. The method for implementing protocol reconfigurable consistency based on the configuration lookup table according to claim 1, wherein:
the consistency state lookup table is not modifiable after the execution of the steps S3 to S5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910859911.2A CN110727465B (en) | 2019-09-11 | 2019-09-11 | Protocol reconfigurable consistency implementation method based on configuration lookup table |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910859911.2A CN110727465B (en) | 2019-09-11 | 2019-09-11 | Protocol reconfigurable consistency implementation method based on configuration lookup table |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110727465A true CN110727465A (en) | 2020-01-24 |
| CN110727465B CN110727465B (en) | 2021-08-10 |
Family
ID=69218132
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910859911.2A Active CN110727465B (en) | 2019-09-11 | 2019-09-11 | Protocol reconfigurable consistency implementation method based on configuration lookup table |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110727465B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120226868A1 (en) * | 2011-03-01 | 2012-09-06 | University Of Washington Through Its Center For Commercialization | Systems and methods for providing deterministic execution |
| CN102681890A (en) * | 2012-04-28 | 2012-09-19 | 中国科学技术大学 | Restrictive value delivery method and device applied to thread-level speculative parallelism |
| CN102893256A (en) * | 2009-12-15 | 2013-01-23 | 英特尔公司 | Handling operating system (os) transitions in an unbounded transactional memory (utm) mode |
| CN103150264A (en) * | 2013-01-18 | 2013-06-12 | 浪潮电子信息产业股份有限公司 | Extension Cache Coherence protocol-based multi-level consistency simulation domain verification and test method |
| US20140115275A1 (en) * | 2008-07-07 | 2014-04-24 | Robert H. Beers | Satisfying memory ordering requirements between partial reads and non-snoop accesses |
| CN107250993A (en) * | 2015-02-23 | 2017-10-13 | 英特尔公司 | Vectorial cache lines write back processor, method, system and instruction |
-
2019
- 2019-09-11 CN CN201910859911.2A patent/CN110727465B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140115275A1 (en) * | 2008-07-07 | 2014-04-24 | Robert H. Beers | Satisfying memory ordering requirements between partial reads and non-snoop accesses |
| CN102893256A (en) * | 2009-12-15 | 2013-01-23 | 英特尔公司 | Handling operating system (os) transitions in an unbounded transactional memory (utm) mode |
| US20120226868A1 (en) * | 2011-03-01 | 2012-09-06 | University Of Washington Through Its Center For Commercialization | Systems and methods for providing deterministic execution |
| CN102681890A (en) * | 2012-04-28 | 2012-09-19 | 中国科学技术大学 | Restrictive value delivery method and device applied to thread-level speculative parallelism |
| CN103150264A (en) * | 2013-01-18 | 2013-06-12 | 浪潮电子信息产业股份有限公司 | Extension Cache Coherence protocol-based multi-level consistency simulation domain verification and test method |
| CN107250993A (en) * | 2015-02-23 | 2017-10-13 | 英特尔公司 | Vectorial cache lines write back processor, method, system and instruction |
Non-Patent Citations (4)
| Title |
|---|
| M. HASSAN: "Predictable Cache Coherence for Multi-core Real-Time Systems", 《2017 IEEE REAL-TIME AND EMBEDDED TECHNOLOGY AND APPLICATIONS SYMPOSIUM (RTAS)》 * |
| X. LAI: "A Cache Coherence Protocol Using Distributed Data Dependence Violation Checking in TLS", 《2012 SECOND INTERNATIONAL CONFERENCE ON INTELLIGENT SYSTEM DESIGN AND ENGINEERING APPLICATION》 * |
| 张阿敏: "基于片上网络的众核高速缓存一致性研究", 《中国优秀硕士学位论文全文数据库信息科技辑》 * |
| 马鹏勇: "CMT处理器高速缓存的优化技术", 《中国博士学位论文全文数据库 信息科技辑》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110727465B (en) | 2021-08-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103246616B (en) | A kind of globally shared buffer replacing method of access frequency within long and short cycle | |
| US20150058570A1 (en) | Method of constructing share-f state in local domain of multi-level cache coherency domain system | |
| JP5006348B2 (en) | Multi-cache coordination for response output cache | |
| US20190251029A1 (en) | Cache line states identifying memory cache | |
| CN109240945B (en) | Data processing method and processor | |
| US8818942B2 (en) | Database system with multiple layer distribution | |
| CN111742301A (en) | Logging cache inflow to higher level caches by request | |
| US10853193B2 (en) | Database system recovery using non-volatile system memory | |
| US20190347167A1 (en) | Primary Node-Standby Node Data Transmission Method, Control Node, and Database System | |
| US11269772B2 (en) | Persistent memory storage engine device based on log structure and control method thereof | |
| CN109582686B (en) | Method, device, system and application for ensuring consistency of distributed metadata management | |
| US20190272122A1 (en) | Memory Access Technology | |
| CN105701219A (en) | Distributed cache implementation method | |
| CN114490141B (en) | High-concurrency IPC data interaction method based on shared memory | |
| CN103076992A (en) | Memory data buffering method and device | |
| JP2017126334A (en) | Storage devices, operating methods thereof and systems | |
| US20240086332A1 (en) | Data processing method and system, device, and medium | |
| CN102693312B (en) | Flexible transaction management method in key-value store data storage | |
| EP3404537A1 (en) | Processing node, computer system and transaction conflict detection method | |
| US20140297966A1 (en) | Operation processing apparatus, information processing apparatus and method of controlling information processing apparatus | |
| US11099998B2 (en) | Method and device for optimization of data caching | |
| US20140297957A1 (en) | Operation processing apparatus, information processing apparatus and method of controlling information processing apparatus | |
| EP4158487A2 (en) | Core-to-core cache stashing and target discovery | |
| CN112463073A (en) | Object storage distributed quota method, system, equipment and storage medium | |
| CN110727465B (en) | Protocol reconfigurable consistency implementation method based on configuration lookup table |
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 |