Messages in this thread | | | Date | Wed, 9 Nov 2005 14:46:37 -0800 | From | Greg KH <> | Subject | Re: [PATCH 4/4] relayfs: Documentation for exported relay fileops |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |