Top all-time · #5962
zinascii.com
Personal blog · zinascii.comsystemsprogramming
zinascii.com is a personal blog at zinascii.com about systems and programming. Since 2013, 13 different Hacker News readers have linked it 22 times, most often “The Illumos Syscall Handler”. No feed was found, so read it on the site itself.
Too few sampled comments (4) to say how often HN recommends it.?
Why HN links it
Ryan Zezeski's blog about illumos and kernel internals, including syscall handling, data structures such as the double-ended vector, and POSIX queue implementation.
Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- The Illumos Syscall Handler3 people · 4 mentions · first linked 2016-05-06
- A Posix Queue Implementation3 people · 3 mentions · first linked 2014-09-11
- How the Illumos AMD64 FBT Provider Intercepts Function Calls2 people · 2 mentions · first linked 2020-06-15
- Debugging SmartOS #1 – Finding Lock Inversions with DTrace2 people · 2 mentions · first linked 2017-06-19
What Hacker News says?
illumos actually has the advantage of a rich set of tooling designed for kernel development (DTrace, mdb, etc.) as well as an ethos of detailed comments -- and it tends to be a bit of a self-selecting community in that it attracts people who value the same. As an example of the adventures of a relative newcomer to illumos, see the excellent writings of Ryan Zezeski, e.g. [1][2][3]. [1] http://zinascii.com/2015/illum…
Comment linking /2014/a-posix-queue-implementation.html
on “Getting into Linux Kernel Development”Submitted Goodbye Joyent as a story · 260 points
HN discussionI wrote a detailed walk-through of the illumos syscall handler back in 2016. It's missing the updates around KPTI (meltdown mitigation), but other than that the mechanisms should be unchanged. https://zinascii.com/2016/the-illumos-syscall-handler.html
Comment linking /2016/the-illumos-syscall-handler.html
on “On the Costs of Syscalls (2021)”Submitted Most operating systems have implemented realtime signals incorrectly as a story · 105 points
HN discussionAre you familiar with the joke where the patient says about some awkward improbable activity, "Doctor, it hurts every time I do it" and the doctor responds "Then don't do that!" The principle here is the same: then don't do that! I will mention though that although pointers occupy 64 bits, the virtual address space on current x64 machines is limited to 48-bit (256 TB). This means that if you are careful, you can get…
Comment linking /2016/the-illumos-syscall-handler.html
on “Double-ended vector – is it useful?”Submitted The Illumos Syscall Handler as a story · 93 points
HN discussionAnother great article from that site: http://zinascii.com/2014/a-posix-queue-implementation.html
Comment linking /2014/a-posix-queue-implementation.html
on “The 8-Byte Two-Step”Submitted How My Printer Caused Excessive Syscalls and UDP Traffic as a story · 90 points
HN discussionSubmitted A Posix Queue Implementation as a story · 88 points
HN discussionSubmitted More Efficient TLB shootdowns as a story · 52 points
HN discussionSubmitted The 8-Byte Two-Step as a story · 48 points
HN discussionSubmitted Tracing Kernel Functions: FBT stack() and arg as a story · 26 points
HN discussionSubmitted Solr Distributed Search and the Stale Check as a story · 6 points
HN discussionSubmitted The Illumos Syscall Handler as a story · 5 points
HN discussionSubmitted Debugging SmartOS #1 – Finding Lock Inversions with DTrace as a story · 4 points
HN discussionSubmitted The Illumos Syscall Handler as a story · 4 points
HN discussionSubmitted How the Illumos AMD64 FBT Provider Intercepts Function Calls as a story · 3 points
HN discussionSubmitted Debugging SmartOS: Finding Lock Inversions with DTrace as a story · 3 points
HN discussionSubmitted Tracing Kernel Functions: How the Illumos AMD64 FBT Provider Intercepts Calls as a story · 2 points
HN discussionSubmitted Debugging a Zig Test Failure as a story · 1 points
HN discussion