From: Peter Williams <pwil3058@bigpond.net.au>
To: karim@opersys.com
Cc: Greg KH <greg@kroah.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@muc.de>,
Roman Zippel <zippel@linux-m68k.org>,
Tom Zanussi <zanussi@us.ibm.com>,
Robert Wisniewski <bob@watson.ibm.com>,
Tim Bird <tim.bird@AM.SONY.COM>
Subject: Re: [PATCH] relayfs redux for 2.6.10: lean and mean
Date: Fri, 21 Jan 2005 13:15:28 +1100 [thread overview]
Message-ID: <41F065C0.7070603@bigpond.net.au> (raw)
In-Reply-To: <41F05D11.5020109@opersys.com>
Karim Yaghmour wrote:
> Greg KH wrote:
>
>>Hm, how about this idea for cutting about 500 more lines from the code:
>>
>>Why not drop the "fs" part of relayfs and just make the code a set of
>>struct file_operations. That way you could have "relayfs-like" files in
>>any ram based file system that is being used. Then, a user could use
>>these fops and assorted interface to create debugfs or even procfs files
>>using this type of interface.
>>
>>As relayfs really is almost the same (conceptually wise) as debugfs as
>>far as concept of what kinds of files will be in there (nothing anyone
>>would ever rely on for normal operations, but for debugging only) this
>>keeps users and developers from having to spread their debugging and
>>instrumenting files from accross two different file systems.
>
>
> However this assumes that the users of relayfs are not going to want
> it during normal system operation. This is an assumption that fails
> with at least LTT as it is targeted at sysadmins, application developers
> and power users who need to be able to trace their systems at any time.
>
> I don't mind piggy-backing off another fs, if it makes sense, but
> unlike debugfs, relayfs is meant for general use, and all files in there
> are of the same type: relay channels for dumping huge amounts of data
> to user-space. It seems to me the target audience and basic idea (relay
> channels only in the fs) are different, but let me know if there's a
> compeling argument for doing this in another way without making it too
> confusing for users of those special "files" (IOW, when this starts
> being used in distros, it'll be more straightforward for users to
> understand if all files in a mounted fs behave a certain way than if
> they have certain "odd" files in certain directories, even if it's
> /proc.)
Perhaps the logical solution is to implement debugfs in terms of relayfs?
Peter
--
Peter Williams pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
next prev parent reply other threads:[~2005-01-21 2:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 6:23 [PATCH] relayfs redux for 2.6.10: lean and mean Karim Yaghmour
2005-01-20 14:50 ` Greg KH
2005-01-21 1:38 ` Karim Yaghmour
2005-01-21 2:15 ` Peter Williams [this message]
2005-01-21 6:39 ` Greg KH
2005-01-21 7:27 ` Peter Williams
2005-01-21 7:46 ` Greg KH
2005-01-21 6:43 ` Greg KH
2005-01-23 8:07 ` Karim Yaghmour
2005-01-20 15:06 ` Greg KH
2005-01-20 19:51 ` Pekka Enberg
2005-02-07 3:04 ` [PATCH] relayfs crash Kingsley Cheung
2005-02-07 3:16 ` Karim Yaghmour
2005-02-07 4:42 ` Tom Zanussi
2005-02-07 4:47 ` Kingsley Cheung
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=41F065C0.7070603@bigpond.net.au \
--to=pwil3058@bigpond.net.au \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=bob@watson.ibm.com \
--cc=greg@kroah.com \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.bird@AM.SONY.COM \
--cc=zanussi@us.ibm.com \
--cc=zippel@linux-m68k.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