Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Jonguk Jeon

dblp:416/7254 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
1since 2021 · last 2025
0009-0004-1770-7376ORCID · reported

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 1 · 1 first-author · 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
Storage systems · 100%

Topics — the 3 heaviest of 3, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Storage systems
crash consistency
0.912025
Analyzing and Enhancing ArckFS: An Anecdotal Example of Benefits of Artifact Evaluation · SOSP 2025
Storage systems
file systems
0.912025
Analyzing and Enhancing ArckFS: An Anecdotal Example of Benefits of Artifact Evaluation · SOSP 2025
Storage systems › file systems › file system design
persistent memory file system
0.912025
Analyzing and Enhancing ArckFS: An Anecdotal Example of Benefits of Artifact Evaluation · SOSP 2025

Methods — techniques the papers use, named apart from their topics

artifact evaluation · 0.9
YearPublicationVenuePosition
2025 Analyzing and Enhancing ArckFS: An Anecdotal Example of Benefits of Artifact Evaluation
abstract
We analyze and enhance Trio and ArckFS by Zhou et al. (SOSP 2023), high-performance NVM file system architecture and file system. A group of authors from KAIST initiated this study through a careful review of the paper and the released artifact, seeking to enhance the Trio work. Their analysis identifies (1) insufficient clarity in the paper on the handling of multi-inode operations, and (2) several implementation bugs in ArckFS that cause occasional operation failures or potential crash inconsistencies during inode creation.
Jonguk Jeon, Subeen Park, Sanidhya Kashyap, Sudarsun Kannan, Diyu Zhou, Jeehoon Kang
SOSP1