From: David Woodhouse <dwmw2@infradead.org>
To: carsteno@de.ibm.com
Cc: jaredeh@gmail.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 09:49:19 +0100 [thread overview]
Message-ID: <1219308560.2988.247.camel@pmac.infradead.org> (raw)
In-Reply-To: <48AD2AFF.5060609@de.ibm.com>
On Thu, 2008-08-21 at 10:44 +0200, Carsten Otte wrote:
> Jared Hulbert wrote:
> > Profiling is a fault instrumentation and /proc formating system.
> > This is used to get an accurate picture of what the pages are actually used.
> > Using this info the image can be optimized for XIP
> 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'.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2008-08-21 8:49 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 [this message]
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
[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=1219308560.2988.247.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=Linux-kernel@vger.kernel.org \
--cc=carsteno@de.ibm.com \
--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;
as well as URLs for NNTP newsgroup(s).