From: Roland Bauerschmidt <rb@debian.org>
To: linux-kernel@vger.kernel.org
Subject: virtual filesystem with data managed in userspace
Date: Tue, 4 Dec 2001 22:40:26 +0100 [thread overview]
Message-ID: <20011204224026.A18753@g> (raw)
Hi,
for a science project I'm thinking about writing a virtual filesystem
driver that provides access to data that is managed in userspace. I'm
quite new to Kernel hacking, so I'd be glad if someone could provide
some tips about the design, especially the data exchange between kernel-
and userspace. The scenario looks like this:
/foo is type my_virtual_fs_to_be_written
If somebody reads let's say /foo/bar, the kernel module communicates in
some way with a daemon (or something) in userspace that provides the
nessary information (data) to the kernel module which then uses it
to return the necessary information to the application that tries to
read data.
Do you think this concept is workable at all? What I am most worried
about is the communication between user and kernel space since
eventually quite an amount of information (file contents) would need be
exchanged. High performance is not really critical here, though. How
could this be done best? I thought about a character device (FIFO)
through which kernel module and userspace daemon would exchange
commands and data in a defined way, similar to some network protocol
standard like HTTP.
It'd be very happy about any suggestions or tips,
Roland
--
Roland Bauerschmidt
next reply other threads:[~2001-12-04 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-04 21:40 Roland Bauerschmidt [this message]
2001-12-04 21:57 ` virtual filesystem with data managed in userspace Mike Castle
2001-12-04 22:00 ` Ragnar Kjørstad
2001-12-04 23:05 ` Adam Keys
2001-12-05 13:50 ` Roland Bauerschmidt
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=20011204224026.A18753@g \
--to=rb@debian.org \
--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