Date: Fri, 1 May 1998 15:25:02 -0500 (EST) From: "John S. Dyson" <dyson@FreeBSD.ORG> To: pb@fasterix.freenix.org (Pierre Beyssac) Cc: wollman@khavrinen.lcs.mit.edu, freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Fwd: NetBSD network code improvements Message-ID: <199805012025.PAA04029@dyson.iquest.net> In-Reply-To: <19980501205833.A655@fasterix.frmug.fr.net> from Pierre Beyssac at "May 1, 98 08:58:33 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Remember, if we take anything from NetBSD, we need to fully credit them. Even though some "teams" are very liberal with other's ideas, lets (the FreeBSD team) not get into that habit. > > It is modular enough that I ported it in 2 hours, and > I'm currently running it. Everything is in one file (ip_flow.c) > and you just need to add hooks calling it when receiving packets > from the interfaces. Works ok for me so far between PPP and my > ethernet (which doesn't say much about the performance improvement > :-)). I'll send the patches to the list soon. The only problem that > I see is that it clutters up the kernel even if you don't use it > (in NetBSD, it is compiled in only if you have the GATEWAY option, > but you can't do that in FreeBSD since it's a kernel configuration > variable). We should probably make it an explicit option but other > than that I don't see any reason for not taking it. > > The bpf stuff is useful for userland application programmers. My > understanding is that it's the same for the socket zero-copy stuff. > I haven't looked at these yet. > -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805012025.PAA04029>