VLDB 2026 Research / reviewers in the wild / expert
Alex Gendler
dblp:217/0656
· DBLP profile ↗
1ranked-venue papers
1as first author
0since 2021 · last 2018
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Systems, architecture and hardware · 1 · 1 first-author
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Hardware reliability and fault tolerance · 61% Memory systems · 39% |
Topics — the 4 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Hardware reliability and fault tolerance › error correction
cache error correction |
0.3 | 1 | 2018 | Don't Correct the Tags in a Cache, Just Check Their Hamming Distance from the Lookup Tag · HPCA 2018 |
Memory systems › cache design
cache tag storage |
0.3 | 1 | 2018 | Don't Correct the Tags in a Cache, Just Check Their Hamming Distance from the Lookup Tag · HPCA 2018 |
Hardware reliability and fault tolerance
error correction |
0.3 | 1 | 2018 | Don't Correct the Tags in a Cache, Just Check Their Hamming Distance from the Lookup Tag · HPCA 2018 |
Memory systems › cache › cache organization
set-associative cache |
0.1 | 1 | 2018 | Don't Correct the Tags in a Cache, Just Check Their Hamming Distance from the Lookup Tag · HPCA 2018 |
Methods — techniques the papers use, named apart from their topics
hamming distance · 0.3ECC · 0.3
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2018 | Don't Correct the Tags in a Cache, Just Check Their Hamming Distance from the Lookup TagabstractThis paper describes the design of an efficient technique for correcting errors in the tag array of set-associative caches. The main idea behind this scheme is that for a cache tag array protected with ECC code, the stored tags do not need to be corrected prior to the comparison against a lookup tag for cache hit/miss definition. This eliminates the need for costly hardware to correct the cache tags before checking for a hit or a miss. The paper reveals the various optimizations needed to translate this idea into a design that delivers a practical improvement in a product. An analysis of our design, as compared to state of the art methods, shows that it can provide the same correction and detection strength with less area, power and timing overheads and better performance. An Intel Core® microprocessor is implementing this technique in its second level and third level caches. Alex Gendler, Arkady Bramnik, Ariel Szapiro, Yiannakis Sazeides |
HPCA | 1 |