From: Arnd Bergmann <arnd@arndb.de>
To: "Jared Hulbert" <jaredeh@gmail.com>
Cc: nickpiggin@yahoo.com.au, linux-embedded@vger.kernel.org,
carsteno@de.ibm.com, "Jörn Engel" <joern@logfs.org>,
Linux-kernel@vger.kernel.org,
linux-mtd <linux-mtd@lists.infradead.org>,
tim.bird@am.sony.com, "David Woodhouse" <dwmw2@infradead.org>
Subject: Re: [PATCH 05/10] AXFS: axfs_profiling.c
Date: Fri, 22 Aug 2008 22:37:19 +0200 [thread overview]
Message-ID: <200808222237.20346.arnd@arndb.de> (raw)
In-Reply-To: <6934efce0808210755n1977e085o63b8b91e84575dc9@mail.gmail.com>
On Thursday 21 August 2008, Jared Hulbert wrote:
> 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.
Ok, so now yet another suggestion, which may sound a little strange:
oprofilefs
I believe you can use the oprofile infrastructure to record data
about file accesses, even independent of the file system you
are looking at.
It's probably a lot of work to get it right, but I would be worth it.
Arnd <><
next prev parent reply other threads:[~2008-08-22 20:37 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
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 [this message]
[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=200808222237.20346.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=Linux-kernel@vger.kernel.org \
--cc=carsteno@de.ibm.com \
--cc=dwmw2@infradead.org \
--cc=jaredeh@gmail.com \
--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