From: "Theodore Ts'o" <tytso@mit.edu>
To: Christoph Hellwig <hch@infradead.org>,
Richard J Moore <richardj_moore@uk.ibm.com>,
Andrew Morton <akpm@osdl.org>,
ak@suse.de, davem@davemloft.net, linux-kernel@vger.kernel.org,
prasanna@in.ibm.com, suparna@in.ibm.com
Subject: Re: [2/3 PATCH] Kprobes: User space probes support- readpage hooks
Date: Tue, 21 Mar 2006 07:40:58 -0500 [thread overview]
Message-ID: <20060321124058.GF8257@thunk.org> (raw)
In-Reply-To: <20060321111452.GA5460@infradead.org>
On Tue, Mar 21, 2006 at 11:14:52AM +0000, Christoph Hellwig wrote:
> > A real life example of where this capability would have been very useful is
> > with a performance problem I am currently investigating. It involves a GPFS
> > + SAMBA + TCPIP + RDAC
>
> this pobablt tells more about the crappy code quality of your propritary
> code than a real need for this. please argue without reference to huge
> blobs of junk.
In real life there are complicated stacks; sometimes they are open
source (for example, like JBoss or Tomcat), sometimes they are
propietary products, sometimes they are custom applications written by
the end-user. Sun has been making big hay about how with dtrace, you
can easily figure out what is going on. Systemtap is a tool that will
allow us to have have this kind of capability, and user space probes
is part of that project.
- Ted
next prev parent reply other threads:[~2006-03-21 12:41 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 6:07 [0/3] Kprobes: User space probes support Prasanna S Panchamukhi
2006-03-20 6:09 ` [1/3 PATCH] Kprobes: User space probes support- base interface Prasanna S Panchamukhi
2006-03-20 6:10 ` [2/3 PATCH] Kprobes: User space probes support- readpage hooks Prasanna S Panchamukhi
2006-03-20 6:11 ` [3/3 PATCH] Kprobes: User space probes support- single stepping out-of-line Prasanna S Panchamukhi
2006-03-20 11:09 ` Andrew Morton
2006-03-20 11:24 ` Arjan van de Ven
2006-03-20 14:05 ` Prasanna S Panchamukhi
2006-03-20 14:13 ` Arjan van de Ven
2006-03-20 11:32 ` Nick Piggin
2006-03-20 13:52 ` Prasanna S Panchamukhi
2006-03-20 13:48 ` Prasanna S Panchamukhi
2006-03-20 20:40 ` Andrew Morton
2006-03-21 2:02 ` Prasanna S Panchamukhi
2006-03-21 10:05 ` Andrew Morton
2006-03-21 11:05 ` Richard J Moore
2006-03-21 11:13 ` Suparna Bhattacharya
2006-03-21 12:23 ` Prasanna S Panchamukhi
2006-03-20 10:53 ` [2/3 PATCH] Kprobes: User space probes support- readpage hooks Andrew Morton
2006-03-20 13:48 ` Prasanna S Panchamukhi
2006-03-21 2:12 ` Andrew Morton
2006-03-21 9:14 ` Richard J Moore
2006-03-21 11:14 ` Christoph Hellwig
2006-03-21 11:38 ` Richard J Moore
2006-03-21 12:40 ` Theodore Ts'o [this message]
2006-03-21 11:28 ` Christoph Hellwig
2006-03-21 11:42 ` Richard J Moore
2006-03-21 12:15 ` Christoph Hellwig
2006-03-21 16:17 ` Richard J Moore
2006-03-20 11:10 ` Andrew Morton
2006-03-20 13:59 ` Prasanna S Panchamukhi
2006-03-20 10:42 ` [1/3 PATCH] Kprobes: User space probes support- base interface Andrew Morton
2006-03-20 13:48 ` Prasanna S Panchamukhi
2006-03-21 11:39 ` [0/3] Kprobes: User space probes support Christoph Hellwig
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=20060321124058.GF8257@thunk.org \
--to=tytso@mit.edu \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prasanna@in.ibm.com \
--cc=richardj_moore@uk.ibm.com \
--cc=suparna@in.ibm.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