Communications kernel -> userland

[Pawel Jakub Dawidek]

On Sat, Jul 19, 2003 at 09:47:08AM +0200, 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.

Hmm, there is a chance that I've reverse direction:)

But if you don't use kevent/kqueue you need to tell kernel that you want
to read data.

For example exporting logs from kernel to userland (to syslogd) is via
device /dev/klog.

-- 
Pawel Jakub Dawidek                       pawel at dawidek.net
UNIX Systems Programmer/Administrator     http://garage.freebsd.pl
Am I Evil? Yes, I Am!                     http://cerber.sourceforge.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 305 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20030719/f9705e4c/attachment.bin