Demo Data from VLDB 2026 / reviewers in the wild / expert
Raghavendra Srinivas
dblp:356/9333
· DBLP profile ↗
1ranked-venue papers
0as first author
1since 2021 · last 2024
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Systems, architecture and hardware · 1 · 1 since 2021
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 |
Memory systems · 100% | |
| Software engineering, system software, and programming languages
1 paper |
Operating systems · 100% |
Topics — the 5 heaviest of 5, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Operating systems › resource management › memory management
memory allocation |
0.8 | 1 | 2024 | Memory Allocation Under Hardware Compression · MICRO 2024 |
Operating systems › resource management
memory management |
0.8 | 1 | 2024 | Memory Allocation Under Hardware Compression · MICRO 2024 |
Memory systems › memory compression
hardware compressed memory |
0.8 | 1 | 2024 | Memory Allocation Under Hardware Compression · MICRO 2024 |
Memory systems
memory compression |
0.8 | 1 | 2024 | Memory Allocation Under Hardware Compression · MICRO 2024 |
Memory systems
DRAM |
0.2 | 1 | 2024 | Memory Allocation Under Hardware Compression · MICRO 2024 |
Methods — techniques the papers use, named apart from their topics
MMU-like component design · 1.5FPGA prototype · 1.5
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2024 | Memory Allocation Under Hardware CompressionabstractAs the scaling of memory density slows physically, a promising solution is to scale memory logically by enhancing the CPU's memory controller to encode and store data more densely in memory. This is known as hardware memory compression. Hardware memory compression decouples OS-managed physical memory from actual memory (i.e., DRAM); the memory controller spends a dynamically varying amount of DRAM on each physical page, depending on the compressibility of the page's content. The newly-decoupled actual memory effectively forms a new layer of memory beyond the traditional layers of virtual, pseudo-physical, and physical memory. We note unlike these traditional memory layers, each with its own specialized allocation interface (e.g., malloc/mmap for virtual memory, page tables+MMU for physical memory), this new layer of memory introduced by hardware memory compression still awaits its own unique memory allocation interface; its absence makes the allocation of actual memory imprecise and, sometimes, even impossible. Imprecisely allocating less actual memory, and/or unable to allocate more, can harm performance. Even imprecisely allocating more actual memory to some jobs can be harmful as it can result in allocating less actual memory to other jobs in highly-occupied memory systems, where compression is useful. To restore precise memory allocation, we design a new memory allocation specialized for this new layer of memory and, subsequently, architect a new MMU-like component in the memory controller and tackle the corresponding design challenges. We create a full-system FPGA prototype of a hardware-compressed memory system with precise memory allocation. Our evaluations using the prototype show that jobs perform stably under colocation. The performance variation is only 1%-2%; in comparison, it is 19%-89% under the prior art. Muhammad Laghari, Gagandeep Panwar, David Bears, Chandler Jearls, Raghavendra Srinivas, Esha Choukse, Kirk W. Cameron, Ali Raza Butt, Xun Jian 0002 |
MICRO | 6 |