tcp offload engine

Article Source: http://hi.baidu.com/zyqq/blog/item/54bb905256546f040cf3e3a9.html In fact, this problem is often found during packet capture. Today I went to Google with curiosity. In a simple summary, the packet captured by Wireshark prompts a checksum error,It is only because it intercepts the overhead checksum of the operating system, and the Gigabit NIC will hand over the computing work to the NIC after enabling checksum offload, the NIC finally

Have you ever encountered a problem where you tried to connect to the trouble shoot network, but you only saw three handshakes in the network packet capture tool? If you use NetMon 2.x, NetMon 3.x, Wireshark, ethereal, and most other network packet capture tools, this will happen. This is a relatively common sense. This happens when TCP chimney offload is enabled, but it always solves the problem after

happened.On a piece of white paper, draw a bunch of gate circuits, and then randomly combine them, slowly, I suddenly found that this circuit is the framework of TSO. I remember helping people fix the routing forwarding last week, but that kind of curing behavior could be too expensive to pass off, after all, now the soft implementation is enough. So only the core transmission network needs this curing of the forwarding, but TSO is the server domain of the first push, server too much, far more

Abbreviated as Tso, TCPSEgmentationOFfloadIs used to reduce the CPU overhead of TCP/IP on fast Networks. TSO breaks down large groups of data sent over a network into smaller segments that pass through all the network elements between the source and destination. this type of offload relies on the network interface controller (NIC) to segment the data and then add the