[HN Gopher] Technical Guide to System Calls: Implementation and ...
       ___________________________________________________________________
        
       Technical Guide to System Calls: Implementation and Signal Handling
       in Modern OS
        
       Author : signa11
       Score  : 13 points
       Date   : 2025-06-03 16:45 UTC (6 hours ago)
        
 (HTM) web link (mohitmishra786.github.io)
 (TXT) w3m dump (mohitmishra786.github.io)
        
       | twoodfin wrote:
       | _One of the most important aspects of slow system calls is how
       | they interact with signals, which is the mechanism you
       | specifically asked about._
       | 
       | I didn't ask about anything. Was this AI-generated?
        
       | kazinator wrote:
       | s/Modern OS/1970s OS design still in use/
        
         | Animats wrote:
         | Right. This is a UNIX/Linux book. It's not how IBM mainframe
         | OSs work, or how QNX works, or how L4 works, or even how the
         | Windows kernel works.
         | 
         | There's nothing wrong with that, but they should say so up
         | front.
         | 
         | They wrote "From the user's perspective, disk reads are usually
         | considered non-blocking because they typically complete
         | quickly." Although if all storage is on solid state disk, you
         | might only lose 40us or so per read.
        
       | junon wrote:
       | AI generated article, seems like. Also, I wouldn't argue signals
       | are modern. They're kind of a hack, and have had endless problems
       | and footguns over the years. Programming with them is difficult
       | more often than it is easy (I think because there isn't actually
       | a way to program correctly with them...)
        
       ___________________________________________________________________
       (page generated 2025-06-03 23:00 UTC)