From: "Ph. Marek" <philipp.marek@bmlv.gv.at>
To: linux-kernel@vger.kernel.org
Subject: Exporting a lot of data to other processes?
Date: Thu, 25 Oct 2007 08:05:33 +0200 [thread overview]
Message-ID: <200710250805.33369.philipp.marek@bmlv.gv.at> (raw)
Hello everybody,
I've already pondered about a question for some time, and would like to ask
for a better idea here. It's not entirely about the kernel - although that
surely has some impact, too.
I've got some process/daemon, that wants to export information to other
processes. As model for exporting that data I found the sysfs and procfs
nice - an easy "cat" can give you the needed data.
Now, in order to do something like that from userspace, I either have to:
-) use FUSE
- feels slow (many context switches)
- much overhead for such common things (another daemon)
-) use named pipes in some directory structure, and keep them open in
the daemon - waiting to be written to
- many open filehandles
- feels not really useable for bigger (>1000) structures
-) use some ramfs/shmfs or similar, and overwrite the data occasionally
- not current data
- runtime overhead (processor load)
Now the open/close events wouldn't be interesting; the read() and (possibly)
write events would have to be relayed (which is not the case for FUSE, IIUC)
Is there some better way? For small structures the pipes seem to be the best
way ... just wait for a reader, give it data, and finished.
Thank you for all ideas.
Regards,
Phil
next reply other threads:[~2007-10-25 6:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 6:05 Ph. Marek [this message]
2007-10-26 22:58 ` Nix
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200710250805.33369.philipp.marek@bmlv.gv.at \
--to=philipp.marek@bmlv.gv.at \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®