public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Tom Zanussi <zanussi@us.ibm.com>
Cc: Karim Yaghmour <karim@opersys.com>,
	akpm@osdl.org, linux-kernel@vger.kernel.org, varap@us.ibm.com,
	richardj_moore@uk.ibm.com
Subject: Re: Merging relayfs?
Date: Mon, 11 Jul 2005 21:27:17 -0700	[thread overview]
Message-ID: <20050712042717.GB2363@kroah.com> (raw)
In-Reply-To: <17107.16181.300398.8599@tut.ibm.com>

On Mon, Jul 11, 2005 at 10:55:33PM -0500, Tom Zanussi wrote:
> Greg KH writes:
>  > On Mon, Jul 11, 2005 at 11:03:59PM -0400, Karim Yaghmour wrote:
>  > > 
>  > > Greg KH wrote:
>  > > > What ever happened to exporting the relayfs file ops, and just using
>  > > > debugfs as your controlling fs instead?  As all of the possible users
>  > > > fall under the "debug" type of kernel feature, it makes more sense to
>  > > > confine users to that fs, right?
>  > > 
>  > > Actually, like we discussed the last time this surfaced, there are far
>  > > more users for relayfs than just debugging.
>  > 
>  > Based on the proposed users of this fs, I don't see any.  What ones are
>  > you saying are not "debug" type operations?  And yes, I consider LTT a
>  > "debug" type operation :)
>  > 
>  > The best part of this, is it gives distros and users a consistant place
>  > to mount the fs, and to know where this kind of thing shows up in the fs
>  > namespace.
> 
> Makes sense, and I don't see a problem with getting rid of the fs part
> of relayfs and letting debugfs take over that role, if debugfs were
> there for all potential users.  It doesn't sound like it would satisfy
> users like LTT and systemtap though, who expect to be available at all
> times even on production systems, which wouldn't be the case unless
> the distros always shipped with debugfs enabled.

They will, the overhead of adding debugfs support is _very_ tiny, only:
 $ size fs/debugfs/built-in.o 
   text    data     bss     dec     hex filename
   2257     788       8    3053     bed fs/debugfs/built-in.o

So I do not see why you should not just drop your fs part.

>  > > What we settled on was having relayfs export its file ops so that
>  > > indeed debugfs users could use it to log things in conjunction with
>  > > debugfs.
>  > 
>  > Last I looked, this was not possible.  Has this changed in the latest
>  > version?
> 
> The file operations are all exported, but I haven't actually tried to
> use relayfs files in debugfs.  Is there something more needed?

Shouldn't be.  Try it to make sure though :)

thanks,

greg k-h

  reply	other threads:[~2005-07-12  4:33 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-12  1:10 Merging relayfs? Tom Zanussi
2005-07-12  1:45 ` Andrew Morton
2005-07-12  2:17   ` Dave Airlie
2005-07-12  2:22   ` Tom Zanussi
2005-07-12  9:12     ` Baruch Even
2005-07-12  2:25 ` Christoph Hellwig
2005-07-12  2:34   ` Andrew Morton
2005-07-12  2:59     ` Karim Yaghmour
2005-07-14 13:26     ` Roman Zippel
2005-07-14 15:01       ` Tom Zanussi
2005-07-17 14:04         ` Roman Zippel
2005-07-17 15:52           ` Tom Zanussi
2005-07-18  5:17             ` Hareesh Nagarajan
2005-07-18 14:31               ` Tom Zanussi
2005-07-18 13:44             ` Steven Rostedt
2005-07-18 14:16               ` Roman Zippel
2005-07-18 14:32                 ` Karim Yaghmour
2005-07-18 15:20                   ` Roman Zippel
2005-07-18 15:58                     ` Tom Zanussi
2005-07-22 20:43                       ` Tom Zanussi
2005-07-22 23:19                         ` Karim Yaghmour
2005-07-23  2:31                           ` Tom Zanussi
2005-07-26  2:35                             ` Karim Yaghmour
2005-07-22 20:43                       ` Tom Zanussi
2005-07-18 14:36                 ` Steven Rostedt
2005-07-18 15:06                   ` Roman Zippel
2005-07-18 14:41               ` Tom Zanussi
2005-07-18  8:40         ` Richard J Moore
2005-07-12 13:03   ` Steven Rostedt
2005-07-12  3:05 ` Greg KH
2005-07-12  3:03   ` Karim Yaghmour
2005-07-12  3:24     ` Greg KH
2005-07-12  3:52       ` Karim Yaghmour
2005-07-12  4:30         ` Greg KH
2005-07-12  4:40           ` Karim Yaghmour
2005-07-12  5:23             ` Greg KH
2005-07-12 14:36               ` Steve Rotolo
2005-07-12  3:55       ` Tom Zanussi
2005-07-12  4:27         ` Greg KH [this message]
2005-07-12 14:01 ` Tomasz Kłoczko
2005-07-12 14:21   ` Baruch Even
2005-07-12 15:30     ` Tomasz Kłoczko
2005-07-12 15:16   ` Tom Zanussi
2005-07-12 15:44     ` Tomasz Kłoczko
2005-07-12 16:27       ` Tom Zanussi
2005-07-12 17:01         ` Tomasz Kłoczko
2005-07-12 17:23           ` Tom Zanussi
     [not found]             ` <Pine.BSO.4.62.0507121935500.6919@rudy.mif.pg.gda.pl>
     [not found]               ` <17108.1906.628755.613285@tut.ibm.com>
     [not found]                 ` <Pine.BSO.4.62.0507122026520.6919@rudy.mif.pg.gda.pl>
     [not found]                   ` <17108.5721.202275.377020@tut.ibm.com>
2005-07-12 19:29                     ` Tomasz Kłoczko
2005-07-12 20:44                       ` Vara Prasad
2005-07-12 21:02               ` Vara Prasad
2005-07-13 12:40                 ` Tomasz Kłoczko
2005-07-13 15:04                   ` Vara Prasad
2005-07-13 16:22                     ` Tomasz Kłoczko
2005-07-13  4:29           ` Vara Prasad
2005-07-13 13:47             ` Tomasz Kłoczko
2005-07-13 15:55               ` Karim Yaghmour
2005-07-13 15:56               ` Vara Prasad
2005-07-13 16:50                 ` Tomasz Kłoczko
2005-07-12 14:58 ` Jason Baron
2005-07-12 15:26   ` Tom Zanussi
2005-07-12 16:00     ` Steven Rostedt
2005-07-12 15:53   ` Steven Rostedt
2005-07-12 16:08     ` Tom Zanussi
2005-07-12 16:23       ` Steven Rostedt
2005-07-12 16:36         ` Tom Zanussi
2005-07-12 16:49           ` Steven Rostedt
2005-07-12 17:01             ` Tom Zanussi
2005-07-12 21:38               ` Tom Zanussi
2005-07-12 23:40                 ` Steven Rostedt
2005-07-12 23:55                   ` Andrew Morton
2005-07-13  0:08                     ` Steven Rostedt
2005-07-16 21:07 ` relayfs documentation sucks? bert hubert
2005-07-16 23:13   ` Tom Zanussi
2005-07-17  9:01     ` [PATCH] " bert hubert
2005-07-17 15:43       ` Tom Zanussi
2005-07-17 19:45         ` bert hubert
2005-07-17 20:47           ` Tom Zanussi
2005-07-18 13:27           ` Steven Rostedt
2005-07-20 21:27             ` Paul Jackson
2005-07-20 21:45               ` bert hubert
2005-07-21  0:31                 ` Paul Jackson
2005-07-22 20:01                 ` Paul Jackson
2005-07-22 20:33                   ` relayfs as infrastructure, ltt, systemtap, diskstat bert hubert
2005-07-23 18:53                     ` Christoph Hellwig
2005-07-23 18:53                   ` [PATCH] Re: relayfs documentation sucks? Christoph Hellwig
2005-07-25 23:47                     ` Karim Yaghmour
2005-07-26  5:15                       ` bert hubert
     [not found] <17107.6290.734560.231978@tut.ibm.com.suse.lists.linux.kernel>
     [not found] ` <20050712022537.GA26128@infradead.org.suse.lists.linux.kernel>
     [not found]   ` <20050711193409.043ecb14.akpm@osdl.org.suse.lists.linux.kernel>
2005-07-12  4:36     ` Merging relayfs? Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2005-07-13  8:13 Spirakis, Charles

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=20050712042717.GB2363@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=karim@opersys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richardj_moore@uk.ibm.com \
    --cc=varap@us.ibm.com \
    --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