From owner-freebsd-hackers Fri Jan 9 05:35:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA19936 for hackers-outgoing; Fri, 9 Jan 1998 05:35:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from db2server.voga.com.br (db2server.voga.com.br [200.239.39.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA19913 for ; Fri, 9 Jan 1998 05:35:09 -0800 (PST) (envelope-from daniel_sobral@voga.com.br) From: daniel_sobral@voga.com.br Received: from papagaio.voga.com.br (papagaio.voga.com.br [200.239.39.2]) by db2server.voga.com.br (8.8.3+2.6Wbeta9/8.8.7) with SMTP id LAA11284; Fri, 9 Jan 1998 11:35:42 -0200 Received: by papagaio.voga.com.br(Lotus SMTP MTA v1.06 (346.7 3-18-1997)) id 03256587.00502AD4 ; Fri, 9 Jan 1998 11:35:38 -0300 X-Lotus-FromDomain: VOGA To: mike@smith.net.au cc: hackers@FreeBSD.ORG Message-ID: <83256587.004F044C.00@papagaio.voga.com.br> Date: Fri, 9 Jan 1998 11:35:33 -0300 Subject: Re: Device Driver Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk > Ah! You are building an encrypting *router*. Everything becomes much > much much more complicated. You have to maintain state for *all* of > the connections whose datagrams you are routing. This is respectably > nontrivial. [snip] > I have to be honest; it really sounds like you have embarked on a > product without actually *designing* the damn thing first. Then it doesn't sound right... :-) The product exists, and it's not mine. I'm just writing a driver for an encryption card that will be used by the product. Anyway, thanks for all the help. It seems all my problems haven been solved. In the end, I decided using tsleep, and they'll be creating a kernel process and accessing the device through it's normal interface. BTW, if I read the source code right, one "unit" of tsleep normally corresponds to 1/128 seconds, and 1/1024 while profiling, is that right? -- Daniel C. Sobral (8-DCS) Daniel_Sobral@voga.com.br