From owner-freebsd-current Thu Aug 22 16:49:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA03135 for current-outgoing; Thu, 22 Aug 1996 16:49:27 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA03100; Thu, 22 Aug 1996 16:49:18 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id QAA13113; Thu, 22 Aug 1996 16:48:51 -0700 From: "Rodney W. Grimes" Message-Id: <199608222348.QAA13113@GndRsh.aac.dev.com> Subject: Re: cvs commit: src/sys/netinet in.h ip_fw.h ip_input.c ip_output.c To: pst@jnx.com (Paul Traina) Date: Thu, 22 Aug 1996 16:48:50 -0700 (PDT) Cc: archie@whistle.com, julian@whistle.com, sos@freebsd.org, current@freebsd.org In-Reply-To: <199608222258.PAA03084@base.jnx.com> from Paul Traina at "Aug 22, 96 03:58:28 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > divert sockets could always be turned into a pointer-chaining module (as > should the IPFW hook itslef. I like the direction that sos layed out, now it just needs to be expanded so that the pointed to object can either be in the kernel or in user land. > From: Archie Cobbs > Subject: Re: cvs commit: src/sys/netinet in.h ip_fw.h ip_input.c ip_output.c > > > > In reply to Rodney W. Grimes who wrote: > > > > > > context switches are just not going to cut it... > > though sometimes you need to do things with packets that > > require interaction with a database of reading from files etc.. > > I put it to you that having a general way of getting the packets > > out of the kernel is better than adding bloat IN the kernel to > > do these things. > > No reason we can't have both; then everybody's happy :-) > > I like Soren's "pointer chaining" idea .. as long as divert sockets > are retained. Then you can use the kernel to do something if it > is suitable (and/or you need performance), or if not, then you can > always do it in user mode. > > User mode is also good for testing & debugging new things. > > -Archie > > > ___________________________________________________________________________ > Archie L. Cobbs, archie@whistle.com * Whistle Communications Corporation > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD