From owner-freebsd-hackers Thu Nov 29 11:59:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 885) id 76D5637B419; Thu, 29 Nov 2001 11:59:09 -0800 (PST) Date: Thu, 29 Nov 2001 11:59:09 -0800 From: Eric Melville To: Nyteckjobs@aol.com Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org, tedm@toybox.placo.com Subject: Re: (no subject) Message-ID: <20011129115909.A75251@FreeBSD.org> References: <14e.4d05ff7.29371325@aol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <14e.4d05ff7.29371325@aol.com>; from Nyteckjobs@aol.com on Wed, Nov 28, 2001 at 11:27:17PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > The concept that "netgraph hooks" are a "leg up" on say, ETs drivers that > have integrated bandwidth management and prioritization, WAN bridging > support, load balancing and a probably 25% performance advantage is a bit > entertaining. Unless you need to do some convoluted encapsulation netgraph > is, aside from being appallingly non-standard to anything else in the market, > not much of an "advantage", and its a poster child for the trade off of > "flexibility" versus performance. > > Lets face it. If you were going to sit down and design an interface for frame > relay, multi-protocol support, etc, you'd have to be smoking something pretty > strong to come up with netgraph. But its free and there is source, so it > must be great! Dennis, if you are going to continue trolling FreeBSD mailing lists from your AOL account, you should really consider choosing a name that does not coincide with what we already know or can easily find out about you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message