Top all-time · #5828
Viacheslav Biriukov
Personal blog · biriukov.devsystemsprogramming
Viacheslav Biriukov's personal blog at biriukov.dev covers systems and programming. Since 2021, 14 different Hacker News readers have linked it 16 times, most often “SRE deep dive into Linux Page Cache”. It has a working feed you can follow.
Too few sampled comments (3) to say how often HN recommends it.?
Why HN links it
HN readers link Viacheslav Biriukov's posts on how DNS resolution works on Linux and Kubernetes, and on terminals, consoles and shells, including how SSH fits in. Commenters call them useful reads.
Summarised by Claude from a sample of 3 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Hi, I’m Viacheslav 👋 Welcome to my corner of the web where code, systems thinking, and life philosophy meet. I write about GNU/Linux, SRE, Golang, Rust, async I/O, and network engineering. Blog posts # Async Rust gotcha: evolving tokio::select! code has sharp edges… or a story about Cancella
Most-linked posts?
- SRE deep dive into Linux Page Cache8 people · 9 mentions · first linked 2021-09-22
- Async Rust with Tokio I/O streams: backpressure, concurrency, and ergonomics2 people · 2 mentions · first linked 2025-10-11
What Hacker News says?
Assuming Linux, oddly enough I came across this exact behavior[0] while researching resource management for an on-prem k8s cluster. Take a look at that thread for more info, but TL;DR, you need to actually finesse page cache constraints if you want avoid the behavior. You actually can have really fine grained control over page cache via cgroups v2[1][2] and systemd[3]. [0]: https://github.com/kubernetes/kubernetes/i…
Comment linking /docs/page-cache/6-cgroup-v2-and-page-cache/
on “Linuxatemyram.com”Submitted SRE deep dive into Linux Page Cache as a story · 17 points
HN discussionExcellent article. I would add two things: Negative DNS responses are possible in two forms: 1. nxdomain and a 2. NODATA response. They both mean that a DNS record is not found but they have different scope. NODATA response rcode is NoError, not nxdomain yet the answer is still negative, like http 404. To understand the difference, read this short rfc https://datatracker.ietf.org/doc/html/rfc2308 Also, I would point…
Comment linking /docs/resolver-dual-stack-application/0-sre-should-know-about-gnu-linux-resolvers-and-dual-stack-applications/
on “Understanding DNS Resolution on Linux and Kubernetes”Submitted Deep Dive into Linux Page Cache as a story · 5 points
HN discussionThis is great! I’ve been remotely logging into systems for all of my adult life and last week I went on a bit of a bender because I realized didn’t really grasp how these things actually work. I am not sure I do now (specifically how SSH ties in to this). But at least I now know more about terminals, shells, rawmode and ptms/ptx and more. This link right here fits right in with the following ones: [0] https://biriuk…
Comment linking /docs/fd-pipe-session-terminal/4-terminals-and-pseudoterminals/
on “A Guide to the Terminal, Console, and Shell”Submitted Async Rust with Tokio I/O streams: backpressure, concurrency, and ergonomics as a story · 3 points
HN discussionSubmitted Linux Page Cache for SRE as a story · 3 points
HN discussionSubmitted Linux Page Cache for SRE as a story · 3 points
HN discussionSubmitted Linux Page Cache for SRE as a story · 3 points
HN discussionSubmitted SRE deep dive into Linux Page Cache as a story · 2 points
HN discussionSubmitted Async Rust with Tokio I/O Streams: Backpressure, Concurrency, and Ergonomics as a story · 2 points
HN discussionSubmitted SRE Deep Dive into Linux Page Cache as a story · 2 points
HN discussionSubmitted Deep Dive into the Linux Page Cache as a story · 2 points
HN discussionSubmitted Linux Page Cache for SRE as a story · 2 points
HN discussionSubmitted Linux Page Cache mini book as a story · 1 points
HN discussionSubmitted GNU/Linux shell related internals as a story · 1 points
HN discussion
