From: Hanna Linder <hannal@us.ibm.com>
To: karim@opersys.com, linux-kernel <linux-kernel@vger.kernel.org>
Cc: hannal@us.ibm.com, lse-tech@lists.sourceforge.net
Subject: Re: [RFC] High-speed data relay filesystem
Date: Tue, 07 Jan 2003 10:44:58 -0800 [thread overview]
Message-ID: <9370000.1041965097@w-hlinder> (raw)
In-Reply-To: <3E1B17DF.BCC51B3@opersys.com>
--On Tuesday, January 07, 2003 01:09:35 PM -0500 Karim Yaghmour <karim@opersys.com> wrote:
>
> As I mentioned earlier on this list, there is an increasing number
> of facilities and tools that need to relay large amounts of data from
> kernel space to user space. Up to this point, each of these has had
> its own mechanism for relaying data. The following is a proposal to
> implement a "high-speed data relay filesystem" (relayfs) that would
> supersede the individual mechanisms. As such, things like LTT, printk,
Karim, This seeems like a good idea. A standard mechanism
for tools to access kernel info could be very useful. Im curious
what other people who work on tools think about this?
Hanna
next prev parent reply other threads:[~2003-01-07 18:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-07 18:09 [RFC] High-speed data relay filesystem Karim Yaghmour
2003-01-07 18:44 ` Hanna Linder [this message]
2003-01-07 19:40 ` Andreas Dilger
2003-01-07 20:32 ` Karim Yaghmour
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=9370000.1041965097@w-hlinder \
--to=hannal@us.ibm.com \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
/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