All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carsten Otte <cotte@de.ibm.com>
To: Jared Hulbert <jaredeh@gmail.com>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
	"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>
Subject: Re: [PATCH 05/10] AXFS: axfs_profiling.c
Date: Fri, 22 Aug 2008 09:26:31 +0200	[thread overview]
Message-ID: <48AE6A27.9070103@de.ibm.com> (raw)
In-Reply-To: <6934efce0808210817h489bbeafyaf27217ca68bd31e@mail.gmail.com>

Jared Hulbert wrote:
>> The profiling code has certainly been useful to you during development,
>> and you should keep that code around for your own work on it,
>> but maybe you should not push that upstream, because regular users
>> are not going to need it.
> 
> Nope.  Profiling is absolutely fundamental to how AXFS works.  Read
> the [PATCH 00/10] thread again.
I agree, the profiling part is the sweet spot. Profiling should be in, 
probably even selectable at runtime as opposed to a config-switch. 
This way we could have it in enterprise distros that would'nt build 
another kernel image for this.

WARNING: multiple messages have this Message-ID (diff)
From: Carsten Otte <cotte@de.ibm.com>
To: Jared Hulbert <jaredeh@gmail.com>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
	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>,
	"David Woodhouse" <dwmw2@infradead.org>
Subject: Re: [PATCH 05/10] AXFS: axfs_profiling.c
Date: Fri, 22 Aug 2008 09:26:31 +0200	[thread overview]
Message-ID: <48AE6A27.9070103@de.ibm.com> (raw)
In-Reply-To: <6934efce0808210817h489bbeafyaf27217ca68bd31e@mail.gmail.com>

Jared Hulbert wrote:
>> The profiling code has certainly been useful to you during development,
>> and you should keep that code around for your own work on it,
>> but maybe you should not push that upstream, because regular users
>> are not going to need it.
> 
> Nope.  Profiling is absolutely fundamental to how AXFS works.  Read
> the [PATCH 00/10] thread again.
I agree, the profiling part is the sweet spot. Profiling should be in, 
probably even selectable at runtime as opposed to a config-switch. 
This way we could have it in enterprise distros that would'nt build 
another kernel image for this.

  parent reply	other threads:[~2008-08-22  7:26 UTC|newest]

Thread overview: 27+ 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  5:45 ` Jared Hulbert
2008-08-21  8:44 ` Carsten Otte
2008-08-21  8:44   ` Carsten Otte
2008-08-21  8:49   ` David Woodhouse
2008-08-21  8:49     ` David Woodhouse
2008-08-21 10:20     ` Carsten Otte
2008-08-21 10:20       ` Carsten Otte
2008-08-21 11:39     ` Arnd Bergmann
2008-08-21 11:39       ` Arnd Bergmann
2008-08-21 14:55       ` Jared Hulbert
2008-08-21 14:55         ` Jared Hulbert
2008-08-21 15:06         ` Arnd Bergmann
2008-08-21 15:06           ` Arnd Bergmann
2008-08-21 15:17           ` Jared Hulbert
2008-08-21 15:17             ` Jared Hulbert
2008-08-21 15:50             ` Arnd Bergmann
2008-08-21 15:50               ` Arnd Bergmann
2008-08-22  7:26             ` Carsten Otte [this message]
2008-08-22  7:26               ` Carsten Otte
2008-08-21 15:18           ` Geert Uytterhoeven
2008-08-21 15:18             ` Geert Uytterhoeven
2008-08-22 20:37         ` Arnd Bergmann
2008-08-22 20:37           ` Arnd Bergmann
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
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=48AE6A27.9070103@de.ibm.com \
    --to=cotte@de.ibm.com \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=arnd@arndb.de \
    --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 \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.