[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6934efce0808210755n1977e085o63b8b91e84575dc9@mail.gmail.com>
Date: Thu, 21 Aug 2008 07:55:34 -0700
From: "Jared Hulbert" <jaredeh@...il.com>
To: "Arnd Bergmann" <arnd@...db.de>
Cc: "David Woodhouse" <dwmw2@...radead.org>, carsteno@...ibm.com,
Linux-kernel@...r.kernel.org, linux-embedded@...r.kernel.org,
linux-mtd <linux-mtd@...ts.infradead.org>,
"Jörn Engel" <joern@...fs.org>,
tim.bird@...sony.com, nickpiggin@...oo.com.au
Subject: Re: [PATCH 05/10] AXFS: axfs_profiling.c
On Thu, Aug 21, 2008 at 4:39 AM, Arnd Bergmann <arnd@...db.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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists