From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-kernel@vger.kernel.org, Randy Dunlap <rdunlap@xenotime.net>,
Sam Ravnborg <sam@ravnborg.org>,
Jens Axboe <jens.axboe@oracle.com>,
Prasanna S Panchamukhi <prasanna@in.ibm.com>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <pzijlstr@redhat.com>,
Philippe Elie <phil.el@wanadoo.fr>,
Linus Torvalds <torvalds@linux-foundation.org>,
"William L. Irwin" <wli@holomorphy.com>,
Arjan van de Ven <arjan@infradead.org>,
Christoph Lameter <christoph@lameter.com>
Subject: Re: [RFC] Create instrumentation directory (git repository)
Date: Mon, 29 Oct 2007 19:40:12 -0400 [thread overview]
Message-ID: <20071029234012.GB19413@Krystal> (raw)
In-Reply-To: <Pine.LNX.4.64.0710291619210.4821@schroedinger.engr.sgi.com>
* Christoph Lameter (clameter@sgi.com) wrote:
> On Mon, 29 Oct 2007, Mathieu Desnoyers wrote:
>
> > vm/vmstat.c
>
> The vm statistics are important for the operation of the VM. They are not
> optional. So I do not think that they fall under the category of
> instrumentation.
But I guess vm stats can be useful to others; a kernel tracer for
instance ?
Putting stuff in instrumentation/ by no way means that it becomes
optional for a subsystem, but merely that it could either export
information useful for kernel instrumentation or have some
infrastructure parts merged with others.
Mathieu
--
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next prev parent reply other threads:[~2007-10-29 23:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 21:51 Mathieu Desnoyers
2007-10-29 22:47 ` Randy Dunlap
2007-10-29 22:54 ` Jeff Garzik
2007-10-29 23:04 ` Mathieu Desnoyers
2007-10-29 23:08 ` Jeff Garzik
2007-10-29 23:35 ` Mathieu Desnoyers
2007-10-30 0:47 ` Jeff Garzik
2007-10-30 1:38 ` Mathieu Desnoyers
2007-10-30 9:13 ` Arnaldo Carvalho de Melo
2007-10-30 17:24 ` [RFC] Create kinst/ or ki/ directory ? Mathieu Desnoyers
2007-10-30 17:49 ` Peter Zijlstra
2007-10-30 17:50 ` Linus Torvalds
2007-10-30 17:58 ` Christoph Hellwig
2007-10-30 18:56 ` Mathieu Desnoyers
2007-10-30 19:25 ` Linus Torvalds
2007-10-30 20:40 ` Mathieu Desnoyers
2007-10-31 15:48 ` Frank Ch. Eigler
2007-10-31 16:29 ` Arjan van de Ven
2007-10-31 19:05 ` Frank Ch. Eigler
2007-10-31 19:49 ` Arjan van de Ven
2007-10-31 16:36 ` Mathieu Desnoyers
2007-10-31 19:29 ` Frank Ch. Eigler
2007-10-30 21:46 ` Sam Ravnborg
2007-10-29 23:20 ` [RFC] Create instrumentation directory (git repository) Christoph Lameter
2007-10-29 23:40 ` Mathieu Desnoyers [this message]
2007-10-29 23:45 ` Christoph Lameter
2007-10-30 0:51 ` Jeff Garzik
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=20071029234012.GB19413@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=arjan@infradead.org \
--cc=christoph@lameter.com \
--cc=clameter@sgi.com \
--cc=davem@davemloft.net \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=phil.el@wanadoo.fr \
--cc=prasanna@in.ibm.com \
--cc=pzijlstr@redhat.com \
--cc=rdunlap@xenotime.net \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.org \
--cc=wli@holomorphy.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
Powered by JetHome