Am Samstag 01 April 2006 14:50 schrieb jamal: > No stefan - check arpd. Infact if you really want to scale ARP to many > many entries, you do it in user space. This has been proven more than > once in the past: Thats the main reason the current daemons exist. It is
AFAIK the primary purpose of arpd was to overcome a limitation in the number of ARP cache entries older kernels can handle. It is extending, not replacing the in kernel implementation, taking over the role of active ARP probing is even optional. But I don't think our opinions are far of. For me, these points are important to make my opinion whether something belongs into the kernel or not. -How complex is the protocol, including workarounds for broken peers -How important is the protocol to allow some feature on a non-specialized machine to work -How often does it run -How bad would be a partial failure (OOM kill) So I'd keep a rather simple but important protocol in kernel, while stuff like 802.1X (not running very often, simple failure scenario) or STP and it's successors that can handle VLANs or load balancing should be userspace, even though the kernel should be able of a clean shutdown in case the daemon is killed. But I think we're getting too off topic now, I just wanted to make clear that I'd be quite unhappy if arp handling would be ripped out of the kernel. Stefan - 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
