From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 21 07:43:04 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 58FA737B401; Mon, 21 Jul 2003 07:43:04 -0700 (PDT) Received: from www.bluecirclesoft.com (cvg-65-26-145-190.cinci.rr.com [65.26.145.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60E8943FB1; Mon, 21 Jul 2003 07:43:03 -0700 (PDT) (envelope-from marc.ramirez@bluecirclesoft.com) Received: from www.bluecirclesoft.com (localhost [127.0.0.1]) h6LEh2SW047380; Mon, 21 Jul 2003 10:43:02 -0400 (EDT) (envelope-from mrami@bluecirclesoft.com) Received: from localhost (mrami@localhost)h6LEh1AG047377; Mon, 21 Jul 2003 10:43:02 -0400 (EDT) X-Authentication-Warning: www.bluecirclesoft.com: mrami owned process doing -bs Date: Mon, 21 Jul 2003 10:43:01 -0400 (EDT) From: Marc Ramirez To: Pawel Jakub Dawidek In-Reply-To: <20030719074707.GB437@garage.freebsd.pl> Message-ID: <20030721092218.C47203@www.bluecirclesoft.com> References: <20030719074707.GB437@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: deischen@freebsd.org cc: Marc Ramirez cc: freebsd-hackers@freebsd.org Subject: Re: Communications kernel -> userland X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2003 14:43:04 -0000 On Sat, 19 Jul 2003, Pawel Jakub Dawidek wrote: > On Fri, Jul 18, 2003 at 03:47:05PM -0400, Marc Ramirez wrote: > +> I have a remote datastore that I want to present as a filesystem. There > +> are two parts to this: fetching raw data over the network, and doing some > +> processing on the data. For purposes of maintainability, I'd like to do > +> as little of this as possible inside the kernel, so I've currently got a > +> daemon to fetch and process the data, and then pipes it over a socket to > +> the kernel FS layer. > > Your choices are: > - device, > - sysctl, > - syscall. > > You need to think about what you exactly need and which options will be > the best. Creating new syscall isn't good idea, creating device is more > complicated than sysctl, but of course it's up to you and your needs. Okay, thanks. Syscall seems completely counter-intuitive for my needs, anyway. Marc. -- Marc Ramirez Blue Circle Software Corporation 513-688-1070 (main) 513-382-1270 (direct) www.bluecirclesoft.com