From: Tom Zanussi <zanussi@us.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: karim@opersys.com, bob@watson.ibm.com
Subject: [RFC][PATCH 0/5] relayfs
Date: Tue, 15 Jul 2003 10:15:35 -0500 [thread overview]
Message-ID: <16148.6807.578262.720332@gargle.gargle.HOWL> (raw)
The following 5 patches implement relayfs, adding a dynamic channel
resizing capability to the previously posted version.
relayfs is a filesystem designed to provide an efficient mechanism for
tools and facilities to relay large amounts of data from kernel space
to user space. Full details can be found in Documentation/filesystems/
relayfs.txt. The current version can always be found at
http://www.opersys.com/relayfs.
I'll be posting shortly a version of printk that replaces the static
printk buffer with a dynamically resizing relayfs channel.
Relayfs is also used as the buffering mechanism for recent development
versions of the Linux Trace Toolkit (LTT).
These patches are for 2.6.0-test1.
Known problems - using read() to read from a resized channel may
result in garbage. This doesn't affect any current clients though
i.e. the dynamic printk I'll be posting or the Linux Trace Toolkit.
Thanks to Rusty Russell for picking some nits in the previous version.
Comments welcome.
--
Regards,
Tom Zanussi <zanussi@us.ibm.com>
IBM Linux Technology Center/RAS
next reply other threads:[~2003-07-15 15:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 15:15 Tom Zanussi [this message]
2003-07-15 15:27 ` [RFC][PATCH 0/5] relayfs Gianni Tedesco
2003-07-15 16:01 ` Tom Zanussi
2003-07-15 16:40 ` Gianni Tedesco
2003-07-15 17:01 ` Tom Zanussi
2003-07-15 18:45 ` Tom Zanussi
2003-07-16 21:55 ` [PATCH] relayfs Stephen Hemminger
2003-07-16 22:27 ` [PATCH] relay_open const filename Stephen Hemminger
2003-07-18 21:11 ` [PATCH] relayfs Tom Zanussi
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=16148.6807.578262.720332@gargle.gargle.HOWL \
--to=zanussi@us.ibm.com \
--cc=bob@watson.ibm.com \
--cc=karim@opersys.com \
--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;
as well as URLs for NNTP newsgroup(s).