Write multithreaded programs using POSIX threads.You'll find descriptions of over 500 system calls and library functions, and more than 200 example programs, 88 tables, and 115 diagrams. In this authoritative work, Linux programming expert Michael Kerrisk provides detailed descriptions of the system calls and library functions that you need in order to master the craft of system programming, and accompanies his explanations with clear, complete example programs. I cannot stop seeing his name now that I have completed the book.The Linux Programming Interface is the definitive guide to the Linux and UNIX programming interface-the interface employed by nearly every application that runs on a Linux or UNIX system. Michael Kerrisk is the maintainer of the Linux man-pages project since 2004, and many man pages were edited during the preparation of this authoritative book. A book like this requires dedication over numerous years before going to press. The explanations are always clear, succinct, and the book is perfectly organized. Few technical books impressed me so much (and I read a lot!). The Linux Programming Interface is truly a masterpiece. You can always come back to read the code examples more attentively before using them in your programs. It contains many chapters, many examples in C, and reading the first pages of every chapter can be enough to decide if you want to learn more on this subject. You will not read the book in a few days, but you don’t need to read the whole book. With over 1500 pages, this book will test the solidity of your bookshelf, and your desire to discover the Linux APIs. I read a lot recently about eBPF, and this book was helpful to feel comfortable on this advanced, also important, topic. And when your application doesn’t operate with the expected performance, understanding the Linux system calls will go a long way to help you understand the bottleneck.
Many innovations were made possible due to changes or the appearance of new system calls. Understanding Linux syscalls is important for developers.
0 kommentar(er)
