From: Greg KH <gregkh@suse.de>
To: Tom Zanussi <zanussi@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, karim@opersys.com
Subject: Re: [PATCH 4/4] relayfs: Documentation for exported relay fileops
Date: Wed, 9 Nov 2005 14:46:37 -0800 [thread overview]
Message-ID: <20051109224637.GA9794@suse.de> (raw)
In-Reply-To: <17266.31257.240080.519064@tut.ibm.com>
On Wed, Nov 09, 2005 at 04:37:13PM -0600, Tom Zanussi wrote:
> Andrew Morton writes:
> > Tom Zanussi <zanussi@us.ibm.com> wrote:
> > >
> > > +By default of course, relay_open() creates relay files in the relayfs
> > > +filesystem. Because relay_file_operations is exported, however, it's
> > > +also possible to create and use relay files in other pseudo-filesytems
> > > +such as debugfs.
> >
> > Why would anyone wish to place relayfs files within other
> filesystems?
>
> The reason they're exported is that when relayfs was being considered
> for inclusion, GregKH requested that the relay file operations be
> exported, which I did but didn't actually try to use them there until
> now. It turns out that the current patch's changes are needed in
> order to be able to do that. The reason behind being able to do this
> I assume is so that developers can use relay files do ad hoc tracing
> inside debugfs rather than have part of their application in debugfs
> and another part in relayfs. Maybe Greg can chime in as to whether he
> thinks it's still useful
Yes, I still think that is very useful to have. The relayfs core code
shouldn't rely on what filesystem is is placed into.
Thanks for doing this, I appreciate it.
greg k-h
prev parent reply other threads:[~2005-11-09 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 21:51 [PATCH 4/4] relayfs: Documentation for exported relay fileops Tom Zanussi
2005-11-09 22:03 ` Andrew Morton
2005-11-09 22:37 ` Tom Zanussi
2005-11-09 22:46 ` Greg KH [this message]
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=20051109224637.GA9794@suse.de \
--to=gregkh@suse.de \
--cc=akpm@osdl.org \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zanussi@us.ibm.com \
/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