Hacker News Reader

Comment by angry_octet | Hacker News Reader

It's down right now, but I guess it is related to Stevens's APUE? A masterful book. I'd love to see it updated for newer kernel interfaces, seccomp etc.

View on HN

There's a cached version:

https://webcache.googleusercontent.com/search?q=cache:Y56fxQ...

GNU/Linux is not Unix ;)

Don't trigger me man :-|

I wasn't excluding the BSDs there, Stevens would definitely have covered dtrace, ZFS, Capsicum etc. But I hope that the Solaris/SysV specific stuff could be put in a forbidden appendix. No more ipcs please!

Care to give a link or context for "no more ipcs"? SysV shared mem is IMO a straightforward, robust low-level (MMU-level) IPC mechanism for CPU-bound tasks compared to memory-mapped I/O and the PITA that are threads, but admittedly I'm not up to date on this topic.

Mainly the cleanup problem. Determining if something is a live resource is tedious. Numeric IDs are inferior to paths IME, especially from a kernel ABI filtering perspective.

>"robust low-level (MMU-level) IPC mechanism for CPU-bound tasks compared to memory-mapped I/O ..."

Could you elaborate on what makes IPCS more suited to CPU-bound tasks vs mmap? Sys V ipcs has always kind of eluded me. I think my exposure to it was mostly via Oracle Databases way back when. Cheers.

Explicit shared read + exclusive write locks without resorting to atomic primitives (though that could also be seen as a disadvantage depending on your task).

Reply on news.ycombinator.com