Top all-time · #2384
paulmck.livejournal.com
Personal blog · paulmck.livejournal.comprogrammingsystems
paulmck.livejournal.com is a personal blog at paulmck.livejournal.com about programming and systems. Since 2011, 32 different Hacker News readers have linked it 43 times, most often “So You Want to Rust the Linux Kernel?”. No feed was found, so read it on the site itself.
Too few sampled comments (9) to say how often HN recommends it.?
Why HN links it
HN readers link Paul McKenney's journal for its long series on RCU, memory models and parallel programming, including Rust in the Linux kernel. Commenters point to the series index and suggest starting points.
Summarised by Claude from a sample of 9 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- So You Want to Rust the Linux Kernel?5 people · 5 mentions · first linked 2021-10-02
- What Does It Mean to Be an RCU Implementation? (2023)2 people · 2 mentions · first linked 2023-01-27
- Linux: Is RCU Watching?2 people · 2 mentions · first linked 2022-05-27
- Transactional Memory Everywhere: 2012 Update 2 people · 2 mentions · first linked 2012-03-11
- /2 people · 2 mentions · first linked 2022-02-07
What Hacker News says?
> This means that using it for the core parts may be feasible sooner rather than later, no? More like much later. There are several performance-critical patterns used in the Linux kernel that are difficult to express in unsafe Rust and impossible to express in safe Rust. See https://paulmck.livejournal.com/62436.html and especially https://paulmck.livejournal.com/64209.html I think promoting the use of Rust for driv…
Comment linking /64209.html
on “Rust support in the Linux kernel”Submitted So You Want to Rust the Linux Kernel? as a story · 240 points
HN discussionEDIT: Paste this hacky snippet into your browser's console to save all of the links into your clipboard: (() => { let result = [...document.querySelectorAll('td a')] .map((link) => link && !link.href.includes('ycombinator') && !link.href.includes('javascript:void') ? link.href : '' ) .filter(Boolean); result = [...new Set(result)]; result.sort(); copy(result.join('\n\n')); })(); Just to help, here's a compiled-list…
Comment linking /
on “Ask HN: Great Blogs by Programmers”Submitted Is parallel programming hard, and, if so, what can you do about it? as a story · 135 points
HN discussionPaul E. McKenney's Journal: https://paulmck.livejournal.com/
Comment linking /
on “Ask HN: Great Blogs by Programmers”Submitted What memory model should Rust use? as a story · 122 points
HN discussionSome of you may want to read the entire series (in 14 parts). The index is here: https://paulmck.livejournal.com/62436.html
Comment linking /62436.html
on “Rust in the 6.2 kernel”Submitted How read-intensive is the kernel's use of RCU? (2022) as a story · 54 points
HN discussionHere's a pretty good blog post that discusses how the memory models could interact: https://paulmck.livejournal.com/65341.html My understanding is that it might not be entirely settled yet, and is still being discussed. That could explain why there isn't much solid documentation written yet
Comment linking /65341.html
on “Rust in the 6.2 kernel”Submitted Parallel Programming, a book by Paul McKenney as a story · 46 points
HN discussion> Given that DEC Alpha famously had difficulty with RCU, it is only reasonable to ask how Rust will do with it. > Including some wild speculation about how Rust's ownership model might be generalized I recommend starting with the latests post in the series and the conclusions( https://paulmck.livejournal.com/64209.html and https://paulmck.livejournal.com/65056.html ). From the snippets at the beginning, it looks lik…
Comment linking /65056.html
on “So You Want to Rust the Linux Kernel?”Submitted Stupid RCU Tricks: Enlisting the Aid of a Debugger as a story · 13 points
HN discussionI shared this perspective, but luckily my job is awesome and (in a routine 1:1!) Paul told me why it's less straightforward than I thought: https://paulmck.livejournal.com/62436.html my takeaway was essentially that you get sweet perf wins from semantics that are hard to replicate with a type system that's also making really strong guarantees without making the code SUPER gross.
Comment linking /62436.html
on “Simple Linux kernel memory corruption bug can lead to complete system compromise”Submitted Verification Challenge 2: RCU NO_HZ_FULL_SYSIDLE as a story · 12 points
HN discussionHere is Paul E. McKenney's announcement of the release: http://paulmck.livejournal.com/36854.html
Comment linking /36854.html
on “Is Parallel Programming Hard, And, If So, What Can You Do About It?”Submitted Stupid SMP Tricks: A Review of Locking Engineering Principles and Hierarchy as a story · 8 points
HN discussionI highly recommend Paul McKenney's blog series on this topic: http://paulmck.livejournal.com/tag/transactional%20memory%20...
Comment linking /tag/transactional%20memory%20everywhere
on “Speculative Lock Elision in Varnish Cache”Submitted Rcutorture Catches an RCU Bug as a story · 8 points
HN discussionSubmitted Transactional Memory Everywhere: HTM and Cache Geometry as a story · 4 points
HN discussionSubmitted Parallel Programming: December 2020 Update as a story · 3 points
HN discussionSubmitted A Linux kernel memory model as a story · 3 points
HN discussionSubmitted Parallel Programming: Second Edition as a story · 2 points
HN discussionSubmitted Concurrent Computational Models as a story · 2 points
HN discussionSubmitted Linux: Is RCU Watching? as a story · 2 points
HN discussionSubmitted Stupid RCU Tricks: Is RCU Watching? as a story · 2 points
HN discussionSubmitted Rusting the Linux Kernel as a story · 2 points
HN discussionSubmitted So You Want to Rust the Linux Kernel? as a story · 2 points
HN discussionSubmitted So You Want to Rust the Linux Kernel? as a story · 2 points
HN discussionSubmitted The Old Man and His Smartphone as a story · 2 points
HN discussionSubmitted “Is Parallel Programming Hard, And, If So, What Can You Do About It?”: July 2016 as a story · 2 points
HN discussion