Key information

Title
Snoop filter device
Application number
20190393
Case type
National
Status
18.01.2021 Patent meddelt (B1)
Filed
22.03.2019
Effective date
22.03.2019
Publicly available
23.09.2020
Next annual fee due
31.03.2027
Applicant
Numascale AS (NO)
Owner
Numascale AS (NO)
Inventor
Helge Simonsen (NO) et al.
Agent
BRYN AARFLOT AS (NO)
Granted
18.01.2021
Patent number
345417
Expiry date
22.03.2039

Abstract and drawing

Disclaimer: This text has been machine-scanned and may contain errors – please refer to "Publications" for legally binding content.
The invention relates to a device for use in maintaining cache coherence in a multiprocessor computing system. The snoop filter device is connectable with a plurality of cache elements, where each cache element comprises a number of cache agents. The snoop filter device comprises a plurality of snoop filter storage locations, where each snoop filter storage location is mapped to one cache element.

Publications

B1A1
Checking availability of the latest published version...

Documents

 Expand Download files (21)
Date
 Date Doc. No. Process Case number In/Out Journal description To/from
 02.02.2021 12-01 Saksbehandling 20190393(345417) UT PT Varsel om betaling av første årsavgift (3317) (PT20190393)
22.01.2021 11-01 Saksbehandling 20190393(345417) UT PT Registreringsbrev Nasjonal Patent (15) (PT20190393)
19.10.2020 10-01 Saksbehandling 20190393 UT PT Meddelelse om patent BRYN AARFLOT AS
 08.04.2020 09-03 Saksbehandling 20190393 INN Hovedbrev BRYN AARFLOT AS
 08.04.2020 09-02 Saksbehandling 20190393 INN Krav BRYN AARFLOT AS
 08.04.2020 09-01 Saksbehandling 20190393 INN Korrespondanse (Hovedbrev inn) BRYN AARFLOT AS
 24.03.2020 08-01 Saksbehandling 20190393 UT Realitet patent BRYN AARFLOT AS
 21.11.2019 07-04 Saksbehandling 20190393 INN Beskrivelse ren BRYN AARFLOT AS
 21.11.2019 07-03 Saksbehandling 20190393 INN Beskrivelse merket BRYN AARFLOT AS
 21.11.2019 07-02 Saksbehandling 20190393 INN Hovedbrev BRYN AARFLOT AS
 21.11.2019 07-01 Saksbehandling 20190393 INN Korrespondanse (Hovedbrev inn) BRYN AARFLOT AS
 18.10.2019 06-02 Saksbehandling 20190393 UT PT_report 11:04:08
18.10.2019 06-01 Saksbehandling 20190393 UT Realitet patent BRYN AARFLOT AS
 04.04.2019 05-03 Saksbehandling 20190393 INN Fullmakt BRYN AARFLOT AS
 04.04.2019 05-02 Saksbehandling 20190393 INN Erklæring Søkers rett til oppfinnelse BRYN AARFLOT AS
 04.04.2019 05-01 Saksbehandling 20190393 INN Korrespondanse (Hovedbrev inn) BRYN AARFLOT AS
 02.04.2019 04-01 Saksbehandling 20190393 UT Information to inventor BRYN AARFLOT AS
 01.04.2019 03-01 Saksbehandling 20190393 UT Formalia 1 BRYN AARFLOT AS
 01.04.2019 02-01 Saksbehandling 20190393 UT Infobrev til oppfinner BRYN AARFLOT AS
 22.03.2019 01-02 Saksbehandling 20190393 INN Beskrivelse BRYN AARFLOT AS
 22.03.2019 01-01 Saksbehandling 20190393 INN Søknadsskjema Patent BRYN AARFLOT AS

Description, claims and drawings

Disclaimer: This text has been machine-scanned and may contain errors – please refer to "Publications" for legally binding content. Description
Technical field[0001] The disclosure relates to a device for maintaining cache coherence in a multiprocessor computing system.Background[0002] Efficiently maintaining cache coherence is a central requirement for obtaining high performance shared memory multiprocessor systems.[0003] Shared memory multiprocessor systems usually contain one or more shared main memory agents in addition to a series of local memory agents, called cache agents, or just cache. The cache agents may belong only to a local processor or a node of processors and are characterized by their high speed and small size compared with the main memory. Storing data in a local cache agent that e.g. belongs to a working set of a local CPU will thus largely improve the overall performance of the multiprocessor system as the frequently used data in the working set can be more quickly accessed by the local CPU.[0004] Having a series of local cache agents each holding data locally gives rise to the problem with how to maintain cache coherence. If a CPU modifies a cache line in a local cache agent through e.g. a write-operation, other cache agents holding a copy of the same cache line will be unaware of this write operation, and their copy of the respective cache line will consequently be out of date. These out of date cache lines may then be defined as stale.[0005] In order to obtain cache coherence, i.e. eliminating stale data, a wide variety of techniques and procedures have been implemented. This involves implementing a variety of cache coherence protocols, like the MSI, MESI, MOESI protocols, as well as implementing a variety of cache coherence mechanisms, like snoopy bus based methods.[0006] Snoopy bus based methods usually involve what is called a snooper that snoops transactions that are being communicated across a bus, and updates the local cache accordingly. The snooper may belong to a cache agent, or group of cache agents, and the bus may run between various agents in the computer system, including cache agents, cache elements, cache nodes, CPUs etc. Whenever a transaction that modifies a cache line is being communicated on the bus, the snooper snoops this transaction, checks whether its respective cache agent holds a copy of this cache line, and modifies the cache line according to the transaction communicated across the bus.[0007] One problem with snoopy bus based cache coherence mechanisms is that every time a transaction occurs on the bus, the snooper has to check its appurtenant cache agents/elements for a copy of the cache line communicated across the bus. This action is commonly called a lockup action and involves a series of procedural steps having to be performed.[0008] The concept of a snoop filter has been developed in order to improve on the efficiency of snoopy based cache coherence mechanisms. A snoop filter is a directory-based structure that maintains information related to a series of cache lines stored in the cache. In a multi-processor system, a snoop filter may for example monitor the bus traffic and filter out the transactions on the bus not relating to a cache line that is stored in any of its appurtenant cache agents. This results in the snooper having to perform fewer power and time consuming lockups, and hence improves the efficiency of the snoopy based cache coherence mechanism.[0009] A snoop filter is commonly structured in order to maintain information as entries stored in a series of snoop filter storage locations. Each snoop filter storage location is commonly configured to store an entry comprising at least a tag that identifies an appurtenant cache line, and optionally various additional information such as state bits, and a series of presence vectors that indicate which cache agents in the system that holds a copy of the cache line identified by the tag. The fraction of each snoop filter storage location associated with presence bits may often be large, resulting in a large overhead. An entry is often defined as the collective information stored in the snoop filter which relate to one specific tag. [0010] Most snoop filters are sized such that they can store a limited amount of information, e.g. a fixed number of entries. The large number of presence vectors in snoop filter entries thus results in a storage capacity problem, consequently limiting the number of snoop filter entries that the snoop filter can maintain. It is desirable to have a snoop filter that covers, i.e. contains information regarding the presence of, as many cache lines as possible per snoop filter storage.[0011] The limited size of a snoop filter will eventually lead to the snoop filter filling up, making it unable to store additional entries. In order to make room for a new entry, the snoop filter will have to dispose of one of its entries through what is called an eviction process. During an eviction process the snoop filter evicts one of its entries and sends a backinvalidation signal to the cache agents in the system that are indicated as holding a copy of the cache line identified by the snoop filter entry being evicted. This back-invalidation signal causes the cache agents to mark the relevant cache line as invalid in order to avoid future problems related to stale data. A problem with this process is that the invalidated cache lines may be in use when invalidated, leading e.g. to additional reloading operations having to be performed.[0012] US 2006294314 A1 describes a snoop filter where the storage locations of a snoop filter are segregated into a number of groups, where some groups are associated with some processors in a system. When new data enter a cache line of a processor, one of the storage locations associated with the processor is selected for further operations.[0013] It is the goal of the present invention to improve the structure of a snoop filer in order to reduce the negative impact of an eviction as well as to increase the efficiency of the snoop filer.Summary of the invention[0014] The invention provides a snoop filter device connectable with a plurality of cache elements, where each cache element comprises a number of cache agents, the snoop filter device comprising a plurality of snoop filter storage locations, each configured to store a tag that identifies a cache line storable in a cache agent, where each snoop filter storage location is mapped to one cache element.[0015] Each snoop filter storage location is in one embodiment of the invention configured to additionally store an identifier for a cache element. Each snoop filter storage location may be mapped to one cache element identified by the identifier stored at that snoop filter storage location.[0016] Each snoop filter storage location is in another embodiment of the invention implicitly associated with one cache element. Each snoop filter storage location may be mapped to one cache element using hard wiring.[0017] Each snoop filter storage location is according to yet another embodiment of the invention configured to additionally store zero or more presence bits, where each presence bit stored at a snoop filter storage location indicates whether a cache line identified by a tag associated with the snoop filter storage location is present in the one cache element to which the snoop filter storage location is mapped.[0018] Each snoop filter storage location is according to yet another embodiment of the invention configured to store up to one presence bit, where a presence bit stored at a snoop filter storage location indicates whether a cache line identified by a tag stored at the snoop filter storage location is present in the cache element to which the snoop filter storage location is mapped.[0019] Each snoop filter storage location is according to yet another embodiment of the invention sectored into a plurality of snoop filter sectors. Each snoop filter sector may be configured to store a tag that identifies a cache line storable in a cache agent. Each snoop filter sector may be configured to additionally store up to one presence bit, where a presence bit stored in a snoop filter sector of a snoop filter storage location indicates whether a cache line identified by a tag stored in the snoop filter sector is present in the cache element to which the snoop filter storage location is mapped.[0020] The snoop filter sectors of a snoop filter storage location may according to yet another embodiment of the invention comprise a first snoop filter sector that is configured to store one tag or a fraction of one tag, and one presence bit, and one or more consecutive snoop filter sectors, each configured to store zero tags and one presence bit, where a presence bit stored in the first snoop filter sector and a presence bit in each one of the consecutive snoop filter sectors indicate the presence of separate cache lines in the same cache element. A presence bit stored in the first snoop filter sector may indicate whether a cache line identified by a tag stored in the first snoop filter sector is present in the cache element to which the snoop filter storage location is mapped, and a presence bit stored in each consecutive snoop filter sector to the first snoop filter sector may indicate whether a cache line identified by a respective consecutive tag to the tag stored in the first snoop filter sector of the snoop filter storage location is present in the cache element to which the snoop filter storage location is mapped.[0021] According to yet another embodiment of the invention a presence bit stored in the first snoop filter sector indicates whether a cache line identified by a reconstructed tag is present in the cache element to which the snoop filter storage location is mapped, and a presence bit stored in each consecutive snoop filter sector to the first snoop filter sector indicates whether a cache line identified by a respective consecutive tag to the reconstructed tag is present in the cache element to which the snoop filter storage location is mapped, the reconstructed tag being reconstructed from a fraction of a tag stored in the first snoop filter sector, and from the number of sectors in the snoop filter storage location. The most significant bits of the reconstructed tag may consist of the fractional tag, and the least significant bits of the reconstructed tag may consist of a log2(n) number of zeros, n being the number of sectors in the snoop filter storage location.[0022] Other advantageous features will be apparent from the accompanyingclaims. Brief description of the drawings[0023] In order to make the invention more readily understandable, the discussion that follows will refer to the accompanying drawings, in which:[0024] Figure 1 is a schematic illustration of a multiprocessor computer system comprising a snoop filter device,[0025] Figure 2 is a schematic illustration of a snoop filter device comprising a plurality of snoop filter storage locations, where each snoop filter storage location indicates the presence of a cache line in a cache element,[0026] Figure 3 is a schematic illustration of a snoop filter device comprising a plurality of snoop filter storage locations, where each snoop filter storage location is mapped to one cache element,[0027] Figure 4 is a schematic illustration of a snoop filter device comprising a plurality of snoop filter storage locations, where each snoop filter storage location stores an identifier for a cache element,[0028] Figure 5 is a schematic illustration of a snoop filter device comprising a plurality of snoop filter storage locations, where each snoop filter storage location stores an identifier for a cache element,[0029] Figure 6 is a schematic illustration of a snoop filter device comprising a plurality of snoop filter storage locations, where each snoop filter storage location is mapped to one cache element using hard wiring,[0030] Figure 7 is a schematic illustration of a snoop filter device comprising a plurality of snoop filter storage locations, where each snoop filter storage location stores a presence bit,[0031] Figure 8 is a schematic illustration of a snoop filter device comprising a plurality of snoop filter storage locations, where each snoop filter storage location is sectored into two sectors,[0032] Figure 9 is a schematic illustration of a snoop filter device comprising a plurality of snoop filter storage locations, where each snoop filter storage location is sectored into two sectors, and where each sector stores a tag and a presence bit,[0033] Figure 10 is a schematic illustration of a snoop filter device comprising a plurality of snoop filter storage locations, where each snoop filter storage location is sectored into a plurality of sector, where the first sector stores a tag and presence bit, and where each consecutive sector after the first stores a presence bit,[0034] Figure 11 is a schematic illustration of a snoop filter device comprising a plurality of snoop filter storage locations, where each snoop filter storage location is sectored into a plurality of sector, where the first sector stores a tag and a presence bit, and where each consecutive sector after the first stores a presence bit,[0035] Figure 12a is a schematic illustration of a snoop filter storage location sectored into a plurality of sector, where the first sector stores a tag and a presence bit, and where each consecutive sector after the first stores a presence bit, and[0036] Figure 12b is a schematic illustration of a snoop filter storage location sectored into a plurality of sector, where the first sector stores a fraction of a tag and a presence bit, and where each consecutive sector after the first stores a presence bit.Detailed description of the Invention[0037] In the following, general embodiments as well as particular exemplary embodiments of the invention will be described. References and possible numerals will be made to the accompanying drawings. It shall be noted, however, that the drawings are exemplary embodiments only, and that other features and embodiments may well be within the scope of the invention as described.[0038] The present invention relates to a snoop filter device for use in maintaining cache coherence across a multi-processor computer system. Figure 1 is a schematic illustration of an example of a multiprocessor system that comprises a snoop filter device 100. Here, the snoop filter device 100 is located between a shared memory, cache agent 120 / cache element 110 and processors in a multi-processor system, and is connected to these components via one or more busses 200. A snoop filter device 100 can generally be considered as a directory based device that monitors and filters bus traffic in order to reduce unnecessary snoops in the system. A snoop filter device 100 comprises as schematically illustrated in figure 2 a plurality of snoop filter storage locations 130 making up a directory. Each snoop filter storage location 130 is configured to store at least one tag 140, where each tag identifies a cache line stored in a cache agent 120 in the multiprocessor system. The snoop filter device 100 may be considered as maintaining an overview of which cache lines that are stored where in a computer system.[0039] The present invention relates to a snoop filter device that is connectable to a plurality of cache elements, where each cache element comprises a number of cache agents. A cache element may in the context of the present invention be interpreted as comprising any number of cache agents, e.g. an integer number of cache agents, or a fractional number of cache agents. An example of a cache element may thus be half a cache agent, one cache agent, two cache agents, one whole cache agent plus half of another cache agent etc. Cache agents in each cache element may be connected directly, collectively or a combination of directly and collectively to the snoop filter device[0040] The snoop filter device comprises according to the invention a plurality of snoop filter storage locations, where each snoop filter storage location is configured to at least store a tag that identifies a cache line storable in a cache agent. The information stored at a snoop filter storage location is often referred to as an entry, and a snoop filter storage location may therefore be interpreted as configured to store an entry. An entry may consequently in the context of the present invention generally be considered as information stored in a snoop filter storage location. An entry may thus be considered to comprise a tag, while a tag may alternatively be considered as an entry. Each snoop filter storage location may in addition to a tag store other data, such as state bits, last recently used bits, etc. These other data may be considered as a part of an entry.[0041] Figure 2 illustrates a snoop filter device 100 that stores a tag 140 in one of its storage locations 130, where the tag 140 identifies a cache line stored in a cache agent in a cache element. The cache agent may here be considered as included in a cache element 110 connected to the snoop filter device. A cache line stored in a cache element may according to the invention be considered as stored in any cache agent in that particular cache element 110.[0042] The snoop filter device may in the context of the invention be considered as configured to track at least a plurality of cache lines, and a plurality of cache elements connected to the snoop filter device. Tracking a cache line by a snoop filter device here means that the snoop filter device maintains information related to which cache elements that holds a copy of the cache line. Tracking a cache element by a snoop filter device here means that the snoop filter device maintains information related to which cache lines that are stored in that cache element.[0043] A snoop filter storage location may be considered as configured to track a cache element, and a cache line. This means that the snoop filter storage location maintains information related to whether the cache element that it is tracking holds a copy of the cache line that it is tracking. Which cache lines that a snoop filter storage location is configured to track may be given by which tags that are stored in the snoop filter storage location.[0044] Figure 3 illustrates a snoop filter device 100 according to the present invention, where each snoop filter storage location 130 is mapped to one cache element 110. This means that any one snoop filter storage location 130 may only track the cache element 110 to which it is mapped. Any one snoop filter storage location 130 may in other words only contain information that relates to cache lines that are stored in the cache element 110 to which that snoop filter storage location 130 is mapped. A snoop filter storage location 130 storing a given tag 140 may consequently indicate that the cache element 110 to which that snoop filter storage location 130 is mapped holds a copy of the cache line identified by that tag 140. The same snoop filter storage location 130 may consequently not contain any information regarding which part of the cache element, e.g. which cache agent, that holds a copy of the cache line, nor will it contain information regarding the presence of the cache line in other cache elements in the system.[0045] Figure 3 illustrates a snoop filter device where multiple snoop filter storage locations are mapped to the same cache element 110. This means that the snoop filter device 100 in certain embodiments of the invention may employ multiple snoop filter storage locations 130 in order to track multiple cache lines in one cache element 110.[0046] In operation, the snoop filter device is connected to a plurality of cache elements, where each cache element comprises a number of cache agents as previously described. When a cache line is loaded into one of the cache elements, e.g. from main memory, the snoop filter device updates its directory by storing the tag related to the newly loaded cache line in one of its storage locations. In the event where all the snoop filter storage locations mapped to the cache element that loaded the cache line already stores an entry, the snoop filter device will have to evict an entry from a snoop filter storage location before it can store a new entry comprising the tag related to the newly loaded cache line. Which snoop filter storage location to evict from will according to the present invention depend on which cache element that loaded the cache line from main memory.According to the invention, the snoop filter device may only store the tag of the newly loaded cache line in a snoop filter storage location that is mapped to the cache element that loaded the new cache line. In other words, when a snoop filter evicts an old entry in favour of a new entry, it can only choose to evict an entry stored in a snoop filter storage location that is mapped to the cache element where the cache line identified by the tag in the new entry was loaded.[0047] Each snoop filter storage location 130 is as previously described mapped to one cache element 110. Which cache element 110 that a snoop filter storage location 130 is mapped to may in one embodiment of the invention be determined by an identifier 150 explicitly stored in the snoop filter storage location 130. Figure 4 and 5 are schematic illustrations of a directory in a snoop filter device 100 where each snoop filter storage location 130 stores an identifier 150 for a cache element 110 in addition to a tag 140. An identifier 150 stored in a snoop filter storage location 130 may generally be considered as being fixed throughout an operation of the snoop filter device 100, e.g. throughout the execution of one program, and may for example only be allowed to be changed on a reboot of a program or by executing a certain reset procedure. This consequently means that the identifier 150 in each snoop filter storage location 130 may remain the same over a certain time period, e.g. determined by the time it takes to execute a certain program.[0048] Which cache element 110 that a snoop filter storage location 130 is mapped to may as schematically illustrated in figure 6 be determined implicitly by the snoop filter storage location 130 itself. This means that each snoop filter storage location 130 is implicitly related to a cache identifier 150 for a cache element 110. In this embodiment, each snoop filter storage location 130 is associated directly with one cache element 110, e.g. through its location in the snoop filter directory. The first snoop filter storage location in the directory of a snoop filter device 110 may for example be configured to be mapped to cache element A, while the second snoop filter storage location may be configured to be mapped to cache element D. This means that this first snoop filter storage location may only contain information regarding the presence of cache lines in cache element A, while the second snoop filter storage location may only contain information regarding the presence of cache lines in cache element D.[0049] Each snoop filter storage location 130 is according to one embodiment of the invention mapped to one cache element 130 using hard wiring. In this case, each snoop filter storage location 130 is connected to one cache element 110 such that each snoop filter storage location 130 is permanently associated with the cache element 110 to which it is mapped. The mapping is in this embodiment in other words permanently set out in the device itself and cannot be changed after the device has been produced [0050] Figure 7 is a schematic illustration of a snoop filter device 100, where each snoop filter storage location 130 is configured to store a presence bit 160 in addition to a tag 140. A presence bit 160 stored together with a tag 140 in a snoop filter storage location 130 may indicate whether a cache line identified by the tag 140 is present in the cache element 110 to which the snoop filter storage location 130 is mapped. The presence bit 160 may here be set as true if the cache line is present in the cache element 110, or false if the cache line is not present. The number of presence bits stored in a snoop filter storage location 130 may according to one embodiment of the invention be limited to maximum one.[0051] Figure 8 is a schematic illustration of a snoop filter device where each snoop filter storage location 130 is sectored into a plurality of sectors 170. A sector 170 may here be considered as a part of a snoop filter storage location 130 that may store information, e.g. information relating to a given tag 140. The number of sectors 170 can in principle be any number, but is preferably a power of 2. A snoop filter storage location may comprise only one sector.[0052] In one embodiment of the invention each sector 170 of a snoop filter storage location 130 is configured to store a tag 140 that identifies a cache line storable in a cache agent. This means that one snoop filter storage location 130 may in this embodiment of the invention store as many tags 140 as it contains sectors 170. One snoop filter storage location 130 is mapped to one single cache element, meaning that each sector 170 of the snoop filter storage location 130 is mapped to the same cache element. Each snoop filter storage location 130 may in this embodiment consequently track multiple cache lines - one for each sector. Figure 9 is a schematic illustration of a snoop filter device comprising sectored snoop filter storage locations 130, where each sector 170 is configured to store one tag 140 and one presence bit 160. A presence bit 160 stored together with a sector 170 of a snoop filter storage may here indicate whether a cache line identified by the tag 140 is present in the cache element to which the snoop filter storage location 130 is mapped. The number of presence bits 160 stored in each sector 170 may in any embodiment of the invention be maximum one.[0053] Figure 10 illustrates an embodiment of the invention where each snoop filter storage location 130 is sectored into a plurality of sectors. Here, the first sector 180 of each snoop filter storage location 130 is configured to store one tag 140 and one presence bit 160, while each consecutive sector 190 after the first 180 is configured to store one presence bit 160, but no tag. A presence bit 160 stored together with a tag 140 in a first sector 180 in a snoop filter storage location 130 may in this embodiment of the invention indicate whether a cache line identified by the tag 140 is present in the cache element to which the snoop filter storage location 130 is mapped. The presence bit 160 of each consecutive sector 190 after the first 180 may in this embodiment of the invention indicate the presence of cache lines identified by tags with a certain iterative relationship to the tag 140 stored in the first sector 180. If the tag 140 in the first sector 180 is 0x0001, the presence bit 160 stored with this tag 140 in a first sector 180 in a snoop filter storage location 130 may indicate the presence of a cache line identified by the tag 0x0001 in the cache element to which the snoop filter storage location 130 is mapped. The presence bits 160 of the consecutive second, third, and fourth sector 190 after the first 180 may here for example indicate the presence of cache lines identified by the tags 0x0002, 0x0003 and 0x0004 in the cache element to which the snoop filter storage location 130 is mapped. The tags 0x0002, 0x0003 and 0x0004 are here given implicitly through their relationship with the first tag, meaning that neither one of the tags 0x0002, 0x0003 and 0x0004 are stored in any sector but are implicitly given by the tag 140 in the first sector 180 and the number of the consecutive sector. The relationship between the explicitly given tag in the first sector and the implicitly given tags in the consecutive sectors may in principle take any form. Following the example with a tag in the first sector being 0x0001, the implicitly given tags of each consecutive sector may e.g. follow a formula such that the tag in sector m is given by a function of m. The tag in sector n may for example equals the tag in the first sector multiplied by a function of m, e.g. m, 2m, m2 , etc.[0054] The first sector 180 of each snoop filter storage location may according to one embodiment of the invention be configured to store a fraction of a tag, and one presence bit. A fraction of a tag/fractional tag may here be interpreted as a subset of the Y number of bits required to write out a full tag. Sectoring of a snoop filter storage location into multiple sectors allows for the tag in the first sector 180 to be identified using X fewer bits than the Y number of bits required to write out the full tag. Here, X = log2(n), where n equals the number of sectors in the snoop filter storage location. Figure 12a illustrates a snoop filter storage location where a full 8 bit tag, 10000000, is stored in the first sector 180, and where each consecutive sector 190 is associated with the consecutive tags 10000001 to 10000111. The linear consecutive relationship between the first tag and the consecutive tags allows the tag in the first sector 180 to be shortened by its 3 least significant bits. These bits are then implicitly given by the number of sectors. Figure 12b illustrates a snoop filter storage location where a Y = 8 bit tag 10000000 is stored in the first sector 180 of a snoop filter storage location as 10000. The X = log2(# of sectors) = log2(8) = 3 least significant bits of the 8 bit tag is not explicitly stored in the first sector 180 as these can be implicitly deduced from the fact that there are 8 sectors in the snoop filter storage location. The full Y bit tag can here be reconstructed by adding the fraction of a tag/fractional tag stored in the first sector 180 and a log2(n) number of zeros. The full Y bit tag may in other words be reconstructed such that the fractional tag makes up the most significant bits while the log2(n) number of zeros make up the least significant bits. A snoop filter storage location may consequently be considered as storing a full Y bit reconstructed tag, where the full Y bit reconstructed tag is given partly by the explicitly stored fractional tag, and partly implicit by the number of sectors in the snoop filter storge location. The full Y bit reconstructed tag can in other words be considered as being stored in the snoop filter storage location. [0055] Sectoring of snoop filter storage locations may consequently be used in order to optimize the number of cache lines that can be tracked per storage in the snoop filter. This can be seen directly from figure 12a and figure 12b. The 16 bits required to write out the information in the storage location illustrated in figure 12a may be be reduced by 3 bits by replacing the tag with a fractional tag. The full tag may here be reconstructed from merging the fractional tag 10000 with log2(number of sectors), i.e. 10000 merged with 000 = 10000000.[0056] The relationship between the explicitly given tag 140 in the first sector 180 and the implicitly given tags in the consecutive sectors 190 may be programed or alternatively be hard wired.Claims1. A snoop filter device connectable with a plurality of cache elements, where each cache element comprises a number of cache agents, the snoop filter device comprising:- a plurality of snoop filter storage locations, each configured to store a tag that identifies a cache line storable in a cache agent,where each snoop filter storage location is mapped to one cache element.2. A snoop filter device according to claim 1, where each snoop filter storage location is configured to additionally store an identifier for a cache element.3. A snoop filter device according to claim 2, where each snoop filter storage location is mapped to one cache element identified by the identifier stored at that snoop filter storage location.4. A snoop filter device according to claim 1, where each snoop filter storage location is implicitly associated with one cache element.5. A snoop filter device according to claim 4, where each snoop filter storage location is mapped to one cache element using hard wiring.6. A snoop filter device according to any one of the preceding claims, where- each snoop filter storage location is configured to additionally store zero or more presence bits, and where- each presence bit stored at a snoop filter storage location indicates whether a cache line identified by a tag associated with the snoop filter storage location is present in the one cache element to which the snoop filter storage location is mapped.7. A snoop filter device according to claim 6, where - each snoop filter storage location is configured to store up to one presence bit, and where- a presence bit stored at a snoop filter storage location indicates whether a cache line identified by a tag stored at the snoop filter storage location is present in the cache element to which the snoop filter storage location is mapped.8. A snoop filter device according to any one of the claims 1 - 6, where each snoop filter storage location is sectored into a plurality of snoop filter sectors.9. A snoop filter device according to claim 8, where each snoop filter sector is configured to store a tag that identifies a cache line storable in a cache agent.10. A snoop filter device according to claim 9, where each snoop filter sector is configured to additionally store up to one presence bit, and where a presence bit stored in a snoop filter sector of a snoop filter storage location indicates whether a cache line identified by a tag stored in the snoop filter sector is present in the cache element to which the snoop filter storage location is mapped.11. A snoop filter device according to claim 8, where the snoop filter sectors of a snoop filter storage location comprise- a first snoop filter sector that is configured to store one tag or a fraction of one tag, and one presence bit, and- one or more consecutive snoop filter sectors, each configured to store zero tags and one presence bit,where a presence bit stored in the first snoop filter sector and a presence bit in each one of the consecutive snoop filter sectors indicate the presence of separate cache lines in the same cache element.12. A snoop filter device according to claim 11, where- a presence bit stored in the first snoop filter sector indicates whether a cache line identified by a tag stored in the first snoop filter sector is present in the cache element to which the snoop filter storage location is mapped, and where- a presence bit stored in each consecutive snoop filter sector to the first snoop filter sector indicates whether a cache line identified by a respective consecutive tag to the tag stored in the first snoop filter sector of the snoop filter storage location is present in the cache element to which the snoop filter storage location is mapped.13. A snoop filter device according to claim 11, where- a presence bit stored in the first snoop filter sector indicates whether a cache line identified by a reconstructed tag is present in the cache element to which the snoop filter storage location is mapped, and where - a presence bit stored in each consecutive snoop filter sector to the first snoop filter sector indicates whether a cache line identified by a respective consecutive tag to the reconstructed tag is present in the cache element to which the snoop filter storage location is mapped,the reconstructed tag being reconstructed from a fraction of a tag stored in the first snoop filter sector, and from the number of sectors in the snoop filter storage location.14. A snoop filter device according to claim 13, where- the most significant bits of the reconstructed tag consist of the fractional tag, and where- the least significant bits of the reconstructed tag consist of a log2(n) number of zeros, n being the number of sectors in the snoop filter storage location.
Claims
Krav1. En snoopfilteranordning som kan kobles til en flerhet med hurtigbufferelementer, hvor hvert hurtigbufferelement omfatter et antall hurtigbufferagenter, snoopfilteranordningen omfatter:- en flerhet med snoopfilterlagringslokasjoner, hver konfigurert for å lagre en merkelapp som identifiserer en hurtigbufferlinje som kan lagres i en hurtigbufferagent,hvor hver snoopfilterlagringslokasjon er kartlagt til ett hurtigbufferelement.2. En snoopfilteranordning i henhold til krav 1, hvor hver snoopfilterlagringslokasjon er konfigurert for å i tillegg lagre en identifikator for et hurtigbufferelement.3. En snoopfilteranordning i henhold til krav 2, hvor hver snoopfilterlagringslokasjon er kartlagt til ett hurtigbufferelement identifisert av identifikatoren lagret ved den snoopfilterlagringslokasjon.4. En snoopfilteranordning i henhold til krav 1, hvor hver snoopfilterlagringslokasjon er implisitt assosiert med ett hurtigbufferelement.5. En snoopfilteranordning i henhold til krav 4, hvor hver snoopfilterlagringslokasjon er kartlagt til ett hurtigbufferelement ved å bruke fast logikk.6. En snoopfilteranordning i henhold til et hvilket som helst av de foregående kravene, hvor- hver snoopfilterlagringslokasjon er konfigurert for å i tillegg lagre null eller flere tilstedeværelsesbit, og hvor- hver tilstedeværelsesbit lagret ved en snoopfilterlagringslokasjon indikerer hvorvidt en hurtigbufferlinje identifisert av en merkelapp assosiert med snoopfilterlagringslokasjonen er tilstede i det ene hurtigbufferelementet til hvilket snoopfilterlagringslokasjonen er kartlagt.7. En snoopfilteranordning i henhold til krav 6, hvor- hver snoopfilterlagringslokasjon er konfigurert for å lagre opp til én tilstedeværelsesbit, og hvor- en tilstedeværelsesbit lagret ved en snoopfilterlagringslokasjon indikerer hvorvidt en hurtigbufferlinje identifisert av en merkelapp lagret ved snoopfilterlagringslokasjonen er tilstede i hurtigbufferelementet til hvilket snoopfilterlagringslokasjonen er kartlagt.8. En snoopfilteranordning i henhold til et hvilket som helst av kravene 1 - 6, hvor hver snoopfilterlagringslokasjon er sektorinndelt i en flerhet med snoopfiltersektorer.9. En snoopfilteranordning i henhold til krav 8, hvor hver snoopfiltersektor er konfigurert for å lagre en merkelapp som identifiserer en hurtigbufferlinje som kan lagres i en hurtigbufferagent.10. En snoopfilteranordning i henhold til krav 9, hvor hver snoopfiltersektor er konfigurert for å i tillegg lagre opptil én tilstedeværelsesbit, og hvor en tilstedeværelsesbit lagret i en snoopfiltersektor av en snoopfilterlagringslokasjon indikerer hvorvidt en hurtigbufferlinje identifisert av en merkelapp lagret i snoopfiltersektoren er tilstede i hurtigbufferelementet til hvilket snoopfilterlagringslokasjonen er kartlagt.11. En snoopfilteranordning i henhold til krav 8, hvor snoopfiltersektorene av en snoopfilterlagringslokasjon omfatter- en første snoopfiltersektor som er konfigurert for å lagre én merkelapp eller en del av én merkelapp, og én tilstedeværelsesbit, og- én eller flere etterfølgende snoopfiltersektorer, hver konfigurert for å lagre null merkelapper og én tilstedeværelsesbit,hvor en tilstedeværelsesbit lagret i den første snoopfiltersektoren og en tilstedeværelsesbit i hver av de etterfølgende snoopfiltersektorene indikerer tilstedeværelsen av separate hurtigbufferlinjer i det samme hurtigbufferelementet.12. En snoopfilteranordning i henhold til krav 11, hvor- en tilstedeværelsesbit lagret i den første snoopfiltersektoren indikerer hvorvidt en hurtigbufferlinje identifisert av en merkelapp lagret i den første snoopfiltersektoren er tilstede i hurtigbufferelementet til hvilket snoopfilterlagringslokasjonen er kartlagt, og hvor- en tilstedeværelsesbit lagret i hver etterfølgende snoopfiltersektor av den første snoopfiltersektoren indikerer hvorvidt en hurtigbufferlinje identifisert av en henholdsvis etterfølgende merkelapp til merkelappen lagret i den første snoopfiltersektoren av snoopfilterlagringslokasjonen er tilstede i hurtigbufferelementet til hvilket snoopfilterlagringslokasjonen er kartlagt.13. En snoopfilteranordning i henhold til krav 11, hvor- en tilstedeværelsesbit lagret i den første snoopfiltersektoren indikerer hvorvidt en hurtigbufferlinje identifisert av en rekonstruert merkelapp er tilstede i hurtigbufferelementet til hvilket snoopfilterlagringslokasjonen er kartlagt, og hvor- en tilstedeværelsesbit lagret i hver etterfølgende snoopfiltersektor til den første snoopfiltersektoren indikerer hvorvidt en hurtigbufferlinje identifisert av en henholdsvis etterfølgende merkelapp av den rekonstruerte merkelappen er tilstede i hurtigbufferelementet til hvilket snoopfilterlagringslokasjonen er kartlagt,den rekonstruerte merkelappen er rekonstruert fra en del av en merkelapp lagret i den første snoopfiltersektoren, og fra antallet sektorer i snoopfilterlagringslokasjonen.14. En snoopfilteranordning i henhold til krav 13, hvor- den mest betydningsfulle delen av den rekonstruerte merkelappen består av delmerkelappen, og hvor- den minst betydningsfulle delen av den rekonstruerte merkelappen består av et log2(n) antall nuller, der n er antallet sektorer isnoopfilterlagringslokasjonen.
Drawings

Priority

No priority

Patent classes

IPC classesG06F 12/0817G06F 12/0831G06F 12/084CPC classesG06F 12/082G06F 12/0831G06F 12/084

Citations

US 2006294314 A1 (A1)US 7325102 B1 (B1)GB 2493593 A (A)US 2007233966 A1 (A1)

Applicants, owners and inventors

Owners
Numascale AS
Innspurten 15 0663 OSLO NO (OSLO Municipality, Oslo county)Org. number: 992462787Inventors
Helge Simonsen
Thorleifs alle 3 B 0489 OSLO NO (OSLO Municipality, Oslo county)
Thibaut Palfer-Sollier
Mortensrudveien 8 X 1283 OSLO NO (OSLO Municipality, Oslo county)
Kai Arne Midjås
Ileveien 40 1407 VINTERBRO NO (ÅS Municipality, Akershus county)
Steffen Persvold
Gladengveien 8 D 0661 OSLO NO (OSLO Municipality, Oslo county)
Einar Rustad
Godliaveien 2 B 0682 OSLO NO (OSLO Municipality, Oslo county)
Thomas Moen
Jomfrubråtveien 39 B 1179 OSLO NO (OSLO Municipality, Oslo county)
Goutam Debnath
19797 SW Sarah Street OR97007 BEAVERTON US
Mario Lodde
Via Montalbo 3 08016 BORORE (NU) IT

Agent

BRYN AARFLOT AS
BRYN AARFLOT AS

Org. number: 979993269

Name and address are automatically synchronized with the Brønnøysund Register Centre.

Open in The Brønnøysund Register Centre
Stortingsgata 8 0161 OSLO NO (OSLO Municipality, Oslo county)
Org. number: 979993269
Reference: 133214/FMA

Status history

Payment history

Oppositions and appeals

No oppositions or appeals

Administrative limitation

No administrative limitation

Liens and licences

No liens or licenses registered

Gazette entries

No Gazette entries foundOnly events from 2024.03.04 and onwards are shown.