书籍介绍
这是一本让读者又爱又恨的技术书。爱，是因为它几乎覆盖了Linux网络协议栈的每个角落：从sk_buff、net_device等关键数据结构，到设备驱动、路由、邻居、网桥与生成树协议，读完后你对内核如何处理一个数据包的完整旅程会有清晰把握。恨，是因为它
AI导读
核心看点
- 本书深入剖析Linux内核网络协议栈底层实现，涵盖从用户空间接口、系统初始化、网络设备驱动注册到PCI层交互的全流程。详细讲解sk_buff、net_device等核心数据结构及通知链机制，帮助读者理解内核如何管理网络硬件与协议栈的交互，是研究Linux网络架构的权威技术参考。
- 内容聚焦于网络层及以下协议实现，包括IPv4协议栈、ICMP、ARP邻居子系统、路由表管理及网桥与生成树协议。书中通过大量代码片段和流程图，揭示数据包在内核中的流转路径、分片处理、源路由及MTU发现机制，为读者提供构建高性能网络应用和调试复杂网络问题的底层视角。
- 作为经典技术著作，本书强调理论与实践结合，指导读者如何通过C语言实现网络功能，并分析内核源码中的关键函数与数据结构关系。尽管部分代码基于旧版内核，但其对网络协议原理、安全机制及系统初始化的深度解析，对于理解现代Linux网络子系统的设计思想仍具有极高的参考价值。
读者共识
- 尽管翻译质量备受诟病，但本书在Linux网络底层技术领域的地位依然不可动摇。读者普遍认为其内容极具深度，是理解Linux网络协议栈、驱动开发及系统初始化的必读经典。对于真正致力于内核级网络开发的从业者而言，克服语言障碍和阅读难度后，能获得其他书籍无法提供的底层视角和实战指导。
- 读者反馈本书学习曲线陡峭，阅读过程极其痛苦，需要极大的耐心和毅力。许多读者表示无法通读全书，建议将其作为工具书查阅，或在遇到具体技术问题时针对性阅读相关章节。同时，读者强烈建议不要依赖中文版，以免因翻译错误导致理解偏差，浪费宝贵时间并产生挫败感。
- 部分读者指出书中内容存在过时现象，且某些章节组织混乱，缺乏循序渐进的逻辑，导致阅读体验不佳。然而，也有资深开发者认为，只要忽略版本差异，其核心原理和设计模式依然适用。共识在于，本书适合有明确研究目的的高阶用户，不适合泛泛而读或作为入门教材，需配合实际源码分析才能发挥其价值。
精彩摘录
- "Few C programmers like the goto statement. Without getting into the history of the goto (one of the longest and most famous controversies in computer programming), I'll summarize some of the reasons the goto is usually deprecated, but why the Linux kernel uses it anyway. Any piece of code that uses "
- "NETDEV_TX_OK* The transmission succeeded. The buffer is not released yet (kfree_skb is not issued). We will see in the section “Processing the NET_TX_SOFTIRQ: net_tx_ action” that the driver does not release the buffer itself but asks the kernel to do so by means of the NET_TX_SOFTIRQ softirq. This "
- "• The root bridge is the only bridge that generates BPDUs. The other bridges transmit BPDUs only when they receive one (i.e., they revise the information they receive by simply updating a couple of fields). • The root bridge makes sure each bridge in the network comes to know about a topology change"
- "Source Routing is a multibyte option in which the source node lists IP addresses to be used on subsequent hops. Of course, if one of the routers in the list goes down, the source-routed packet will not be able to benefit from any dynamic rerouting done on routing protocols. Usually, when a router go"
- "In the very worst case, the two packets could have the same length and the overlapping could corrupt the payload without corrupting the L4 headers. The IP checksum cov- ers only the IP header and therefore cannot detect this condition. Depending on the application, the consequences could be serious."
- "It should be noted that the algorithm always shrinks the PMTU, it never increases it. However, the entries of the routing cache whose PMTU is derived from an ingress ICMP FRAGMENTATION NEEDED message expire after some time, which is equivalent to going back to the (bigger) default PMTU. See the same"
- "Nevertheless, one has to admit that a better design of related protocols could remove some of the overhead imposed by features that overlap in the proto- cols at different layers. Because most L2 and L4 protocols provide checksums, hav- ing it at L3 as well is not strictly necessary. For exactly thi"
- "The minimum MTU associated with a route is in fact 68, which comes from RFC 791. Since the IP header can be up to 60 bytes long (20+40) and the minimum frag- ment length (with the exception of the last one) is 8 bytes, it follows that every IP router must be able to forward an IP packet of 68 bytes "
目录
用户评论
基本概念介绍的很清楚，相关代码有些过时。
怀念那时没日没夜地啃这本书的充实感
有些地翻译的差了些，不过配个着百度和远吗，可以看懂
翻译太差，有一页的两个图居然是两个大叉，可见译者的态度，可怜我的一百大洋啊……
建议读原著，除非想速读。
通信工程驱动协议转发linux开发必读课本
对于理解内核中网络设备驱动，路由子系统，邻居子系统很有帮助。这本书不涉及内核中socket层的实现，包括tcp传输层等。
linux内核网络协议栈的必读著作，读了部分章节。还是先看点linux源码相关的，不然看的比较吃力。
linux内核网络协议栈的必读著作，翻译有些问题
19.04.05 趁清明放假把路由部分看看
中国电力出版社的其他书籍查看全部
下载
收藏