From owner-freebsd-net Fri Jan 29 16:00:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04578 for freebsd-net-outgoing; Fri, 29 Jan 1999 16:00:14 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04570 for ; Fri, 29 Jan 1999 16:00:13 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id PAA28623; Fri, 29 Jan 1999 15:54:22 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma028621; Fri, 29 Jan 99 15:54:19 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id PAA01659; Fri, 29 Jan 1999 15:54:19 -0800 (PST) From: Archie Cobbs Message-Id: <199901292354.PAA01659@bubba.whistle.com> Subject: Re: netgraph... In-Reply-To: <2105.917596839@critter.freebsd.dk> from Poul-Henning Kamp at "Jan 29, 99 09:00:39 am" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Fri, 29 Jan 1999 15:54:19 -0800 (PST) Cc: julian@whistle.com, net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Poul-Henning Kamp writes: > >Now the question is: > >where does it go? > > I argue with KISS for "in the kernel". > > The area we're into here, is the "weirdo config args", things like > telling cards to go into loop-back on channel 4, to select balanced > or unbalanced connection, the speed of V.35 (for buffer estimation), > ISDN switch type. All these highly irregular things that always > ends up in the LINK[012] flags for interfaces and in the flags for > isa devices. > > (If you look at most of the fooctrl programs, they are small, do > almost nothing, and a general "ioctl" program which could pass > an generic ioctl with an ascii argument to the driver would save > us some code...) > > I can almost even live with the bloat of a "usage" control message > which returns an ascii usage string. Poul- What did you think of the idea of having each node contain two new methods for encoding and decoding ASCII strings? I say methods but really they would just understand two new generic message types. Then ngctl could send control messages to encode and decode, while 'normal' control messages between nodes stayed in binary form. It also respects KISS, by keeping all the node-specific code together. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message