public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: David Boreham <david_list@boreham.org>
To: Vara Prasad <prasadav@us.ibm.com>
Cc: SystemTap <systemtap@sources.redhat.com>
Subject: Re: user mode backtrace
Date: Thu, 19 Oct 2006 22:51:00 -0000	[thread overview]
Message-ID: <45380175.3080708@boreham.org> (raw)
In-Reply-To: <4537FD1A.9080607@us.ibm.com>

Vara Prasad wrote:

> If i read your above message correctly you would like to put probes in 
> the kernel but you want to get a full stack which includes kernel mode 
> stack and as well as user mode stack, correct.

ack

> David, if you want to put probes in the user space itself and do back 
> trace we are working on user space probing patch that will let you  
> see the stack just in the application space only. We may be able to 
> give some thing for you to play within couple of weeks if you are 
> interested in user space probing.

I'm not sure if this would work. It depends on whether I would need to 
identify the
processes subject to probing in advance. The application spawns 
processes left and right,
many of which are sort-lived. If I could place a probe in the glibc 
layer above
the system calls that might work, but said probes would need to magically
apply to any process that called that code. Is that the feature you have 
in mind ?

But even so, I can imagine cases where it would still be useful to probe 
in the
kernel but show user stack : e.g. I probe physical read from disk 
because I am
not interested in reads served from filesystem cache. But I'd like to 
find out
where the read calls that hit non-cached data are coming from in the 
application.
Hope that makes sense.

> My next question to you is we are looking to put good load on the 
> system while running probes, is this filesystem application is 
> something that you can share and it is easy for us to run outside of 
> your environment. If this is an application that you can not share 
> outside can you help us run this application while putting lots of 
> probes touching various parts of the system. We can give you scripts, 
> if you like, that will place probes in many parts of the system or 
> specifically in the areas this application touches the most. Please 
> let us know.

The application is not supersecret. In fact in binary form it can be
downloaded from a public web site. I have been loading it with
an open source benchmark tool. So it would be possible for
someone else to reproduce my setup. To see source you'd need
to wait for the application to be open source'ed, which it will be soon
but not right now.

For now however I want to be a little cautious about the details
of what I'm working on. Let me go find out how much I am able
to share...



  reply	other threads:[~2006-10-19 22:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-19 20:47 David Boreham
2006-10-19 22:33 ` Vara Prasad
2006-10-19 22:51   ` David Boreham [this message]
2006-10-20 14:28     ` William Cohen
2006-10-20 14:50       ` David Boreham
2006-10-19 23:50 ` Frank Ch. Eigler
2006-10-20  0:15   ` David Boreham
2006-10-20  0:27     ` Frank Ch. Eigler
2006-10-19 22:56 Stone, Joshua I
2006-10-19 23:07 ` David Boreham
2006-10-19 23:24 ` David Boreham
2006-10-20  0:09 ` Frank Ch. Eigler
2006-10-20  2:02 Stone, Joshua I
2006-10-20  2:13 Stone, Joshua I
2006-10-20 18:34 Stone, Joshua I

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=45380175.3080708@boreham.org \
    --to=david_list@boreham.org \
    --cc=prasadav@us.ibm.com \
    --cc=systemtap@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).