Date: Mon, 21 Jul 2003 10:43:01 -0400 (EDT) From: Marc Ramirez <marc.ramirez@bluecirclesoft.com> To: Pawel Jakub Dawidek <nick@garage.freebsd.pl> Cc: freebsd-hackers@freebsd.org Subject: Re: Communications kernel -> userland Message-ID: <20030721092218.C47203@www.bluecirclesoft.com> In-Reply-To: <20030719074707.GB437@garage.freebsd.pl> References: <Pine.GSO.4.10.10307181512460.14292-100000@pcnet5.pcnet.com> <20030719074707.GB437@garage.freebsd.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030721092218.C47203>