linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jared Hulbert" <jaredeh@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "David Woodhouse" <dwmw2@infradead.org>,
	carsteno@de.ibm.com, Linux-kernel@vger.kernel.org,
	linux-embedded@vger.kernel.org,
	linux-mtd <linux-mtd@lists.infradead.org>,
	"Jörn Engel" <joern@logfs.org>,
	tim.bird@am.sony.com, nickpiggin@yahoo.com.au
Subject: Re: [PATCH 05/10] AXFS: axfs_profiling.c
Date: Thu, 21 Aug 2008 07:55:34 -0700	[thread overview]
Message-ID: <6934efce0808210755n1977e085o63b8b91e84575dc9@mail.gmail.com> (raw)
In-Reply-To: <200808211339.37187.arnd@arndb.de>

On Thu, Aug 21, 2008 at 4:39 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> On Thursday 21 August 2008, David Woodhouse wrote:
>> On Thu, 2008-08-21 at 10:44 +0200, Carsten Otte wrote:
>> >
>> > Exporting profiling data for a file system in another file system
>> > (/proc) seems not very straigtforward to me. I think it is worth
>> > considering to export this information via the same mount point.
>>
>> I would have said sysfs, rather than 'the same mount point'.
>>
>
> Let me throw in debugfs as my preferred option. sysfs is for stable
> interfaces, while profiling generally fits into the debugging category.

Three responses, three suggestions....

1) same mount point -
I don't see how this works without an ioctl.  I can't just make up
files in my mounted filesystem.   You expect the mounted version to
match input to the mkfs.  I'd not be happy with an ioctl.  You can
just read it.

2) sysfs -
I agree with Carsten, I don't see how this fits in the sysfs hierarchy.

3) debugfs -
I don't know diddly about this.

So why not /proc?

  reply	other threads:[~2008-08-21 14:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21  5:45 [PATCH 05/10] AXFS: axfs_profiling.c Jared Hulbert
2008-08-21  8:44 ` Carsten Otte
2008-08-21  8:49   ` David Woodhouse
2008-08-21 10:20     ` Carsten Otte
2008-08-21 11:39     ` Arnd Bergmann
2008-08-21 14:55       ` Jared Hulbert [this message]
2008-08-21 15:06         ` Arnd Bergmann
2008-08-21 15:17           ` Jared Hulbert
2008-08-21 15:50             ` Arnd Bergmann
2008-08-22  7:26             ` Carsten Otte
2008-08-21 15:18           ` Geert Uytterhoeven
2008-08-22 20:37         ` Arnd Bergmann
     [not found] ` <200808221840.39206.arnd@arndb.de>
     [not found]   ` <6934efce0808221037u4548dd00q9ccd67545bfbcc8@mail.gmail.com>
2008-08-22 19:38     ` Arnd Bergmann

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=6934efce0808210755n1977e085o63b8b91e84575dc9@mail.gmail.com \
    --to=jaredeh@gmail.com \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=arnd@arndb.de \
    --cc=carsteno@de.ibm.com \
    --cc=dwmw2@infradead.org \
    --cc=joern@logfs.org \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=tim.bird@am.sony.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;
as well as URLs for NNTP newsgroup(s).