Our system is a lot more complex than just 1 image source and 1 image sink.
We have several other processes that may also require images. The file,
although it may have its drawbacks, does allow multiple processes to use the
same image data without replicating it all over the place.

----- Original Message -----
From: "Jochen Kunz" <jkunz@unixag-kl.fh-kl.de>
To: "Daniel Brewer" <danielb@cat.co.za>
Cc: <tech-kern@netbsd.org>
Sent: Tuesday, July 08, 2003 10:16 AM
Subject: Re: fsync performance hit on 1.6.1


On 2003.07.07 09:45 Daniel Brewer wrote:

> For our application, we have 1 process capturing images from a
> frame-grabber and dumping them to a file in a memory file system.
> It sends a UDP message to another process that reads the images
> from this file and writes them to disk in a database.
Why don't you use a AF_UNIX socket to pipe the image data from process
to process or SYSV sharerd memory with semaphore interlocking? The later
would be the fastetst way to transfer the data and it avoids any file
system interaction.
--


tschüß,
       Jochen

Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/