From owner-cvs-src@FreeBSD.ORG Fri Feb 27 10:43:39 2004 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 69FED16A4CF for ; Fri, 27 Feb 2004 10:43:39 -0800 (PST) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 2814243D2F for ; Fri, 27 Feb 2004 10:43:39 -0800 (PST) (envelope-from nate@root.org) Received: (qmail 86182 invoked by uid 1000); 27 Feb 2004 18:43:39 -0000 Date: Fri, 27 Feb 2004 10:43:39 -0800 (PST) From: Nate Lawson To: Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= In-Reply-To: Message-ID: <20040227104209.A86020@root.org> References: <200402260234.i1Q2YDx1014240@repoman.freebsd.org> <20040226060126.GA70201@troutmask.apl.washington.edu> <20040226015016.B23674@xorpc.icir.org> <20040226071123.A31631@xorpc.icir.org> <20040227004602.A73084@xorpc.icir.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/contrib/pf/net if_pflog.c if_pflog.h if_pfsync.c if_pfsync.h pf.c pf_ioctl.c pf_norm.c pf_osfp.c pf_table.c pfvar.h src/sys/contrib/pf/netinet in4_cksum.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Feb 2004 18:43:39 -0000 On Fri, 27 Feb 2004, Dag-Erling [iso-8859-1] Sm=F8rgrav wrote: > Luigi Rizzo writes: > > I believe this (convert the entire networking stack to netgraph > > nodes) is completely unfeasible. > > It shouldn't be. Open any textbook on computer networking and you'll > find that netgraph is the canonical way to organize a protocol stack. > > > There are interactions among subsystems all over the place. > > Otherwise known as "layering violations" and "bugs". Not necessarily. I like Dave Clark's point that layers are a good way to specify networking standards but a poor way to implement them. This talk is old but gives good info on one way of doing it: http://www.root.org/ip-development/talks/vj-nkarch.ps.gz -Nate