From: "Zhang, Yanmin" <[EMAIL PROTECTED]> Date: Tue, 22 Jan 2008 14:52:32 +0800
> I double-checked it and they are queued to socket A. If I define a > different local port for netperf, packets will be queued to socket > B. This does not prove the kernel is buggy. If netperf is binding to devices, that could make the kernel consider the 0.0.0.0 bound socket equally preferable to the 127.0.0.1 bound one. When preference is equal, the first socket in the list is choosen. The algorithm is in net/ipv4/udp.c:__udp4_lib_lookup(), you can look for yourself. It uses a scoring system to decide which socket to match. Binding to a specific device gives the score two points, so does binding to a specific local address. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
